Hi All, sorry for being so unspecific :)
Harald is right though this issue is not only in the 80s build but already an issue with http://ci.ops4j.org/hudson/job/org.ops4j.pax.web/79/console from the 29th of Mai (though something changed then with pax-url) and also with http://ci.ops4j.org/hudson/job/org.ops4j.pax.vaadin/7/console might be an co-incident that both modules somehow depended on Pax URL with the master pom issue. we should find a way around this for the future since this will be an issue the next time someone upgrades the master pom :) regards, Achim Am 08.06.2012 19:31, schrieb Harald Wellmann: > Hmm, I suspect Achim was referring to this one here: > > http://ci.ops4j.org/hudson/job/org.ops4j.pax.web/80/console > > I vaguely remember having seen that before, and I think it's a known > bug related to parent POM resolution. > > Could it be that Pax Web references Pax URL which references the new > Master POM which is not yet on Maven Central and not in Hudson's local > repo either? > > Regards, > Harald > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general -- ----- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
