[
https://issues.apache.org/activemq/browse/CAMEL-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61440#action_61440
]
Daniel Bevenius commented on CAMEL-3018:
----------------------------------------
I'm having issues when using maven3 as well. I get the following;
c-dc9ee055:camel-web danbev$ mvn clean install
[INFO] Scanning for projects...
[INFO] snapshot org.apache.camel:camel-parent:2.5-SNAPSHOT: checking for
updates from java.net.m2
[INFO] snapshot org.apache.camel:camel-parent:2.5-SNAPSHOT: checking for
updates from fusesource.snapshots
[INFO] snapshot org.apache.camel:camel:2.5-SNAPSHOT: checking for updates from
java.net.m2
[INFO] snapshot org.apache.camel:camel:2.5-SNAPSHOT: checking for updates from
fusesource.snapshots
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR] The project org.apache.camel:camel-web:2.5-SNAPSHOT
(/Users/danbev/work/apache/camel/trunk/components/camel-web/pom.xml) has 1 error
[ERROR] 'repositories.repository.id' must be unique: glassfish-repo-archive
-> http://maven.glassfish.org/content/groups/glassfish vs
http://maven.glassfish.org/content/groups/glassfish
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
There is indeed a duplicate in components/web/pom.xml (pom.patch attached).
Using the patch I'm able to build but I get failures during the test phase
which I'm looking into at the moment.
> Building not possible with maven3
> ---------------------------------
>
> Key: CAMEL-3018
> URL: https://issues.apache.org/activemq/browse/CAMEL-3018
> Project: Apache Camel
> Issue Type: Bug
> Reporter: Norman Maurer
> Assignee: Claus Ibsen
> Fix For: 2.5.0
>
> Attachments: camel-pom.diff
>
>
> maven3 is a way stricter with duplicated specified dependencies, so its not
> possible to compile camel with it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
