Ok, so it seems the parent POM was the wrong clue after all.
This issue here
http://issues.hudson-ci.org/browse/HUDSON-5519
looks much like ours, except that we're not running on a JDK 5.
From what Toni posted a while ago, the default JDK on Hudson *should*
be a JDK 6.
Anyway, I just changed the JDK for the Pax Web Job to JDK 7, and now the
job is running again...
Regards,
Harald
Am 08.06.2012 20:21, schrieb Achim Nierbeck:
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
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
