[
https://issues.apache.org/jira/browse/STANBOL-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Christ resolved STANBOL-553.
-----------------------------------
Resolution: Fixed
> Remove dependency management for org.apache.stanbol components from parent POM
> ------------------------------------------------------------------------------
>
> Key: STANBOL-553
> URL: https://issues.apache.org/jira/browse/STANBOL-553
> Project: Stanbol
> Issue Type: Improvement
> Components: Build
> Affects Versions: 0.9.0-incubating
> Reporter: Fabian Christ
> Assignee: Fabian Christ
> Labels: Release, Version
>
> We manage the versions of all POMs using the Maven dependency management
> feature in the parent POM. This includes the versions of all
> org.apache.stanbol components.
> This has one drawback when we want to release single components
> independently. For sure we will have big source releases from time to time,
> but the short improvements should be developed on a per component base. If we
> keep on managing the versions of org.apache.stanbol components within the
> parent POM, we will have to release the parent POM each time we want to
> release a single component. Additionally, the parent POM may include several
> SNAPSHOT versions of org.apache.stanbol components. In this case, all the
> SNAPSHOT components need to be released, too. The reason is that we can not
> release a parent POM with SNAPSHOT dependencies.
> To solve this problem, we should manage the version of each
> org.apache.stanbol component in its own POM and make it therefore independent
> of the parent POM. The parent POM is only used to manage the versions to
> third party artifacts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
