[
https://issues.apache.org/jira/browse/BROOKLYN-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280091#comment-14280091
]
Aled Sage commented on BROOKLYN-86:
-----------------------------------
Thanks for reporting, including the workaround for 0.7.0-M1. Unfortunately
there's no fix we can give for the old 0.7.0-M1 (because it's already
released), other than recommending your workaround.
However, this has been resolved in 0.7.0-M2, with moving to apache and thus
maven groupIds changing. The camp modules are now all inside the brooklyn repo,
and share the same version number as brooklyn itself.
> brooklyn-all include camp-base as dependency.
> ---------------------------------------------
>
> Key: BROOKLYN-86
> URL: https://issues.apache.org/jira/browse/BROOKLYN-86
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.7.0-M1
> Reporter: David Medinets
> Priority: Minor
>
> When using the following in my pom.xml, maven tries to find
> io.brooklyn.camp:camp-base:jar:0.1.0-SNAPSHOT.
> {noformat}
> <dependency>
> <groupId>io.brooklyn</groupId>
> <artifactId>brooklyn-all</artifactId>
> <version>0.7.0-M1</version>
> </dependency>
> {noformat}
> I changed my pom.xml to have the following and the issue seems to be resolved:
> {noformat}
> <dependency>
> <groupId>io.brooklyn</groupId>
> <artifactId>brooklyn-all</artifactId>
> <version>0.7.0-M1</version>
> <exclusions>
> <exclusion>
> <groupId>io.brooklyn.camp</groupId>
> <artifactId>camp-base</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>io.brooklyn</groupId>
> <artifactId>brooklyn-camp</artifactId>
> <version>0.7.0-M1</version>
> </dependency>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
