Re: [net] Re: [GUMP@brutus]: Project commons-net (in module jakarta-commons) failed
On Tue, 11 Jan 2005, Steve Cohen [EMAIL PROTECTED] wrote: Checked in refactored test that hopefully will not break under GUMP Stefan, please let me know how it works. Great - Gump build on Sun JDKs passes now (tests fail in the Kaffe build in various places, probably Kaffe's fault). Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [net] Re: [GUMP at brutus]: Project commons-net (in module jakarta-commons) failed
Stefan Bodewig bodewig at apache.org writes: On Tue, 11 Jan 2005, Steve Cohen scohen at javactivity.org wrote: Checked in refactored test that hopefully will not break under GUMP Stefan, please let me know how it works. Great - Gump build on Sun JDKs passes now (tests fail in the Kaffe build in various places, probably Kaffe's fault). I'm resyncing with Classpath at the moment, I think there were some improvements in that area in the last couple of days (commons-io/net failures). cheers, dalibor topic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: Project commons-jelly-tags-junit (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-junit has an issue affecting its community integration. This issue affects 27 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-ant - commons-jelly-tags-bean - commons-jelly-tags-beanshell - commons-jelly-tags-betwixt - commons-jelly-tags-define - commons-jelly-tags-dynabean - commons-jelly-tags-fmt - commons-jelly-tags-html - commons-jelly-tags-http - commons-jelly-tags-jaxme - commons-jelly-tags-jetty - commons-jelly-tags-jface - commons-jelly-tags-jmx - commons-jelly-tags-jsl - commons-jelly-tags-junit - commons-jelly-tags-log - commons-jelly-tags-sql - commons-jelly-tags-swing - commons-jelly-tags-swt - commons-jelly-tags-threads - commons-jelly-tags-util - commons-jelly-tags-validate - commons-jelly-tags-xml - commons-jelly-tags-xmlunit - commons-latka : Functional Testing Suite - maven : Project Management Tools - maven-bootstrap : Project Management Tools Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-junit/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-junit-13012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/junit/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/junit/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/junit/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/junit/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/junit/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-junit/gump_work/build_commons-jelly-tags_commons-jelly-tags-junit.html Work Name: build_commons-jelly-tags_commons-jelly-tags-junit (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/junit] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at
[GUMP@brutus]: Project commons-jelly-tags-antlr (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-antlr has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-antlr Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-antlr/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-antlr-13012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/antlr/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-antlr/gump_work/build_commons-jelly-tags_commons-jelly-tags-antlr.html Work Name: build_commons-jelly-tags_commons-jelly-tags-antlr (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/antlr] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) You have encountered an unknown error running Maven. Please help us to correct this problem by following these simple
[GUMP@brutus]: Project commons-jelly-tags-email (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-email has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-email Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-email/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-email-13012005.jar] identifier set to project name -ERROR- Multiple outputs defined by project javamail; an id attribute is required to select the one you want -ERROR- Unhandled Property: maven.jar.mail on: Maven on Project:commons-jelly-tags-email -DEBUG- Dependency on jaf exists, no need to add for property maven.jar.activation. -DEBUG- Dependency on javamail exists, no need to add for property maven.jar.mail. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/email/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/email/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/email/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/email/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/email/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-email/gump_work/build_commons-jelly-tags_commons-jelly-tags-email.html Work Name: build_commons-jelly-tags_commons-jelly-tags-email (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/email] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaf-1.0.1/activation.jar:/usr/local/gump/packages/javamail-1.3.2/mail.jar:/usr/local/gump/packages/javamail-1.3.2/lib/mailapi.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[GUMP@brutus]: Project commons-jelly-tags-interaction (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-interaction has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-interaction Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-interaction/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-interaction-13012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/interaction/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/interaction/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/interaction/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/interaction/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/interaction/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-interaction/gump_work/build_commons-jelly-tags_commons-jelly-tags-interaction.html Work Name: build_commons-jelly-tags_commons-jelly-tags-interaction (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/interaction] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) You have encountered an unknown error running Maven. Please help us to correct this
[GUMP@brutus]: Project commons-jelly-tags-regexp (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-regexp has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-regexp Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-regexp/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-regexp-13012005.jar] identifier set to project name -DEBUG- Dependency on jakarta-oro exists, no need to add for property maven.jar.oro. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/regexp/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/regexp/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/regexp/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/regexp/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/regexp/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-regexp/gump_work/build_commons-jelly-tags_commons-jelly-tags-regexp.html Work Name: build_commons-jelly-tags_commons-jelly-tags-regexp (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/regexp] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jakarta-oro/jakarta-oro-13012005.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at
[GUMP@brutus]: Project commons-jelly-tags-velocity (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-velocity has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-velocity Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-velocity/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-velocity-13012005.jar] identifier set to project name -DEBUG- Dependency on jakarta-velocity exists, no need to add for property maven.jar.velocity. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/velocity/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/velocity/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/velocity/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/velocity/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/velocity/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-velocity/gump_work/build_commons-jelly-tags_commons-jelly-tags-velocity.html Work Name: build_commons-jelly-tags_commons-jelly-tags-velocity (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/velocity] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-13012005.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at
[GUMP@brutus]: Project commons-jelly-tags-bsf (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-bsf has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-bsf Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-bsf/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-bsf-13012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/bsf/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/bsf/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/bsf/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/bsf/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/bsf/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-bsf/gump_work/build_commons-jelly-tags_commons-jelly-tags-bsf.html Work Name: build_commons-jelly-tags_commons-jelly-tags-bsf (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/bsf] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/packages/bsf-2_2/lib/bsf.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) You have encountered an unknown error running Maven. Please help us to correct this problem by following these simple steps: - read the Maven FAQ
[GUMP@brutus]: Project commons-jelly-tags-jms (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-jms has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jms Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-jms/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jms-13012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/jms/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/jms/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/jms/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/jms/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/jms/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-jms/gump_work/build_commons-jelly-tags_commons-jelly-tags-jms.html Work Name: build_commons-jelly-tags_commons-jelly-tags-jms (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/jms] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jakarta-commons-sandbox/messenger/target/commons-messenger-13012005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar:/usr/local/gump/packages/jms1.1/lib/jms.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) You have encountered an unknown error
[GUMP@brutus]: Project commons-jelly-tags-soap (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-soap has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-soap Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-soap/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-soap-13012005.jar] identifier set to project name -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.axis. -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.jaxrpc-api. -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.saaj-api. -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for property maven.jar.servletapi. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: jaxme-api unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-soap/rss.xml - Atom: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-soap/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2413012005, brutus:brutus-public:2413012005 Gump E-mail Identifier (unique within run) #39. -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: Project commons-jelly-tags-antlr (in module commons-jelly-tags) failed
I've merged the gump descriptors so that the tags should build tomorrow. - Brett commons-jelly-tags-antlr development wrote: 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 [EMAIL PROTECTED] Project commons-jelly-tags-antlr has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-antlr Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-antlr/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-antlr-13012005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/antlr/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/antlr/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-antlr/gump_work/build_commons-jelly-tags_commons-jelly-tags-antlr.html Work Name: build_commons-jelly-tags_commons-jelly-tags-antlr (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/antlr] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) You have
[GUMP@brutus]: Project commons-jelly-tags-quartz (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-quartz has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-quartz Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-quartz/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-quartz-13012005.jar] identifier set to project name -DEBUG- Dependency on logging-log4j exists, no need to add for property maven.jar.log4j. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/quartz/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/quartz/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/quartz/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/quartz/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/quartz/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-quartz/gump_work/build_commons-jelly-tags_commons-jelly-tags-quartz.html Work Name: build_commons-jelly-tags_commons-jelly-tags-quartz (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/quartz] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar:/usr/local/gump/public/workspace/logging-log4j/log4j-13012005.jar:/usr/local/gump/public/workspace/quartz/lib/quartz.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
[GUMP@brutus]: Project commons-jelly-tags-avalon (in module commons-jelly-tags) 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 [EMAIL PROTECTED] Project commons-jelly-tags-avalon has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-avalon Full details are available at: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-avalon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-avalon-13012005.jar] identifier set to project name -DEBUG- Dependency on avalon-framework-api exists, no need to add for property maven.jar.avalon-framework. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly-tags/avalon/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly-tags/avalon/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly-tags/avalon/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly-tags/avalon/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly-tags/avalon/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/commons-jelly-tags/commons-jelly-tags-avalon/gump_work/build_commons-jelly-tags_commons-jelly-tags-avalon.html Work Name: build_commons-jelly-tags_commons-jelly-tags-avalon (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly-tags/avalon] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-13012005.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-13012005.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-13012005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-13012005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-13012005.jar - __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0 org.apache.maven.MavenException: Error parsing project.xml '/home/gump/workspaces2/public/workspace/parent-project.xml' at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:208) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:232) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:144) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.MavenSession.initializeRootProject(MavenSession.java:235) at org.apache.maven.MavenSession.initialize(MavenSession.java:175) at org.apache.maven.cli.App.doMain(App.java:473) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Re: [all] current dir in SVN test repository (externals)
The svn:externals property was set to check out the whole components rather than just the trunks of each component. I've tested my commit privs by fixing this (The working copy from a full checkout as below is now only 23M) Otherwise, the structure looks pretty good and the cli conversion looks accurate so I'm a big +1 on the transition when the infrastructure guys are ready. Rob Tim O'Brien wrote: I've set the svn:externals properties on the current subdirectory, if you do this: svn co https://svn.apache.org/repos/test/jakarta/commons/current/ You will get the current trunk for proper components. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] current dir in SVN test repository (externals)
Any reason this doesn't exist ? svn co https://svn.apache.org/repos/test/jakarta/commons/proper/jelly/ or this svn co https://svn.apache.org/repos/test/jakarta/commons/current/jelly/ Jelly seems to be nowhere :-( ... for some reasons https://svn.apache.org/repos/test/jakarta/commons/ seems to contain only projects till c... (neither when browsed nor when checked out) paul Le 11 janv. 05, à 15:00, Tim O'Brien a écrit : svn co https://svn.apache.org/repos/test/jakarta/commons/current/ You will get the current trunk for proper components. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] current dir in SVN test repository (externals)
A quote from Tim's original posting: A selection of components from commons proper and the sandbox are now available for you to experiment with on ASF hardware. -- Dennis Lundberg Paul Libbrecht wrote: Any reason this doesn't exist ? svn co https://svn.apache.org/repos/test/jakarta/commons/proper/jelly/ or this svn co https://svn.apache.org/repos/test/jakarta/commons/current/jelly/ Jelly seems to be nowhere :-( ... for some reasons https://svn.apache.org/repos/test/jakarta/commons/ seems to contain only projects till c... (neither when browsed nor when checked out) paul Le 11 janv. 05, à 15:00, Tim O'Brien a écrit : svn co https://svn.apache.org/repos/test/jakarta/commons/current/ You will get the current trunk for proper components. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/net/src/test/org/apache/commons/net/telnet TelnetClientTest.java
scohen 2005/01/13 04:07:59
Modified:net/src/test/org/apache/commons/net/telnet
TelnetClientTest.java
Log:
minor refactoring to make more efficient
Revision ChangesPath
1.12 +10 -10
jakarta-commons/net/src/test/org/apache/commons/net/telnet/TelnetClientTest.java
Index: TelnetClientTest.java
===
RCS file:
/home/cvs/jakarta-commons/net/src/test/org/apache/commons/net/telnet/TelnetClientTest.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- TelnetClientTest.java 12 Jan 2005 03:51:32 - 1.11
+++ TelnetClientTest.java 13 Jan 2005 12:07:59 - 1.12
@@ -31,7 +31,7 @@
public class TelnetClientTest
extends TestCase implements TelnetNotificationHandler
{
-private static final int CONNECTIONS = 5;
+private static final int CONNECTIONS = 4;
protected TelnetTestSimpleServer[] servers =
new TelnetTestSimpleServer[CONNECTIONS];
protected TelnetClient[] clients =
@@ -62,10 +62,12 @@
servers[socket] = new TelnetTestSimpleServer(port);
switch (socket) {
case 0:
-clients[socket] = new TelnetClient();
+ clients[socket] = new TelnetClient();
+// redundant but makes code clearer.
+clients[socket].setReaderThread(true);
break;
case 1:
-clients[socket] = new TelnetClient();
+ clients[socket] = new TelnetClient();
TerminalTypeOptionHandler ttopt =
new TerminalTypeOptionHandler(VT100, false,
false, true, false);
EchoOptionHandler echoopt =
@@ -84,12 +86,10 @@
clients[socket] = new TelnetClient();
clients[socket].setReaderThread(false);
break;
- case 4:
-clients[socket] = new TelnetClient();
-clients[socket].setReaderThread(true);
- break;
}
clients[socket].connect(127.0.0.1, port);
+
+ // only increment socket number on success
socket++;
System.err.println(opened client-server connection on port
+ port);
} catch (IOException e) {
@@ -761,8 +761,8 @@
negotiation1_ok = true;
}
-InputStream is2 = servers[4].getInputStream();
-OutputStream os2 = servers[4].getOutputStream();
+InputStream is2 = servers[0].getInputStream();
+OutputStream os2 = servers[0].getOutputStream();
Thread.sleep(1000);
is2.skip(is2.available());
os2.write(send1);
@@ -777,7 +777,7 @@
}
assertTrue(!clients[3].getReaderThread());
-assertTrue(clients[4].getReaderThread());
+assertTrue(clients[0].getReaderThread());
assertTrue(read_ok);
assertTrue(negotiation1_ok);
assertTrue(negotiation2_ok);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [net] Re: [GUMP at brutus]: Project commons-net (in module jakarta-commons) failed
Dalibor Topic wrote: Stefan Bodewig bodewig at apache.org writes: On Tue, 11 Jan 2005, Steve Cohen scohen at javactivity.org wrote: Checked in refactored test that hopefully will not break under GUMP Stefan, please let me know how it works. Great - Gump build on Sun JDKs passes now (tests fail in the Kaffe build in various places, probably Kaffe's fault). I'm resyncing with Classpath at the moment, I think there were some improvements in that area in the last couple of days (commons-io/net failures). cheers, dalibor topic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just checked in another minor refactoring of the test. It makes the code a little more efficient. Don't know if you GUMP guys have to do anything about that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jxpath] Array Creation Problem
Hi All, I am trying to call createPath to create array type of bean. I have registered my own AbstractFactory to the context. I am calling jxPathContext.createPath(secondBeanArray[1]/thirdBean). I have created the context using FirstBean. Method getSecondBeanArray() of FirstBean never returns null it always return a array (may be blank if no child bean i.e. SecondBean is added). Problem is createObject() method of my factory is not getting called in this scenario even though there is no SecondBean already added to FirstBean. I debugged the problem and found that if getSecondBeanArray() returns a null then only my factory is getting called. But I can't return null from getSecondBeanArray() method. Is there any direct way to solve this problem ?? If not, is there any way if I extend some classes of JXPath API and register those back? I saw the code also of JXPath API. And found that BeanPropertyPointer.createPath() is calling the PropertyPointer to create the node only in case of null. Thanks Puneet __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/net/src/test/org/apache/commons/net/telnet TelnetClientTest.java
scohen 2005/01/13 04:45:30
Modified:net/src/test/org/apache/commons/net/telnet
TelnetClientTest.java
Log:
Further refactoring, remove annoying array syntax introduced in 1.11.
Revision ChangesPath
1.13 +130 -86
jakarta-commons/net/src/test/org/apache/commons/net/telnet/TelnetClientTest.java
Index: TelnetClientTest.java
===
RCS file:
/home/cvs/jakarta-commons/net/src/test/org/apache/commons/net/telnet/TelnetClientTest.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- TelnetClientTest.java 13 Jan 2005 12:07:59 - 1.12
+++ TelnetClientTest.java 13 Jan 2005 12:45:30 - 1.13
@@ -31,12 +31,39 @@
public class TelnetClientTest
extends TestCase implements TelnetNotificationHandler
{
-private static final int CONNECTIONS = 4;
-protected TelnetTestSimpleServer[] servers =
-new TelnetTestSimpleServer[CONNECTIONS];
-protected TelnetClient[] clients =
-new TelnetClient[CONNECTIONS];
+/**
+ * Handy holder to hold both sides of the connection
+ * used in testing for clarity.
+ */
+private class TestConnection {
+TelnetTestSimpleServer server;
+TelnetClient client;
+int port;
+TestConnection(
+TelnetTestSimpleServer server,
+TelnetClient client,
+int port)
+{
+this.server = server;
+this.client = client;
+this.port = port;
+}
+protected void close() {
+TelnetClientTest.this.closeConnection(
+this.server, this.client, this.port);
+}
+}
+
+// four connections with different properties
+// to use in tests.
+private TestConnection STANDARD;
+private TestConnection OPTIONS;
+private TestConnection ANSI;
+private TestConnection NOREAD;
+
+private int NUM_CONNECTIONS = 4;
+
protected int numdo = 0;
protected int numdont = 0;
protected int numwill = 0;
@@ -56,18 +83,20 @@
protected void setUp() throws Exception
{
super.setUp();
-for (int port = , socket = 0; socket CONNECTIONS port
4000; port++)
+for (int port = , socket = 0; socket NUM_CONNECTIONS port
4000; port++)
{
+TelnetTestSimpleServer server = null;
+TelnetClient client = null;
try {
- servers[socket] = new TelnetTestSimpleServer(port);
- switch (socket) {
+ server = new TelnetTestSimpleServer(port);
+switch (socket) {
case 0:
- clients[socket] = new TelnetClient();
+ client = new TelnetClient();
// redundant but makes code clearer.
-clients[socket].setReaderThread(true);
+client.setReaderThread(true);
break;
case 1:
- clients[socket] = new TelnetClient();
+ client = new TelnetClient();
TerminalTypeOptionHandler ttopt =
new TerminalTypeOptionHandler(VT100, false,
false, true, false);
EchoOptionHandler echoopt =
@@ -75,25 +104,40 @@
SuppressGAOptionHandler gaopt =
new SuppressGAOptionHandler(true, true, true,
true);
-clients[socket].addOptionHandler(ttopt);
-clients[socket].addOptionHandler(echoopt);
-clients[socket].addOptionHandler(gaopt);
+client.addOptionHandler(ttopt);
+client.addOptionHandler(echoopt);
+client.addOptionHandler(gaopt);
break;
case 2:
-clients[socket] = new TelnetClient(ANSI);
+client = new TelnetClient(ANSI);
break;
case 3:
-clients[socket] = new TelnetClient();
-clients[socket].setReaderThread(false);
+client = new TelnetClient();
+client.setReaderThread(false);
break;
}
- clients[socket].connect(127.0.0.1, port);
+ client.connect(127.0.0.1, port);
+ switch (socket) {
+
DO NOT REPLY [Bug 32889] - [email][PATCH] Additional To, Cc and Bcc setters
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32889. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32889 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-01-13 14:51 --- patch submitted! thanks to Travis Meisenheimer for supporting this. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/email/src/java/org/apache/commons/mail Email.java
matzew 2005/01/13 05:52:32
Modified:emailproject.xml
email/src/java/org/apache/commons/mail Email.java
Log:
Closed bugzilla-ticket #32889 .thanks to Travis Meisenheimer for supporting
this.
Revision ChangesPath
1.8 +176 -181 jakarta-commons/email/project.xml
Index: project.xml
===
RCS file: /home/cvs/jakarta-commons/email/project.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- project.xml 14 Dec 2004 09:40:55 - 1.7
+++ project.xml 13 Jan 2005 13:52:32 - 1.8
@@ -1,182 +1,177 @@
-?xml version=1.0 encoding=UTF-8?
-!--
- Copyright 2001-2004 The Apache Software Foundation
-
- Licensed under the Apache License, Version 2.0 (the License);
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an AS IS BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
---
project
- nameCommons Email/name
- idcommons-email/id
- logo/images/email-logo-white.png/logo
- inceptionYear2001/inceptionYear
- shortDescriptionCommons Email/shortDescription
- descriptionCommons Email provides a simple wrapper over the Java Mail
API/description
- currentVersion1.0-rc2/currentVersion
- packageorg.apache.commons.mail/package
- gumpRepositoryIdjakarta/gumpRepositoryId
- siteAddressjakarta.apache.org/siteAddress
-
siteDirectory/www/jakarta.apache.org/commons/${pom.artifactId.substring(8)}//siteDirectory
-
distributionDirectory/www/jakarta.apache.org/builds/jakarta-commons/${pom.artifactId.substring(8)}//distributionDirectory
- issueTrackingUrlhttp://issues.apache.org/bugzilla//issueTrackingUrl
- repository
-connectionscm:cvs:pserver:[EMAIL
PROTECTED]:/home/cvspublic:jakarta-commons/${pom.artifactId.substring(8)}/connection
-
urlhttp://cvs.apache.org/viewcvs/jakarta-commons/${pom.artifactId.substring(8)}//url
- /repository
- mailingLists
-mailingList
- nameCommons Dev List/name
- subscribe[EMAIL PROTECTED]/subscribe
- unsubscribe[EMAIL PROTECTED]/unsubscribe
- archivehttp://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]/archive
-/mailingList
-mailingList
- nameCommons User List/name
- subscribe[EMAIL PROTECTED]/subscribe
- unsubscribe[EMAIL PROTECTED]/unsubscribe
- archivehttp://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]/archive
-/mailingList
- /mailingLists
- developers
-developer
- namedIon Gillard/name
- iddion/id
- email[EMAIL PROTECTED]/email
- organizationMultitask Consulting/organization
-/developer
-developer
- nameJohn McNally/name
- idjmcnally/id
- email[EMAIL PROTECTED]/email
- organizationCollabNet, Inc./organization
-/developer
-developer
- nameQuinton McCombs/name
- idquintonm/id
- email[EMAIL PROTECTED]/email
- organizationNequalsOne, LLC./organization
-/developer
-developer
- nameEric Pugh/name
- idepugh/id
- email[EMAIL PROTECTED]/email
- organizationOpenSource Connections/organization
-/developer
-developer
- nameDaniel Rall/name
- iddlr/id
- emaildlr@finemaltcoding.com/email
- organizationCollabNet, Inc./organization
-/developer
-developer
- nameJon Scott Stevens/name
- idjon/id
- email[EMAIL PROTECTED]/email
- organizationCollabNet, Inc./organization
-/developer
-developer
- nameJason van Zyl/name
- idjvanzyl/id
- email[EMAIL PROTECTED]/email
- organizationZenplex/organization
-/developer
-developer
- nameJoe Germuska/name
- idgermuska/id
- email[EMAIL PROTECTED]/email
-/developer
- /developers
-
- contributors
-contributor
- nameMatthias Wessendorf/name
- email[EMAIL PROTECTED]/email
-/contributor
-contributor
- nameCorey Scott/name
- email[EMAIL PROTECTED]/email
-/contributor
- contributor
- nameMark Lowe/name
- email[EMAIL PROTECTED]/email
-/contributor
- contributor
- nameRegis Koenigt/name
- email/email
-/contributor
- /contributors
-
- dependencies
-dependency
- groupIdcommons-lang/groupId
- artifactIdcommons-lang/artifactId
- version2.0/version
- urlhttp://jakarta.apache.org/commons/lang.html/url
RE: [feedparser] problems
I noticed some new activity on [feedparser]. But some problems I mentioned in this email are still existing. Any thoughts? Thanks! Matthias -Original Message- From: Matthias Wessendorf [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 5:45 PM To: commons-dev@jakarta.apache.org Subject: [feedparser] problems Hi all, I loaded [feedparser] and saw, that inside of package org.apache.commons.feedparser.post are clazzes with package-declaration org.apache.commons.feedparser see: http://cvs.apache.org/viewcvs.cgi/jakarta-commons-sandbox/feed parser/src /java/org/apache/commons/feedparser/post/MetaWeblogPostAgent.j ava?rev=1. 1view=auto Also I saw usage of org.apache.xmlrpc.* (http://ws.apache.org/xmlrpc/) but maven-dependency tells nothing on XML-RPC... see: http://jakarta.apache.org/commons/sandbox/feedparser/dependencies.html Btw, I couldn't run Maven. I tried maven jar but not success. see log below. Anybody still working on feedparser? Thanks, Matthias C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparsermaven jar __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc4 Plugin 'maven-deploy-plugin' in project 'Commons Feedparser' is not available build:start: java:prepare-filesystem: java:compile: [echo] Compiling to C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\fee dparser/target/classes [javac] Compiling 81 source files to C:\Programme\eclipse-SDK-3.0-win32\ecli pse\workspace\feedparser\target\classes C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\FeedParser.java:35: package org.apache.log4j does not exi st import org.apache.log4j.Logger; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\FeedParser.java:48: cannot resolve symbol symbol : class Logger location: class org.apache.commons.feedparser.FeedParser private static Logger log = Logger.getLogger( FeedParser.class ); ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\locate\FeedLocator.java:21: package org.peerfear.newsmons ter.network does not exist import org.peerfear.newsmonster.network.*; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\locate\FeedLocator.java:25: package org.apache.log4j does not exist import org.apache.log4j.Logger; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\locate\FeedLocator.java:47: cannot resolve symbol symbol : class Logger location: class org.apache.commons.feedparser.locate.FeedLocator private static Logger log = Logger.getLogger( FeedLocator.class ); ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\locate\ProbeLocator.java:22: package org.peerfear.newsmon ster.network does not exist import org.peerfear.newsmonster.network.*; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\locate\ProbeLocator.java:26: package org.apache.log4j doe s not exist import org.apache.log4j.Logger; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\locate\ProbeLocator.java:42: cannot resolve symbol symbol : class Logger location: class org.apache.commons.feedparser.locate.ProbeLocator private static Logger log = Logger.getLogger( ProbeLocator.class ); ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\post\MetaWeblogPostAgent.java:25: package org.apache.xmlr pc does not exist import org.apache.xmlrpc.*; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\test\TestAtom.java:32: package org.peerfear.newsmonster.t ools does not exist import org.peerfear.newsmonster.tools.*; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\test\TestAtom.java:33: package org.peerfear.newsmonster.n etwork does not exist import org.peerfear.newsmonster.network.*; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\test\TestFeedFilter.java:32: package org.peerfear.newsmon ster.tools does not exist import org.peerfear.newsmonster.tools.*; ^ C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\feedparse r\src\java \org\apa che\commons\feedparser\test\TestFeedFilter.java:33: package org.peerfear.newsmon ster.network does not exist
DO NOT REPLY [Bug 18942] - [beanutils] Add t/f to BooleanConverter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=18942. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=18942 --- Additional Comments From [EMAIL PROTECTED] 2005-01-13 15:57 --- I have a fix to BooleanConverter and a corresponding unit test for it. I have never contributed to any Jakarta project, but this is something that I had to write for my project anyway so I figured I'd see what is involved in submitting the code. Is my best option just to attach the modified code to this bug and hope a committer picks it up? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/transaction/src/test/org/apache/commons/transaction/locking GenericLockTest.java
ozeigermann2005/01/13 08:44:03
Modified:transaction/src/java/org/apache/commons/transaction/locking
GenericLockManager.java
transaction/src/test/org/apache/commons/transaction/locking
GenericLockTest.java
Log:
Fixed deadlock hazard in deadlock detection caused by interleaving access
to locks set of an owner and added test case that revealed it
Revision ChangesPath
1.20 +14 -9
jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking/GenericLockManager.java
Index: GenericLockManager.java
===
RCS file:
/home/cvs/jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking/GenericLockManager.java,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- GenericLockManager.java 9 Jan 2005 19:33:53 - 1.19
+++ GenericLockManager.java 13 Jan 2005 16:44:03 - 1.20
@@ -281,12 +281,17 @@
protected void releaseAllNoTimeOutReset(Object ownerId) {
Set locks = (Set) globalOwners.get(ownerId);
if (locks != null) {
+Collection locksCopy;
+// need to copy in order not to interfere with wouldDeadlock
+// possibly called by
+// other threads
synchronized (locks) {
-for (Iterator it = locks.iterator(); it.hasNext();) {
-GenericLock lock = (GenericLock) it.next();
-lock.release(ownerId);
-it.remove();
-}
+locksCopy = new ArrayList(locks);
+}
+for (Iterator it = locksCopy.iterator(); it.hasNext();) {
+GenericLock lock = (GenericLock) it.next();
+lock.release(ownerId);
+it.remove();
}
}
}
1.12 +77 -6
jakarta-commons/transaction/src/test/org/apache/commons/transaction/locking/GenericLockTest.java
Index: GenericLockTest.java
===
RCS file:
/home/cvs/jakarta-commons/transaction/src/test/org/apache/commons/transaction/locking/GenericLockTest.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- GenericLockTest.java 8 Jan 2005 18:56:03 - 1.11
+++ GenericLockTest.java 13 Jan 2005 16:44:03 - 1.12
@@ -262,6 +262,9 @@
sLogger.logInfo(\n\nChecking detection of indirect deadlock \n\n);
+final String jamowner1 = jamowner1;
+final String jamowner2 = jamowner2;
+
final String owner1 = owner1;
final String owner2 = owner2;
final String owner3 = owner3;
@@ -274,7 +277,7 @@
final ReadWriteLockManager manager = new
ReadWriteLockManager(sLogger,
TIMEOUT);
-final RendezvousBarrier restart = new RendezvousBarrier(restart,
3, TIMEOUT, sLogger);
+final RendezvousBarrier restart = new RendezvousBarrier(restart,
5, TIMEOUT, sLogger);
final TurnBarrier cb = new TurnBarrier(cb1, TIMEOUT, sLogger, 1);
@@ -282,6 +285,74 @@
System.out.print(.);
+// thread that accesses lock of res1 just to cause interference
and
+// possibly detect concurrency problems
+Thread jamThread1 = new Thread(new Runnable() {
+public void run() {
+try {
+for (int i = 0; i 10; i++) {
+manager.readLock(jamowner1, res1);
+Thread.sleep(10);
+manager.releaseAll(jamowner1);
+Thread.sleep(10);
+manager.writeLock(jamowner1, res1);
+Thread.sleep(10);
+manager.releaseAll(jamowner1);
+Thread.sleep(10);
+}
+} catch (LockException le) {
+fail(Jam Thread should not fail);
+} catch (InterruptedException ie) {
+} finally {
+manager.releaseAll(jamowner1);
+synchronized (restart) {
+try {
+synchronized (restart) {
+restart.meet();
+restart.reset();
+}
+} catch (InterruptedException ie) {}
+}
+}
+}
+}, Jam Thread #1);
+
+jamThread1.start();
+
+
cvs commit: jakarta-commons/transaction build.xml RELEASE-NOTES.txt project.xml
ozeigermann2005/01/13 08:46:42
Modified:transaction build.xml RELEASE-NOTES.txt project.xml
Log:
Counted up to release number 1.1b2pre
Revision ChangesPath
1.11 +1 -1 jakarta-commons/transaction/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-commons/transaction/build.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- build.xml 10 Jan 2005 00:32:35 - 1.10
+++ build.xml 13 Jan 2005 16:46:42 - 1.11
@@ -20,7 +20,7 @@
property name=compile.deprecation value=true /
property name=compile.optimize value=true /
- property name=version value=1.1b1/
+ property name=version value=1.1b2pre/
property name=name value=commons-transaction /
property name=title value=Commons Transaction /
property name=package value=org.apache.commons.transaction /
1.16 +11 -11jakarta-commons/transaction/RELEASE-NOTES.txt
Index: RELEASE-NOTES.txt
===
RCS file: /home/cvs/jakarta-commons/transaction/RELEASE-NOTES.txt,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- RELEASE-NOTES.txt 13 Jan 2005 02:07:44 - 1.15
+++ RELEASE-NOTES.txt 13 Jan 2005 16:46:42 - 1.16
@@ -1,8 +1,8 @@
-Jakarta Commons Transaction Release 1.1 beta1
--
+Jakarta Commons Transaction Release 1.1 beta2 pre
+-
-RELEASE NUMBER: 1.1b1
-RELEASE TAG / BRANCH: TRANSACTION_1_1_B1_RELEASE / none yet
+RELEASE NUMBER: 1.1b2pre
+RELEASE TAG / BRANCH: none yet / none yet
DESCRIPTION
---
@@ -19,7 +19,9 @@
GENERAL RELEASE NOTES
-
-This is the first beta of the Commons Transaction 1.1 feature release.
+This is the second beta of the Commons Transaction 1.1 feature release.
+It mainly fixes concurrency bugs not discovered before the first beta and
+adds test cases that reveal them.
Commons Transaction 1.1 aims at polishing (interface) oddities, improving
locking and making the file store more flexible. Locking now is much more
@@ -56,13 +58,11 @@
- PessimisticMapWrapper now throws the more general LockException from
locking package
-BUGFIXES FROM 1.0
--
-
+BUGFIXES FROM 1.0 beta1
+---
+- Fixed deadlock hazard in deadlock detection caused by interleaving access
to locks set of an owner
KNOWN ISSUES
-- Deadlock detection sometimes determines more than one thread as a deadlock
victim
-- There are (unverified) reports about deadlocks inside the deadlock
detection code
- or deadlocks not detected there
\ No newline at end of file
+- Deadlock detection sometimes determines more than one thread as a deadlock
victim
\ No newline at end of file
1.7 +1 -1 jakarta-commons/transaction/project.xml
Index: project.xml
===
RCS file: /home/cvs/jakarta-commons/transaction/project.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- project.xml 10 Jan 2005 00:32:35 - 1.6
+++ project.xml 13 Jan 2005 16:46:42 - 1.7
@@ -10,7 +10,7 @@
shortDescriptionCommons Transaction/shortDescription
descriptionCommons Transaction/description
- currentVersion1.1b1/currentVersion
+ currentVersion1.1b2pre/currentVersion
urlhttp://jakarta.apache.org/commons/${pom.artifactId.substring(8)}//url
packageorg.apache.commons.${pom.artifactId.substring(8)}/package
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I am out ill today (hopefully I will be back tomorrow)
I will be out of the office starting 01/13/2005 and will not return until 01/14/2005. I will respond to your message when I return.
cvs commit: jakarta-commons-sandbox/feedparser/lib jakarta-feedparser.jar
burton 2005/01/13 10:14:09 Modified:feedparser/lib jakarta-feedparser.jar Log: ... Revision ChangesPath 1.2 +341 -329 jakarta-commons-sandbox/feedparser/lib/jakarta-feedparser.jar Binary file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [all] current dir in SVN test repository (externals)
Paul, I can add Jelly to this mix as well. Let me know if you want me to and I'll put it on my stack. I can assure you that jelly made it into the full conversion. What you are looking at isn't a product of svnadmin load, I performed the migration to a subversion repository, then I exported the current version of all files and added them to the ASF test repository. I did this to same time and minimize the time it took to get something into the test repository. Justin's recommendation was a subset of the entire project without history. Tim -Original Message- From: Paul Libbrecht [mailto:[EMAIL PROTECTED] Sent: Thu 1/13/2005 5:33 AM To: Jakarta Commons Developers List Subject: Re: [all] current dir in SVN test repository (externals) Any reason this doesn't exist ? svn co https://svn.apache.org/repos/test/jakarta/commons/proper/jelly/ or this svn co https://svn.apache.org/repos/test/jakarta/commons/current/jelly/ Jelly seems to be nowhere :-( ... for some reasons https://svn.apache.org/repos/test/jakarta/commons/ seems to contain only projects till c... (neither when browsed nor when checked out) paul Le 11 janv. 05, à 15:00, Tim O'Brien a écrit : svn co https://svn.apache.org/repos/test/jakarta/commons/current/ You will get the current trunk for proper components. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/httpclient/xdocs performance.xml navigation.xml userguide.xml
olegk 2005/01/13 12:13:16 Modified:httpclient/xdocs navigation.xml userguide.xml Added: httpclient/xdocs performance.xml Log: PR #28296 (Compile performance optimization guide) Contributed by Oleg Kalnichevski, Ortwin Glueck, Michael Becke Revision ChangesPath 1.17 +2 -1 jakarta-commons/httpclient/xdocs/navigation.xml Index: navigation.xml === RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/navigation.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- navigation.xml8 Jan 2005 11:38:04 - 1.16 +++ navigation.xml13 Jan 2005 20:13:16 - 1.17 @@ -24,6 +24,7 @@ item name=Exception Handling href=/exception-handling.html/ item name=Logging Guide href=/logging.html/ item name=Methods href=/methods.html/ +item name=Optimization Guide href=/performance.html/ item name=Preference Architecture href=/preference-api.html/ item name=Redirects Handling href=/redirects.html/ item name=Sample Code href=http://cvs.apache.org/viewcvs.cgi/jakarta-commons/httpclient/src/examples// 1.6 +5 -1 jakarta-commons/httpclient/xdocs/userguide.xml Index: userguide.xml === RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/userguide.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- userguide.xml 16 Sep 2004 06:24:43 - 1.5 +++ userguide.xml 13 Jan 2005 20:13:16 - 1.6 @@ -55,6 +55,10 @@ that are provided by HttpClient and how to use them./td /tr tr + tda href=performance.htmlOptimization Guide/a/td + tdThis document outlines HttpClient performance optimization techniques./td +/tr +tr tda href=preference-api.htmlPreference Architecture/a/td tdThis document explains the preference architecture used by HttpClient and enumerates standard HttpClient parameters./td 1.1 jakarta-commons/httpclient/xdocs/performance.xml Index: performance.xml === ?xml version=1.0 encoding=ISO-8859-1? document properties titleHttpClient Performance Optimization Guide/title author email=oleg -at- ural.ruOleg Kalnichevski/author revision$Id: performance.xml,v 1.1 2005/01/13 20:13:16 olegk Exp $/revision /properties body section name=Introduction p By default HttpClient is configured to provide maximum reliability and standards compliance rather than raw performance. There are several configuration options and optimization techniques which can significantly improve the performance of HttpClient. This document outlines various techniques to achieve maximum HttpClient performance. /p subsection name=Contents ul li a href=#Reuse of HttpClient instanceReuse the HttpClient instance/a /li li a href=#Connection persistenceConnection persistence/a /li li a href=#Concurrent execution of HTTP methodsConcurrent execution of HTTP methods/a /li li a href=#Request/Response entity streamingRequest/Response entity streaming/a /li li a href=#Expect-continue handshakeExpect-continue handshake/a /li li a href=#Stale connection checkStale connection check/a /li li a href=#Cookie processingCookie processing/a /li /ul /subsection /section section name=Reuse the HttpClient instance p Generally it is recommended to have a single instance of HttpClient per communication component or even per application. However, if the application makes use of HttpClient only very infrequently, and keeping an idle instance of HttpClient in memory is not warranted, it is highly recommended to explicitly a href=apidocs/org/apache/commons/httpclient/MultiThreadedHttpConnectionManager.html#shutdown() shut down/a the multithreaded connection manager prior to disposing the HttpClient instance. This will ensure proper closure of all HTTP connections in the connection pool. /p /section section name=Connection persistence p HttpClient always does its best to reuse connections. Connection persistence is enabled by default and requires no configuration. Under some situations this can lead to leaked connections and therefore lost
cvs commit: jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking GenericLockManager.java
ozeigermann2005/01/13 15:11:56
Modified:transaction/src/java/org/apache/commons/transaction/locking
GenericLockManager.java
Log:
Fix for latest fix that did not remove freed locks from the owner list, but
from the snapshot copy only.
Revision ChangesPath
1.21 +5 -5
jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking/GenericLockManager.java
Index: GenericLockManager.java
===
RCS file:
/home/cvs/jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking/GenericLockManager.java,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- GenericLockManager.java 13 Jan 2005 16:44:03 - 1.20
+++ GenericLockManager.java 13 Jan 2005 23:11:56 - 1.21
@@ -291,7 +291,7 @@
for (Iterator it = locksCopy.iterator(); it.hasNext();) {
GenericLock lock = (GenericLock) it.next();
lock.release(ownerId);
-it.remove();
+locks.remove(lock);
}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking GenericLock.java
ozeigermann2005/01/13 15:12:44
Modified:transaction/src/java/org/apache/commons/transaction/locking
GenericLock.java
Log:
Added proper equals and hashcode methods.
Revision ChangesPath
1.14 +15 -4
jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking/GenericLock.java
Index: GenericLock.java
===
RCS file:
/home/cvs/jakarta-commons/transaction/src/java/org/apache/commons/transaction/locking/GenericLock.java,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- GenericLock.java 9 Jan 2005 23:56:07 - 1.13
+++ GenericLock.java 13 Jan 2005 23:12:44 - 1.14
@@ -156,6 +156,17 @@
this.logger = logger;
}
+public boolean equals(Object o) {
+if (o instanceof GenericLock) {
+return ((GenericLock)o).resourceId.equals(resourceId);
+}
+return false;
+}
+
+public int hashCode() {
+return resourceId.hashCode();
+}
+
/**
* @see MultiLevelLock2#test(Object, int, int)
*/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-145) jelly -version should answer
[ http://issues.apache.org/jira/browse/JELLY-145?page=comments#action_57609 ] dion gillard commented on JELLY-145: a test jelly -version should answer Key: JELLY-145 URL: http://issues.apache.org/jira/browse/JELLY-145 Project: jelly Type: Improvement Components: core / taglib.core Versions: 1.0-beta-4 Reporter: Paul Libbrecht Priority: Critical Attachments: a.txt Currently jelly -version responds an exception whereas every normal software would like to have a current version given. This could be assorted to the version of each taglib (e.g. jelly --tagLibVersion=swing). My best wish would be to output this automagically out of the project.xml... I am pretty sure maven users have requested, made, or even standardized this already... thanks paul -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-145) jelly -version should answer
[ http://issues.apache.org/jira/browse/JELLY-145?page=history ] dion gillard updated JELLY-145: --- Attachment: a.txt testing jelly -version should answer Key: JELLY-145 URL: http://issues.apache.org/jira/browse/JELLY-145 Project: jelly Type: Improvement Components: core / taglib.core Versions: 1.0-beta-4 Reporter: Paul Libbrecht Priority: Critical Attachments: a.txt Currently jelly -version responds an exception whereas every normal software would like to have a current version given. This could be assorted to the version of each taglib (e.g. jelly --tagLibVersion=swing). My best wish would be to output this automagically out of the project.xml... I am pretty sure maven users have requested, made, or even standardized this already... thanks paul -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-145) jelly -version should answer
[ http://issues.apache.org/jira/browse/JELLY-145?page=history ] dion gillard updated JELLY-145: --- Comment: was deleted jelly -version should answer Key: JELLY-145 URL: http://issues.apache.org/jira/browse/JELLY-145 Project: jelly Type: Improvement Components: core / taglib.core Versions: 1.0-beta-4 Reporter: Paul Libbrecht Priority: Critical Currently jelly -version responds an exception whereas every normal software would like to have a current version given. This could be assorted to the version of each taglib (e.g. jelly --tagLibVersion=swing). My best wish would be to output this automagically out of the project.xml... I am pretty sure maven users have requested, made, or even standardized this already... thanks paul -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-145) jelly -version should answer
[ http://issues.apache.org/jira/browse/JELLY-145?page=history ] dion gillard updated JELLY-145: --- Comment: was deleted jelly -version should answer Key: JELLY-145 URL: http://issues.apache.org/jira/browse/JELLY-145 Project: jelly Type: Improvement Components: core / taglib.core Versions: 1.0-beta-4 Reporter: Paul Libbrecht Priority: Critical Currently jelly -version responds an exception whereas every normal software would like to have a current version given. This could be assorted to the version of each taglib (e.g. jelly --tagLibVersion=swing). My best wish would be to output this automagically out of the project.xml... I am pretty sure maven users have requested, made, or even standardized this already... thanks paul -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
