[
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)
