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/22 12:42:57 UTC

[jira] [Resolved] (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 resolved OAK-4487.
---------------------------------
    Resolution: Won't Fix

The steps in the {{apache-release}} profile in the main reactor POM are irrelevant for the release of a single module. Moreover, the fix for OAK-4488 excludes oak-segment-tar from the default release process of Oak. 

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