[
https://issues.apache.org/jira/browse/OAK-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339560#comment-15339560
]
Julian Sedding commented on OAK-4488:
-------------------------------------
Maybe after moving the {{apache-release}} profile as suggested in OAK-4487 to
oak-parent, you can create a new {{apache-release}} profile in the reactor pom
that lists all modules of the "bulk release" and overwrites the default
{{modules}} section. I.e. list all modules except {{oak-segment-tar}} in that
profile.
> Create separate reactor POM to perform releases
> -----------------------------------------------
>
> Key: OAK-4488
> URL: https://issues.apache.org/jira/browse/OAK-4488
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: parent
> Reporter: Francesco Mari
> Assignee: Julian Sedding
> Fix For: 1.6
>
>
> Releases are currently performed from the root reactor POM. This triggers the
> execution of the {{release:prepare}} and {{release:perform}} goals on every
> module referenced from the reactor.
> This approach prevents the individual release of some sub-modules. To enable
> individual releases, the least disruptive approach would be the creation of
> another reactor POM to reference every module in Oak that needs to be
> released in one big bulk. In example, {{oak-release/pom.xml}} or something
> along these lines.
> The current reactor POM will remain untouched and will still reference every
> module in the project. This way, we will not have to change configuration of
> CI jobs out there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
