You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Zack Shoylev (JIRA)" <ji...@apache.org> on 2014/03/08 01:14:43 UTC
[jira] [Commented] (JCLOUDS-104) Change labs/cli/karaf to have
their own parent POMs separate from the top-level POM
[ https://issues.apache.org/jira/browse/JCLOUDS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924542#comment-13924542 ]
Zack Shoylev commented on JCLOUDS-104:
--------------------------------------
So what actually still remains to be fixed?
> 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.2
>
> 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.2#6252)