I guess this is a question for Carlos; Look at http://ci.ops4j.org/bamboo/build/viewBuildLog.action?buildKey=PAX-CLIN&buildNumber=113
At the end, you will see that Pax Wicket Toolkit fails due to Pax Wicket Service 0.5.0-SNAPSHOT is missing, but it is being built a couple of projects earlier. The problem is the following 23-Apr-2007 05:34:47 [INFO] Installing /var/bamboo/xml-data/build-dir/ PAX-CLIN/wicket/service/target/ service-0.5.0-SNAPSHOT.jar to /home/ tomcat/.m2/repository/org/ops4j/pax/wicket/service/ 0.5.0-SNAPSHOT/ service-0.5.0-SNAPSHOT.bundle The Pax Wicket Service is installed with a "bundle" extension, and the Pax Wicket Toolkit is looking for; 23-Apr-2007 05:34:52 1) org.ops4j.pax.wicket:service:jar:0.5.0-SNAPSHOT a JAR. Well, that is not completely unexpected, but then let's look at http://ci.ops4j.org/bamboo/build/viewBuildLog.action?buildKey=PAXWICKET-DEFAULT&buildNumber=7 This is the same sources being built. But here the Pax Wicket Service is installed as a ".jar" and NOT a ".bundle" 23-Apr-2007 05:47:10 [INFO] Installing /var/bamboo/xml-data/build-dir/ PAXWICKET-DEFAULT/service/target/ service-0.5.0-SNAPSHOT.jar to /home/ tomcat/.m2/repository/org/ops4j/pax/wicket/service/ 0.5.0-SNAPSHOT/ service-0.5.0-SNAPSHOT.jar And the only difference is that in case one, the build is done from pax/ and the second one is built from pax/wicket/ Somewhere along the line, Maven looses track of the mapping between the "bundle" type and the "jar" extension. Any clue what is going on?? Oh, and if I declare the dependency in Toolkit for Service to be <type>bundle</type>, then the first case will work and the second will fail. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug
