You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Francesco Mari (JIRA)" <ji...@apache.org> on 2016/06/20 13:21:05 UTC
[jira] [Updated] (OAK-4487) Move the apache-release profile in
oak-parent
[ https://issues.apache.org/jira/browse/OAK-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Mari updated OAK-4487:
--------------------------------
Description:
The {{apache-release}} profile in the root POM defines some required steps to build release artifacts in Oak. This profile should be moved to the POM in {{oak-parent}} so that these steps can be shared between different modules.
As a concrete example, oak-segment-tar should be able to reuse these steps to be compliant with our release process. For further details, see OAK-4446.
was:
The {{apache-release}} profile in the root POM defines some required steps to build release artifacts in Oak. This profile should be moved to the POM in {{oak-parent}} so that these steps can be shared between different modules.
As a concrete example, oak-segment-tar should be able to reuse these steps to be compliant with our release process. For further detail, see OAK-4446.
> Move the apache-release profile in oak-parent
> ---------------------------------------------
>
> Key: OAK-4487
> URL: https://issues.apache.org/jira/browse/OAK-4487
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: parent
> Reporter: Francesco Mari
> Assignee: Francesco Mari
> Fix For: 1.6
>
>
> The {{apache-release}} profile in the root POM defines some required steps to build release artifacts in Oak. This profile should be moved to the POM in {{oak-parent}} so that these steps can be shared between different modules.
> As a concrete example, oak-segment-tar should be able to reuse these steps to be compliant with our release process. For further details, see OAK-4446.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)