[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663493#comment-16663493
]
Oliver Lietz commented on SLING-7935:
-------------------------------------
[~rombert], binding all testing modules to the starter version prevents
improving incrementally und using them. Currently I'm seeing an issue with
DavEx and would like to fix it:
{code}
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.001 s
<<< FAILURE! - in
org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest
[ERROR]
testDescriptor(org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest)
Time elapsed: 0 s <<< ERROR!
java.lang.NoClassDefFoundError:
org/apache/jackrabbit/webdav/client/methods/BaseDavRequest
at
org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest.setUp(DavExIntegrationTest.java:47)
Caused by: java.lang.ClassNotFoundException:
org.apache.jackrabbit.webdav.client.methods.BaseDavRequest
at
org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest.setUp(DavExIntegrationTest.java:47)
{code}
But releasing this module now as version 13 doesn't make sense. What's the plan
for such cases?
> 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
(v7.6.3#76005)
