[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511399#comment-17511399 ] Oliver Lietz commented on SLING-7935: - [~rombert], Yes, that's fine. See [my comment|https://issues.apache.org/jira/browse/SLING-7935?focusedCommentId=17073558&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17073558]. > 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 13 > > > 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.20.1#820001)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511327#comment-17511327
]
Robert Munteanu commented on SLING-7935:
[~olli] - I'd like to take a "small steps" approach with this, and start by
moving {{launchpad-testing}} into the Starter project. The net effect will be
that we will be able to run all Sling ITs from the Starter, and not have two
separate modules anymore.
The "auxiliary" test-services, test-bundle etc modules will be untouched by
this.
Would that work for you?
> 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 13
>
>
> 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.20.1#820001)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087556#comment-17087556 ] Robert Munteanu commented on SLING-7935: [~olli]. My larger point was that we have the starter testing projects, that run against the starter. When releasing the Starter, we should release the launchpad-testing ones as well, since they are projects that are built for running the tests _against the starter_. The testing projects have SNAPSHOT dependencies to other projects in the mix, hence the need to release. I do not disagree with your point on updating the test bundles when a bundle changes, but that is IMO better served by moving the tests next to the bundle, rather than having a separate release flow. As Bertrand pointed out, those tests rarely change these days. Taking a step back, I think the challenge here is that the whole test setup was made to be run executed against the Launchpad (now Starter) and now we have multiple targets ( which is perfectly fine BTW ). I think that we should keep these dependencies manageable in terms of releases by moving back to the starter what makes sense ( launchpad-testing and launchpad-testing-war ) and then consolidating all the other testing projects. The consolidation could use more discussion, and yes, the workflow you proposed above could work as well. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087096#comment-17087096
]
Oliver Lietz commented on SLING-7935:
-
[~rombert], How does it answer my question?
{quote}We release the tests to capture the state of how Sling worked for that
certain release, [...]
{quote}
Is the above your point? With that approach you cover the state only for a
Sling Starter release – once for a period of one to two years.
If we release the modules when required we cover also the state between Starter
releases. That makes tracking of changes easier and the modules evolve
independently anyway.
Workflow:
# (Try to) Add a new version of a bundle to Starter
# Test breaks
# Fix test/support bundle
# Release test/support bundle
# Update test/support bundle in Starter
# Finally add the new version of bundle to Starter
With that workflow the committer who wants to update Starter is also
responsible for the integration tests. This means also no more snapshots in
Starter and effort for keeping ITs working is distributed between committers.
> 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077985#comment-17077985 ] Robert Munteanu commented on SLING-7935: [~olli] - see https://cwiki.apache.org/confluence/display/SLING/Releasing+a+new+version+of+the+Sling+Starter#ReleasinganewversionoftheSlingStarter-Updateandreleasethe%22core%22setofartifacts > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077240#comment-17077240
]
Oliver Lietz commented on SLING-7935:
-
[~bdelacretaz], Running Launchpad ITs during Starter build is very much
appreciated (sorry if I was not clear on this point).
[~rombert], Where do you see interdependencies between Starter and testing
modules?
See for example [~bdelacretaz]'s [latest
commit|https://github.com/apache/sling-org-apache-sling-launchpad-test-services/commit/ed44eaa99a3fd6ca4ab556b5e0d12c9015615ea1]
which changes the package import version in
{{org.apache.sling.launchpad.test-services}} - there is no need to adjust any
other test module (only Testing/Starter/Karaf have to switch to SNAPSHOT).
> 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077198#comment-17077198
]
Robert Munteanu commented on SLING-7935:
[~olli]
{quote}I still see no benefit in moving the remaining modules into a single Git
repo{quote}
After releasing the Sling Starter a number of times I see a great benefit in
releasing 1 module instead of 8 interdependent ones. In addition, those
particular modules don't change that much so I don't think it's a big problem
in lumping them together in a single repository.
Yes, in theory they are independent, in practice we need to touch all of them
for releases due to all the SNAPSHOT dependencies.
(Who would've thought I would be arguing for moving modules in the same git
repo :-) )
> 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077195#comment-17077195 ] Bertrand Delacretaz commented on SLING-7935: bq. I still see no benefit in moving the remaining modules into a single Git repo. For me what adds value is being able to run the Launchpad ITs as part of the Starter build, to catch issues earlier than we do today. I don't have a strong opinion on where the test code comes from. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077189#comment-17077189 ] Oliver Lietz commented on SLING-7935: - [~rombert], [~bdelacretaz], I still see no benefit in moving the remaining modules into a single Git repo. The modules evolve independently. Sometimes we improve the tests and sometimes we adjust the supporting bundles. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074431#comment-17074431 ] Robert Munteanu commented on SLING-7935: The main driver for consolidating the modules is to make it simpler to release the Sling Starter. I think, based on input from everyone, a scheme that would work is: - moving the 'testing' module - a test launcher - into the Sling Starter - consolidating all other modules into a single git repository, with a standalone lifecycle, independent of the Sling Starter This way we get - the benefit of easily launching the tests from the Starter Module - a way of reusing the tests from the Karaf ITs - simpler release management for the Sling Starter WDYT? > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074392#comment-17074392 ] Bertrand Delacretaz commented on SLING-7935: I think the idea with running the Launchpad integration tests as part of the Starter build is to detect issues earlier, without having to wait for a "distant" build to fail. I like that idea. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074357#comment-17074357 ] Oliver Lietz commented on SLING-7935: - [~rombert], [~bdelacretaz], [~kwin], If we now agree on a final soft freeze (only bug fixing and adjusting support modules to newer Sling) we should keep the modules as is and not consolidate, right? > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073566#comment-17073566
]
Oliver Lietz commented on SLING-7935:
-
[~bdelacretaz], Sure. Moving {{.testing}} into Starter makes failing tests
hopefully more visible.
> 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073558#comment-17073558
]
Oliver Lietz commented on SLING-7935:
-
[~rombert], Yes, you are right.
{{[org.apache.sling.karaf-launchpad-oak-tar-integration-tests|https://github.com/apache/sling-org-apache-sling-karaf-launchpad-oak-tar-integration-tests]}}
is equivalent to
{{[org.apache.sling.launchpad.testing|https://github.com/apache/sling-org-apache-sling-launchpad-testing]}}.
The full list of testing modules used by
{{org.apache.sling.karaf-launchpad-oak-tar-integration-tests}}:
* {{org.apache.sling.launchpad.integration-tests}}
* {{org.apache.sling.junit.core}}
* {{org.apache.sling.junit.remote}}
* {{org.apache.sling.junit.scriptable}}
* {{org.apache.sling.launchpad.test-services}}
* {{org.apache.sling.launchpad.test-fragment}}
* {{org.apache.sling.testing.tools}}
> 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073556#comment-17073556 ] Bertrand Delacretaz commented on SLING-7935: bq. ...Launchpad ITs are a moving target which is hard to track also because new tests are added for snapshots That used to be a problem but recently we've been adding ITs closer to or directly in the modules that they test, AFAICS the last addition of a test there was in January 2019, [commit 3da37cc96|https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/3da37cc963fa1367d07eb1ed2d37cb3296d6b270]. These tests are very important to preserve backwards compatibility IMO but nowadays we have better ways to implement ITs in their own modules. I think it would be reasonable to declare the Launchpad ITs as "frozen legacy integration tests" that we don't touch except to fix the tests themselves if really needed, and declare that new ITs go elsewhere. Would that help with you concern about ITs being a moving target? > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073528#comment-17073528 ] Robert Munteanu commented on SLING-7935: [~olli] - IIUC, you are reusing the launchpad _tests_ right? You would not be impacted if we moved launchpad _testing_ into the starter module? This would allow us to reuse the launcher, but the tests stay independent. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072978#comment-17072978 ] Konrad Windszus commented on SLING-7935: [~olli] Would it be ok, if we for now just start with merging org-apache-sling-launchpad-testing into sling-starter? > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865569#comment-16865569 ] Robert Munteanu commented on SLING-7935: [~olli] - I will start the release now, sorry for the delay. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863348#comment-16863348 ] Oliver Lietz commented on SLING-7935: - [~rombert], yes – that would be enough. Will you do the release or should I do it? Both is fine for me. Thanks. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863130#comment-16863130 ] Robert Munteanu commented on SLING-7935: [~olli] - is it enough if I revert [sling-org-apache-sling-launchpad-integration-tests commit 02439fd|https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/02439fd] and release it with 1.0.10, which would've been the next version before the numbering change? > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862368#comment-16862368
]
Oliver Lietz commented on SLING-7935:
-
[~rombert], can we please switch back to individual versions until all
module-specific tests are moved and release
{{org.apache.sling.launchpad.integration-tests}}?
> 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678424#comment-16678424 ] Robert Munteanu commented on SLING-7935: [~olli] - that's something I hadn't considered before, sorry. My medium-term plan is the following ( will send a proposal to dev@ before starting work on it ): - extract integration tests for specific bundles and move then to the respective bundle - run those ITs alongside the bundle in the regular build (this is IMO the big win) - in the launchpad-testing module, collect IT modules for modules part of the starter and run then like we do today In this scenario, the tests will be released with the bundle, so you will always refer to then by a released version. Would that work for you? > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663523#comment-16663523
]
Oliver Lietz commented on SLING-7935:
-
[~rombert], the modules are referenced from
{{org.apache.sling.karaf-launchpad-oak-tar-integration-tests}}. Snapshot
dependencies are not practically as new tests are added steadily and often only
work with (non-testing) snapshot dependencies in features/starter.
> 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663502#comment-16663502 ] Robert Munteanu commented on SLING-7935: [~olli] - do you need to reference it outside the launchpad-testing modules? You should just use snapshot depedencies. > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[
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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657466#comment-16657466 ] Robert Munteanu commented on SLING-7935: Unified versions in > 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)
[jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
[ https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657068#comment-16657068 ] Robert Munteanu commented on SLING-7935: As a first step I will change the projects to have the same version. It makes life much easier when releasing anyway and we only release them alongside the starter. > 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)
