You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/10/19 16:48:00 UTC
[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)