jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-104) Change labs/cli/karaf to have their own parent POMs separate from the top-level POM
Date Thu, 05 Feb 2015 10:10:35 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306946#comment-14306946
] 

Ignasi Barrera commented on JCLOUDS-104:
----------------------------------------

Oops. When I commented on the issue I thought the openstack repos were "release-friendly".
I agree 100% with you that the only purpose of this issue is to make the release process smoother
and non-interactive. So let's do whatever it has to be done to achieve that. Thanks for pointing
Andrew!

> Change labs/cli/karaf to have their own parent POMs separate from the top-level POM
> -----------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-104
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-104
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-cli, jclouds-karaf, jclouds-labs, jclouds-labs-aws, jclouds-labs-google,
jclouds-labs-openstack
>            Reporter: Andrew Bayer
>            Assignee: Zack Shoylev
>         Attachments: JCLOUDS-104-cli.patch
>
>
> Currently, jclouds and jclouds-chef each have a parent POM, (repo)/project/pom.xml, which
all the other POMs, including the top-level POM, in the project inherit from. jclouds-labs*,
jclouds-cli and jclouds-karaf all just have the top-level POM, and everything else inherits
from that top-level POM. That makes some processes (like aggregate javadoc and assemblies)
done in the top-level POM a bit problematic for the first build of a new version (i.e., in
releases). It'd be nice if these projects separated out the parent and top-level POM functionality
as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message