[
https://issues.apache.org/jira/browse/JCLOUDS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692226#comment-13692226
]
Ignasi Barrera commented on JCLOUDS-141:
----------------------------------------
If the existing jclouds/project/pom.xml works, I'd prefer using it rather than
having a new super-pom. To do things properly, it would make sense to have it
in a new git repository (if we placed it in the jclouds repo, why having the
project/pom and the new super-pom? sounds a bit weird to me), but that would
introduce unnecessary complexity.
If possible, I'd prefer to use the existing one.
> Create super-parent POM that jclouds and other components inherit from
> ----------------------------------------------------------------------
>
> Key: JCLOUDS-141
> URL: https://issues.apache.org/jira/browse/JCLOUDS-141
> Project: jclouds
> Issue Type: Task
> Components: jclouds-chef, jclouds-cli, jclouds-core, jclouds-karaf,
> jclouds-labs, jclouds-labs-aws, jclouds-labs-google, jclouds-labs-openstack
> Affects Versions: 1.6.1
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Fix For: 1.7.0, 1.5.11, 1.6.2
>
>
> Now that we release all the components at once, it'd make sense to have one
> common super-parent POM they all inherited from, where we can define the
> version (so we don't have to update properties in chef/cli/karaf/etc when
> jclouds' version changes, etc) and the like. It'd make releasing simpler.
--
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
