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/13 09:13:21 UTC
[jira] [Updated] (OAK-4446) Release oak-segment-tar
[ https://issues.apache.org/jira/browse/OAK-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Mari updated OAK-4446:
--------------------------------
Attachment: OAK-4446-01.patch
In [^OAK-4446-01.patch] I outline the changes that should be performed to our build files to have independent releases of {{oak-segment-tar}}. In particular:
# {{oak-segment-tar}} uses non-snapshot versions for its parent POM and its dependencies.
# every module in oak using {{oak-segment-tar}} depends on a specific version of that module.
# a workaround is implemented in the POM in {{oak-segment-tar}} to release the module. This workaround, still to be verified, forces the release manager of {{oak-segment-tar}} to activate a profile on the command line when the {{release:perform}} goal is invoked.
I will add additional documentation as soon as I figure out the raw edges of this solution.
> Release oak-segment-tar
> -----------------------
>
> Key: OAK-4446
> URL: https://issues.apache.org/jira/browse/OAK-4446
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Francesco Mari
> Labels: release
> Attachments: OAK-4446-01.patch
>
>
> Tweak our setup in order to be able to cut an initial release of {{oak-segment-tar}} and perform the release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)