[
https://issues.apache.org/jira/browse/JCLOUDS-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240367#comment-14240367
]
Andrew Phillips commented on JCLOUDS-141:
-----------------------------------------
> Is this still an open issue?
Thanks for the ping, [~broudy]. At the current moment, I'd say "no, it's not."
If projects want to inherit from a jclouds "top-level POM" they should use
jclouds-project.
That's not to say that there isn't plenty of cleanup to do in the individual
repo POMs, but as far as I am aware that currently doesn't involve creating a
new Top-Level Pom To Rule Them All.
> 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
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
