jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-104) Change labs/cli/karaf to have their own parent POMs separate from the top-level POM
Date Fri, 22 Nov 2013 06:37:35 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829702#comment-13829702
] 

ASF subversion and git services commented on JCLOUDS-104:
---------------------------------------------------------

Commit 8a43a4dbcb263cc83dae7bab33e8bce7afd3e2fc in branch refs/heads/master from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-cli.git;h=8a43a4d ]

JCLOUDS-104: Cleaning up CLI POMs

* module jclouds-cli-project -> project
* removing unnecessary duplicate versions and group IDs
* adding an explicit version tag to the project POM to allow the jclouds-cli version to be
different from jclouds-project

Follow-on from bb56570


> 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.0, 1.5.11, 1.6.4
>
>         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.1#6144)

Mime
View raw message