Re: [GUMP@vmgump]: Project fulcrum-quartz-test (in module turbine-fulcrum) failed
Hi General Gump, On 19.11.11 05:33, fulcrum-quartz development wrote: > The following work was performed: > http://vmgump.apache.org/gump/public/turbine-fulcrum/fulcrum-quartz-test/gump_work/build_turbine-fulcrum_fulcrum-quartz-test.html > Work Name: build_turbine-fulcrum_fulcrum-quartz-test (Type: Build) > Work ended in a state of : Failed > Elapsed: 6 secs > Command Line: /opt/maven2/bin/mvn --batch-mode --settings > /srv/gump/public/workspace/turbine-fulcrum/quartz/gump_mvn_settings.xml test > [Working Directory: /srv/gump/public/workspace/turbine-fulcrum/quartz] > M2_HOME: /opt/maven2 > - > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > Caused by: java.lang.IllegalStateException: org.slf4j.LoggerFactory could not > be successfully initialized. See also > http://www.slf4j.org/codes.html#unsuccessfulInit > at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) > at > org.quartz.impl.StdSchedulerFactory.(StdSchedulerFactory.java:274) > at > org.apache.fulcrum.quartz.impl.QuartzSchedulerImpl.initialize(QuartzSchedulerImpl.java:114) > at > org.apache.fulcrum.yaafi.framework.component.AvalonServiceComponentImpl.initialize(AvalonServiceComponentImpl.java:404) > at > org.apache.fulcrum.yaafi.framework.component.AvalonServiceComponentImpl.incarnateInstance(AvalonServiceComponentImpl.java:106) > at > org.apache.fulcrum.yaafi.framework.component.ServiceComponentImpl.getInstance(ServiceComponentImpl.java:139) > at > org.apache.fulcrum.yaafi.framework.component.ServiceComponentImpl.incarnate(ServiceComponentImpl.java:154) > ... 31 more > Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.636 sec <<< > FAILURE! Could some kind soul enlighten me, WTF is going on here again? Is this a topic we can fix? Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 5 notifys should have been sent *** G U M P [GUMP@vmgump]: Project objenesis (in module objenesis) failed [GUMP@vmgump]: Project lucene-java-contrib-test (in module lucene-java) failed [GUMP@vmgump]: Project tika-parsers (in module tika) failed [GUMP@vmgump]: Project james-protocols (in module james-protocols) failed [GUMP@vmgump]: Project commons-jelly-tags-ant-test (in module commons-jelly) failed *** G U M P [GUMP@vmgump]: Project objenesis (in module objenesis) failed To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at general@gump.apache.org. Project objenesis has an issue affecting its community integration. This issue affects 2 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jmock2-test : jMock is a library for testing Java code using mock objects. - objenesis : Objenesis is a small Java library that serves one purpose: T... Full details are available at: http://vmgump.apache.org/gump/public/objenesis/objenesis/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [objenesis-*[0-9T].jar] identifier set to project name -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/objenesis/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/objenesis/pom.xml -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/objenesis/objenesis/gump_work/build_objenesis_objenesis.html Work Name: build_objenesis_objenesis (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 27 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/objenesis/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/objenesis] M2_HOME: /opt/maven2 - Downloading: http://repository.springsource.com/maven/bundles/release/org/springframework/osgi/log4j.osgi/1.2.15-SNAPSHOT/log4j.osgi-1.2.15-SNAPSHOT.jar [INFO] Unable to find resource 'org.springframework.osgi:log4j.osgi:jar:1.2.15-SNAPSHOT' in repository com.springsource.repository.bundles.release (http://repository.springsource.com/maven/bundles/release) Downloading: http://repository.springsource.com/maven/bundles/external/org/springframework/osgi/log4j.osgi/1.2.15-SNAPSHOT/log4j.osgi-1.2.15-SNAPSHOT.jar [INFO] Unable to find resource 'org.springframework.osgi:log4j.osgi:jar:1.2.15-SNAPSHOT' in repository com.springsource.repository.bundles.external (http://repository.springsource.com/maven/bundles/external) Downloading: http://maven.springframework.org/osgi/org/springframework/osgi/log4j.osgi/1.2.15-SNAPSHOT/log4j.osgi-1.2.15-SNAPSHOT.jar [INFO] Unable to find resource 'org.springframework.osgi:log4j.osgi:jar:1.2.15-SNAPSHOT' in repository i21-s3-osgi-repo (http://maven.springframework.org/osgi) 465K downloaded (org.springframework.context-2.5.6.A.jar) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.springframework.osgi:log4j.osgi:jar:1.2.15-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.springframework.osgi -DartifactId=log4j.osgi -Dversion=1.2.15-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.springframework.osgi -DartifactId=log4j.osgi -Dversion=1.2.15-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.objenesis:objenesis-tck:jar:1.2 2) org.springframework.osgi:log4j.osgi:jar:1.2.15-SNAPSHOT -- 1 required artifact is missing. for artifact: org.objenesis:objenesis-tck:jar:1.2 from the specified remote repositories: com.springsource.repository.bundles.release (http://repository.springsource.com/maven/bundles/release), com.springsource.repository.bundles.external (http://repository.springsource.com/maven/bundles/external), gump-central (http://localhost:8192/maven2), i21-s3-osgi-repo (http://maven.springframework.org/osgi), spring-ext (http://springframework.svn.sourceforge.net/svnroot/springframework/repos/repo-ext/) [INFO] --
Re: [GUMP@vmgump]: Project fulcrum-quartz-test (in module turbine-fulcrum) failed
Hi Thomas, On 2011-11-19, Thomas Vandahl wrote: >> Caused by: java.lang.IllegalStateException: org.slf4j.LoggerFactory could >> not be successfully initialized. See also >> http://www.slf4j.org/codes.html#unsuccessfulInit >> at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275) >> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) >> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) >> at >> org.quartz.impl.StdSchedulerFactory.(StdSchedulerFactory.java:274) >> at >> org.apache.fulcrum.quartz.impl.QuartzSchedulerImpl.initialize(QuartzSchedulerImpl.java:114) >> at >> org.apache.fulcrum.yaafi.framework.component.AvalonServiceComponentImpl.initialize(AvalonServiceComponentImpl.java:404) >> at >> org.apache.fulcrum.yaafi.framework.component.AvalonServiceComponentImpl.incarnateInstance(AvalonServiceComponentImpl.java:106) >> at >> org.apache.fulcrum.yaafi.framework.component.ServiceComponentImpl.getInstance(ServiceComponentImpl.java:139) >> at >> org.apache.fulcrum.yaafi.framework.component.ServiceComponentImpl.incarnate(ServiceComponentImpl.java:154) >> ... 31 more > Could some kind soul enlighten me, WTF is going on here again? I'm not sure. The major difference between a local build and Gump is the version of dependencies you pull in. This means you likely get a more recent version of SLF4J or Quartz than you have asked for and maybe this newer version needs some additional configuration. Looking through http://www.slf4j.org/codes.html#unsuccessfulInit and looking at http://vmgump.apache.org/gump/public/turbine-fulcrum/fulcrum-quartz-test/gump_work/build_turbine-fulcrum_fulcrum-quartz-test.html which has a java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder pretty far at the top of the log it may be a case of a missing binding. fulcrum-quartz doesn't seem to specifiy a dependency on SLF4J at all, so you pull it in via a transitive dependency. You depend on Quartz 2.0.0 whose POM depends on SLF4J but only the api dependency is non-optional. I don't know for sure how transitive dependendcies work in Maven but guess you don't inherit the optional slf4j-log4j binding. If it works for a local build then the most likely reason is some sort of change in SLF4J that it now requires one of the bindings to be available and didn't require it in the version you get locally. > Is this a topic we can fix? Not sure, it depends on whether you want to take explicit control over logging (I think you should, but don't know enough about fulcrum or even fulcrum-quartz) and provide some sort of slf4j binding (as optional dependency, I guess). If you don't want to do that then I currently don't see what you could do. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
