I did a build on another machine with nexus turned off and reproduced this problem.
We (karaf people) think that it's due to aether expecting maven metadata in the karaf system repository and ignoring any artifacts there not represented by metadata, and downloading a remote older version of the snapshot. I did not see this because I have my local nexus configured to not download any geronimo artifacts. It's still not entirely clear why aether would prefer an older copy from apache-snapshots to a newer copy in the ~/.m2/repository repo. This might be due to a bug in the old version of aether embedded in pax-url-aether. thanks david jencks On Jan 12, 2012, at 4:43 AM, Forrest Xia wrote: > > > On Thu, Jan 12, 2012 at 3:29 PM, David Jencks <[email protected]> wrote: > I have seen problems like this sometimes. I wonder if the pax-url and karaf > snapshots are up to date? > I locally built karaf, but no pax-url, will retry. > That might result in old artifacts (not from the build you just did) getting > downloaded and installed in the framework rather than the ones in the server > /system repo. You might also be able to use the console to investigate why > geronimo-system won't start. The log (now at data/log/karaf.log) might show > something also. > > I'll see if I can find some time tomorrow to run a build on another machine > and see what happens. > > thanks > david jencks > > > > On Jan 11, 2012, at 9:58 PM, Forrest Xia wrote: > >> Made a build bypassing the test, but failed to start server with this >> exception: >> >> Module 1/62 org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car >> Server Startup failed >> >> org.apache.geronimo.kernel.config.LifecycleException: load of >> org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car failed >> at >> org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:389) >> at >> org.apache.geronimo.system.main.EmbeddedDaemon$1.run(EmbeddedDaemon.java:261) >> Caused by: org.osgi.framework.BundleException: Unresolved constraint in >> bundle org.apache.geronimo.framework.j2ee-system [129]: Unable to resolve >> 129.0: missing requirement [129.0] osgi.wiring.package; >> (osgi.wiring.package=org.apache.geronimo.system.osgi) >> at >> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826) >> at org.apache.felix.framework.Felix.startBundle(Felix.java:1868) >> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944) >> at >> org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(SimpleConfigurationManager.java:380) >> ... 1 more >> >> >> On Tue, Jan 10, 2012 at 11:13 PM, Kevan Miller <[email protected]> >> wrote: >> >> Looks like there's a new build issue -- >> http://ci.apache.org/builders/geronimo-server-trunk/builds/506/steps/compile/logs/stdio >> >> --kevan >> >> >> >> -- >> Thanks! >> >> Regards, Forrest >> > > > > > -- > Thanks! > > Regards, Forrest >
