[jira] [Resolved] (STANBOL-806) Move all bundlelists into /launchers/bundlelists

["Fabian Christ (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STANBOL-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabian Christ resolved STANBOL-806.
-----------------------------------

    Resolution: Fixed
    
> Move all bundlelists into /launchers/bundlelists
> ------------------------------------------------
>
>                 Key: STANBOL-806
>                 URL: https://issues.apache.org/jira/browse/STANBOL-806
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Fabian Christ
>            Assignee: Fabian Christ
>              Labels: release
>             Fix For: parent-2
>
>
> Currently, the bundlelists of different components are located along with the components, e.g. /enhancer/bundlelist.
> From a release management point of view it is not so easy to keep track of the right versions in the bundlelists when a component gets released. For example, the automated release process will only check for SNAPSHOT deps in the pom.xml files and not in the list.xml files. The list.xml can not be updated automatically. The practice in the past has proven that releases get published which have deps to SNAPSHOT versions in the bundlelists. This should be avoided.
> Bundlelist belong logically to launcher configurations which make use of certain bundlelists to keep the configuration more modular. Therefore, we should move all bundleslists from the components to /launchers/bundlelists.
> With this change the release manager does not need to keep track of required changes to the bundelists. Instead, the bundlelists should be updated after a release is published. The release process and cycles of launchers+bundlelists and the components is decoupled. This makes releasing of different launchers with different bundlelists also more flexible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira