sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Lietz (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
Date Thu, 02 Apr 2020 06:49:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073420#comment-17073420
] 

Oliver Lietz commented on SLING-7935:
-------------------------------------

[~kwin], [~rombert], Tying the tests and support modules to the release cycle of Sling Starter
(fka Launchpad) means being unstable for 1 to 2 years with our current setup.
 Sling Karaf is consuming the Launchpad ITs inĀ [Apache Sling - Karaf Launchpad Integration
Tests (Oak Tar)|https://github.com/apache/sling-org-apache-sling-karaf-launchpad-oak-tar-integration-tests]
and there was a time when all tests passed (see history in SLING-3821).
 Currently we are again in a situation where cutting a release would help to stabilize (by
adjusting support modules to our current set of bundles):
{noformat}
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement
[root] osgi.identity; osgi.identity=test-dependencies; type=karaf.feature; version="[0,0.0.0]";
filter:="(&(osgi.identity=test-dependencies)(type=karaf.feature)(version>=0.0.0)(version<=0.0.0))"
[caused by: Unable to resolve test-dependencies/0.0.0: missing requirement [test-dependencies/0.0.0]
osgi.identity; osgi.identity=org.apache.sling.launchpad.test-services; type=osgi.bundle; version="[2.0.16,2.0.16]";
resolution:=mandatory [caused by: Unable to resolve org.apache.sling.launchpad.test-services/2.0.16:
missing requirement [org.apache.sling.launchpad.test-services/2.0.16] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.apache.sling.api.resource)(version>=2.11.0)(!(version>=2.12.0)))"]]
{noformat}
Otherwise Launchpad ITs are a moving target which is hard to track also because new tests
are added for snapshots.
How should this new approach work when we keep Sling Starter and Karaf free from snapshots?
That said the situation cannot get worse and as long the Launchpad/Starter ITs are usable
we could give it a try. 


> Consolidate all 'launchpad-testing' modules into a single git repository
> ------------------------------------------------------------------------
>
>                 Key: SLING-7935
>                 URL: https://issues.apache.org/jira/browse/SLING-7935
>             Project: Sling
>          Issue Type: Task
>          Components: Launchpad
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Starter 12
>
>
> We currently have seven testing-related modules in Git:
> * org-apache-sling-launchpad-integration-tests
> * org-apache-sling-launchpad-test-bundles
> * org-apache-sling-launchpad-test-fragment
> * org-apache-sling-launchpad-testing
> * org-apache-sling-launchpad-testing-war
> * org-apache-sling-launchpad-test-services
> * org-apache-sling-launchpad-test-services-war
> All of these are related to testing the starter application and typically we only release
them when the starter is also released. As such, it's a pain to manually keep versions in
sync and release the modules one by one. This is one scenario where a single git repository
would make sense.
> Whether this should be the actual starter repository or a starter-testing one is something
that is not set in stone, but the current situation is not optimal.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message