You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Tomek Rekawek <re...@adobe.com> on 2016/06/06 13:01:16 UTC

deploying oak-segment-tar to nexus

Hello,

I’ve noticed that the maven-deploy-plugin is disabled for the oak-segment-tar. As a result, the 1.5.2 release is not quite consistent (oak-jcr and oak-upgrade depend on the oak-segment-tar, which isn’t available in the remote repository). Should we re-enable the plugin before the 1.5.3 release?

Best regards,
Tomek

-- 
Tomek Rękawek | Adobe Research | www.adobe.com
rekawek@adobe.com

Re: deploying oak-segment-tar to nexus

Posted by Tomek Rekawek <re...@adobe.com>.
Hi Francesco,

thanks for the clarification, it makes sense.

Best regards,
Tomek

-- 
Tomek Rękawek | Adobe Research | www.adobe.com
rekawek@adobe.com

> On 06 Jun 2016, at 15:23, Francesco Mari <ma...@gmail.com> wrote:
> 
> The maven-deploy-plugin is disabled for oak-segment-tar to avoid that
> module from being released. We didn't agree on the release policy for that
> module. In particular, is not clear to us if oak-segment-tar should be
> released during the biweekly release process or if it should be released
> independently.
> 
> About the concrete dependencies, oak-jcr depends on oak-segment-tar for
> testing purposes only, while oak-upgrade seems to embed oak-segment-tar.
> Unless the missing release of oak-segment-tar creates major problems to the
> rest of the project, I would ask to leave the situation as is for a little
> longer.
> 
> 2016-06-06 15:01 GMT+02:00 Tomek Rekawek <re...@adobe.com>:
> 
>> Hello,
>> 
>> I’ve noticed that the maven-deploy-plugin is disabled for the
>> oak-segment-tar. As a result, the 1.5.2 release is not quite consistent
>> (oak-jcr and oak-upgrade depend on the oak-segment-tar, which isn’t
>> available in the remote repository). Should we re-enable the plugin before
>> the 1.5.3 release?
>> 
>> Best regards,
>> Tomek
>> 
>> --
>> Tomek Rękawek | Adobe Research | www.adobe.com
>> rekawek@adobe.com
>> 
>>

Re: deploying oak-segment-tar to nexus

Posted by Francesco Mari <ma...@gmail.com>.
The maven-deploy-plugin is disabled for oak-segment-tar to avoid that
module from being released. We didn't agree on the release policy for that
module. In particular, is not clear to us if oak-segment-tar should be
released during the biweekly release process or if it should be released
independently.

About the concrete dependencies, oak-jcr depends on oak-segment-tar for
testing purposes only, while oak-upgrade seems to embed oak-segment-tar.
Unless the missing release of oak-segment-tar creates major problems to the
rest of the project, I would ask to leave the situation as is for a little
longer.

2016-06-06 15:01 GMT+02:00 Tomek Rekawek <re...@adobe.com>:

> Hello,
>
> I’ve noticed that the maven-deploy-plugin is disabled for the
> oak-segment-tar. As a result, the 1.5.2 release is not quite consistent
> (oak-jcr and oak-upgrade depend on the oak-segment-tar, which isn’t
> available in the remote repository). Should we re-enable the plugin before
> the 1.5.3 release?
>
> Best regards,
> Tomek
>
> --
> Tomek Rękawek | Adobe Research | www.adobe.com
> rekawek@adobe.com
>
>