Andrew Bayer created JCLOUDS-104:
------------------------------------
Summary: 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: Andrew Bayer
Fix For: 1.7.0, 1.5.11, 1.6.2
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
