[GUMP@vmgump]: Project logging-log4j-receivers (in module logging-log4j-receivers) 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 gene...@gump.apache.org. Project logging-log4j-receivers has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 14 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - logging-log4j-chainsaw : Chainsaw log viewer - logging-log4j-receivers : Back-port of log4j 1.3 receivers for use with log4j 1.2. - logging-log4j-receivers-test : Back-port of log4j 1.3 receivers for use with log4j 1.2. Full details are available at: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/gump_work/build_logging-log4j-receivers_logging-log4j-receivers.html Work Name: build_logging-log4j-receivers_logging-log4j-receivers (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dproject.version=01092011 jar [Working Directory: /srv/gump/public/workspace/logging-log4j-receivers] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-01092011.jar:/srv/gump/public/workspace/logging-log4j-component/target/apache-log4j-component-01092011.jar:/srv/gump/public/workspace/logging-log4j-extras/target/apache-log4j-extras-01092011.jar:/srv/gump/packages/jms1.1/lib/jms.jar:/srv/gump/packages/apache-attic/oro-2.0.8.jar - Buildfile: /srv/gump/public/workspace/logging-log4j-receivers/build.xml BUILD FAILED Target jar does not exist in the project null. Total time: 0 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/rss.xml - Atom: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 04000601092011, vmgump.apache.org:vmgump:04000601092011 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Companions - Chainsaw?
Scott, Curt had an interesting idea lately, he mentioned it might make sense to move the companions code into chainsaw. What do you think on that? I like the idea - less releases, and no other interested parties in having companions. Please comment, when you can :-) Cheers Christian - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Companions - Chainsaw?
At this point I'm only focusing only on 2.0. I've been wondering if I should create a subproject for chainsaw or if it should remain separate. I already moved a large part of extras in as a core part of the functionality. Ralph On Sep 1, 2011, at 4:13 AM, Christian Grobmeier wrote: Scott, Curt had an interesting idea lately, he mentioned it might make sense to move the companions code into chainsaw. What do you think on that? I like the idea - less releases, and no other interested parties in having companions. Please comment, when you can :-) Cheers Christian - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Companions - Chainsaw?
On Thu, Sep 1, 2011 at 6:15 PM, Scott Deboy scott.de...@gmail.com wrote: I think pulling in component would make sense...no one else probably uses it. Receivers? I suppose if they were built as a separate jar that'd be fine too, I have no idea who uses them if anyone. We can always cut them out again if somebody wants it - which is very unlikely. If you are fine with moving them to chainsaw... do you need any help? Scott On Thu, Sep 1, 2011 at 7:09 AM, Ralph Goers ralph.go...@dslextreme.com wrote: At this point I'm only focusing only on 2.0. I've been wondering if I should create a subproject for chainsaw or if it should remain separate. I already moved a large part of extras in as a core part of the functionality. Ralph On Sep 1, 2011, at 4:13 AM, Christian Grobmeier wrote: Scott, Curt had an interesting idea lately, he mentioned it might make sense to move the companions code into chainsaw. What do you think on that? I like the idea - less releases, and no other interested parties in having companions. Please comment, when you can :-) Cheers Christian - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Companions - Chainsaw?
On Thu, Sep 1, 2011 at 4:09 PM, Ralph Goers ralph.go...@dslextreme.com wrote: At this point I'm only focusing only on 2.0. I've been wondering if I should create a subproject for chainsaw or if it should remain separate. I already moved a large part of extras in as a core part of the functionality. B/c of Chainsaw2 builds upon log4j2, I think I would create a subproject. This would make it easier to release Chainsaw version for a specific log4j2 release Ralph On Sep 1, 2011, at 4:13 AM, Christian Grobmeier wrote: Scott, Curt had an interesting idea lately, he mentioned it might make sense to move the companions code into chainsaw. What do you think on that? I like the idea - less releases, and no other interested parties in having companions. Please comment, when you can :-) Cheers Christian - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Companions - Chainsaw?
On Sep 1, 2011, at 6:13 AM, Christian Grobmeier wrote: Scott, Curt had an interesting idea lately, he mentioned it might make sense to move the companions code into chainsaw. What do you think on that? I like the idea - less releases, and no other interested parties in having companions. Please comment, when you can :-) Cheers Christian Did a quick review of receivers and there are a few things in there that are general purpose that would be better to move into log4j while most everything else would move directly into Chainsaw. Specifically, the org.apache.log4j.rewrite package and org.apache.log4j.helpers.UtilLoggingLevel look like they might have a better to have in log4j. http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/log4j/rewrite/package-summary.html http://logging.apache.org/log4j/companions/receivers/apidocs/org/apache/log4j/helpers/UtilLoggingLevel.html I think OSGi does not like to have a package to span multiple jars, so it might make sense to tweak the package names so that Chainsaw.jar does not define any classes in packages that are already defined in log4j.jar. That likely would have also been an issue if we proceeded to do a companion release. All the package names came from the backport of the log4j 1.3 code and there was no thought of the OSGi in the package naming. I think that I'd be able to do some quick surgery to svn mv the code from component and receivers into the proper places and fix up the import statements over the weekend. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
