[jira] [Commented] (SLING-7935) Move launchpad-testing module into the main starter repository

["Robert Munteanu (Jira)" <ji...@apache.org>]

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

Robert Munteanu commented on SLING-7935:
----------------------------------------

The main changes are in, all that is left IMO is to deprecate the launchpad-testing repository.

> Move launchpad-testing module into the main starter 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
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> The functionality from the launchpad-testing module can be moved into the main starter repository, meaning we'll have one less module to release for the Starter and that we can run all integration tests with the main starter job.
> -----
> _Old description_:
> 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.7#820007)