Hi, We are using Archiva repository to locally store all the jars needed for projects. Archiva can automatically download jars from http://mvnrepository.com/ when there are jar files not found in the archiva repo. So, I have tried to run camel:dot and we are unable to download org.springframework.config.java with version 1.0.0-20090215 from archiva. The mvnrepository site only has 1.0.0-m3 version. Unfortunately i have come to know that, camel-spring-javaconfig (2.1.0) is referencing to version 1.0.0-20090215. So, even if i use 1.0.0-m3, it won't resolve the issue. So, i have manually added org.springframework.config.java/1.0.0-20090215 in my local machine repository just to get it working. Then i moved on to next problem where camel maven plugin has transitive dependency to groupid = org.springframework.context, version =2.5.6 but our archiva has groupid = org.springframework and artifactid =spring-context ... I thought it would be silly to add org.springframework.context groupid in archiva when jar file already exist in the groupid = org.springframework, artifactid= spring-context. What is the standard for naming artifacts and groupid ? I am finding it hard to deal with camel dependencies and run mvn camel:dot. Can you please advise how i can resolve this issue? Any hints greatly appreciated.
Regards, -Vid- -- View this message in context: http://old.nabble.com/Maven-repository-tp27618995p27618995.html Sent from the Camel - Users mailing list archive at Nabble.com.
