sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7935) Consolidate all 'launchpad-testing' modules into a single git repository
Date Fri, 03 Apr 2020 09:22:00 GMT

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

Mime
View raw message