[
https://issues.apache.org/jira/browse/JCLOUDS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241725#comment-14241725
]
Ignasi Barrera commented on JCLOUDS-104:
----------------------------------------
Having a look at the repos:
* jclouds-chef repo is deprecated, so nothing to do there.
* jclouds-cli is OK.
* jclouds-karaf uses its own parent pom and is not using the aggregate javadocs
plugin, so shouldn't present issues when releasing with Maven.
* jclouds-labs needs to be changed.
* jclouds-labs-aws has some projects OK and some that have to be changed.
* jclouds-labs-google has to be changed too.
The changes to be applied to the remaining repos are:
* Change each individual project in the repo, and the root pom.xml to use
{{jclouds-project}} as a parent.
* Replace all occurrences of {{jclouds.version}} by {{project.parent.version}}.
The jclouds-labs-openstack repo can be used as a model to apply the changes.
As [~abayer] says, the issue is having projects depending on the "aggregator"
pom.xml (the root pom.xml in the repo). As the parent pom gets build first, if
it "does stuff" such as generating the aggregate javadocs, weird things will
happen, as that will run *before* the build of the child repos is done.
> 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
> 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.3.4#6332)
