jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Phillips (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 Mon, 09 Dec 2013 20:20:12 GMT

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

Andrew Phillips commented on JCLOUDS-104:
-----------------------------------------

With the recent change to jclouds-cli, which ones are still open here? Can we split any remaining
ones out into a separate issue and close this for 1.7.0?

> 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
>             Fix For: 1.7.0, 1.5.11, 1.6.4
>
>         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.1.4#6159)

Mime
View raw message