[EMAIL PROTECTED]: Project commons-daemon (in module jakarta-commons) 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-daemon has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 231 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-daemon : Commons Daemon Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/gump_work/build_jakarta-commons_commons-daemon.html Work Name: build_jakarta-commons_commons-daemon (Type: Build) Work ended in a state of : Failed Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dcomponent.name=daemon-28022006 dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons/daemon] CLASSPATH: /opt/jdk1.5/lib/tools.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:junit-gump-27022006.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] daemon-28022006 1.0.1 prepare: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target/classes [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target/conf [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target/tests static: [copy] Copying 1 file to /x1/gump/public/workspace/jakarta-commons/daemon/target/conf compile: [javac] Compiling 6 source files to /x1/gump/public/workspace/jakarta-commons/daemon/target/classes BUILD FAILED :144: java.lang.VerifyError: verification failed at PC 0 in com.sun.tools.javac.Main:clinit(()V): String, int, or float constant expected Total time: 3 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2628022006, vmgump.apache.org:vmgump-public:2628022006 Gump E-mail Identifier (unique within run) #18. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-daemon (in module jakarta-commons) 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-daemon has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 231 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-daemon : Commons Daemon Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/gump_work/build_jakarta-commons_commons-daemon.html Work Name: build_jakarta-commons_commons-daemon (Type: Build) Work ended in a state of : Failed Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dcomponent.name=daemon-28022006 dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons/daemon] CLASSPATH: /opt/jdk1.5/lib/tools.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:junit-gump-27022006.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] daemon-28022006 1.0.1 prepare: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target/classes [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target/conf [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/daemon/target/tests static: [copy] Copying 1 file to /x1/gump/public/workspace/jakarta-commons/daemon/target/conf compile: [javac] Compiling 6 source files to /x1/gump/public/workspace/jakarta-commons/daemon/target/classes BUILD FAILED :144: java.lang.VerifyError: verification failed at PC 0 in com.sun.tools.javac.Main:clinit(()V): String, int, or float constant expected Total time: 3 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons/commons-daemon/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2628022006, vmgump.apache.org:vmgump-public:2628022006 Gump E-mail Identifier (unique within run) #18. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-launcher (in module jakarta-commons) 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-launcher has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 231 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-launcher : Jakarta commons Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-launcher.jar] identifier set to project name -DEBUG- Dependency on ant exists, no need to add for property ant.home. -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/gump_work/build_jakarta-commons_commons-launcher.html Work Name: build_jakarta-commons_commons-launcher (Type: Build) Work ended in a state of : Failed Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/usr/local/gump/public/workspace/ant/dist dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons/launcher] CLASSPATH: /opt/jdk1.5/lib/tools.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:junit-gump-27022006.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] launcher 1.2-dev prepare: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target/classes [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target/conf [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target/tests static: [copy] Copying 1 file to /x1/gump/public/workspace/jakarta-commons/launcher/target/conf compile: [javac] Compiling 16 source files to /x1/gump/public/workspace/jakarta-commons/launcher/target/classes BUILD FAILED :157: java.lang.VerifyError: verification failed at PC 0 in com.sun.tools.javac.Main:clinit(()V): String, int, or float constant expected Total time: 3 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2628022006, vmgump.apache.org:vmgump-public:2628022006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-launcher (in module jakarta-commons) 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-launcher has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 231 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-launcher : Jakarta commons Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-launcher.jar] identifier set to project name -DEBUG- Dependency on ant exists, no need to add for property ant.home. -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/gump_work/build_jakarta-commons_commons-launcher.html Work Name: build_jakarta-commons_commons-launcher (Type: Build) Work ended in a state of : Failed Elapsed: 4 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dant.home=/usr/local/gump/public/workspace/ant/dist dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons/launcher] CLASSPATH: /opt/jdk1.5/lib/tools.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:junit-gump-27022006.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] launcher 1.2-dev prepare: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target/classes [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target/conf [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/launcher/target/tests static: [copy] Copying 1 file to /x1/gump/public/workspace/jakarta-commons/launcher/target/conf compile: [javac] Compiling 16 source files to /x1/gump/public/workspace/jakarta-commons/launcher/target/classes BUILD FAILED :157: java.lang.VerifyError: verification failed at PC 0 in com.sun.tools.javac.Main:clinit(()V): String, int, or float constant expected Total time: 3 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons/commons-launcher/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2628022006, vmgump.apache.org:vmgump-public:2628022006 Gump E-mail Identifier (unique within run) #19. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-threading (in module jakarta-commons-dormant) 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-threading has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 231 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-threading : Commons Threading Utility Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-threading-28022006.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/gump_work/build_jakarta-commons-dormant_commons-threading.html Work Name: build_jakarta-commons-dormant_commons-threading (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dcomponent.version=28022006 dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons-dormant/threading] CLASSPATH: /opt/jdk1.5/lib/tools.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:junit-gump-27022006.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] threading 28022006 prepare: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/classes [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/conf [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/tests static: [copy] Copying 1 file to /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/conf compile: [javac] Compiling 20 source files to /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/classes BUILD FAILED :131: java.lang.VerifyError: verification failed at PC 0 in com.sun.tools.javac.Main:clinit(()V): String, int, or float constant expected Total time: 3 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2628022006, vmgump.apache.org:vmgump-public:2628022006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-threading (in module jakarta-commons-dormant) 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-threading has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 231 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-threading : Commons Threading Utility Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-threading-28022006.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/gump_work/build_jakarta-commons-dormant_commons-threading.html Work Name: build_jakarta-commons-dormant_commons-threading (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dcomponent.version=28022006 dist [Working Directory: /usr/local/gump/public/workspace/jakarta-commons-dormant/threading] CLASSPATH: /opt/jdk1.5/lib/tools.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:junit-gump-27022006.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar - Buildfile: build.xml init: [echo] threading 28022006 prepare: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/classes [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/conf [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/tests static: [copy] Copying 1 file to /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/conf compile: [javac] Compiling 20 source files to /x1/gump/public/workspace/jakarta-commons-dormant/threading/target/classes BUILD FAILED :131: java.lang.VerifyError: verification failed at PC 0 in com.sun.tools.javac.Main:clinit(()V): String, int, or float constant expected Total time: 3 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-dormant/commons-threading/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2628022006, vmgump.apache.org:vmgump-public:2628022006 Gump E-mail Identifier (unique within run) #20. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[email] ant dist fails / dependencies not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, ant dist fails, cause the dependencies cannot be found. http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar ... brought an I/O Exception, trying to download this from a browser show a 404. Are there any other archives or who does maintain this ibiblio.org site? An apache-depencies-host would be great, i guess... Regards, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEBB3Bkv8rKBUE/T4RAp9+AJsEL8PS+t/tY2sWS8A6GTJ5ZNq1kQCfSf/E rMgf/hCLYoaFEMpvW0ZrlNs= =cEZa -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [email] ant dist fails / dependencies not found
The javamail jars cannot be distributed by themselves as they are licensed under the Sun Binary Code License. I thought the generated ant build.xml would allow you to specify an alternate location of javamail.jar as a a property? is this not working? On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, ant dist fails, cause the dependencies cannot be found. http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar ... brought an I/O Exception, trying to download this from a browser show a 404. Are there any other archives or who does maintain this ibiblio.org site? An apache-depencies-host would be great, i guess... Regards, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEBB3Bkv8rKBUE/T4RAp9+AJsEL8PS+t/tY2sWS8A6GTJ5ZNq1kQCfSf/E rMgf/hCLYoaFEMpvW0ZrlNs= =cEZa -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris
Re: [email] ant dist fails / dependencies not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dion Gillard wrote: The javamail jars cannot be distributed by themselves as they are licensed under the Sun Binary Code License. I thought the generated ant build.xml would allow you to specify an alternate location of javamail.jar as a a property? is this not working? I got Dumbster, but not these two: * http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar * http://www.ibiblio.org/maven/activation/jars/activation-1.0.2.jar The location is hard-coded in the get/ Tag. Problem is before downloading you have to accept the terms. I think it would be better to kick off these get/ Tags and tell the user he has to download these apis manually. How is this solved with maven? I guess this will result in an error too. Regards, Chris On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: Hello, ant dist fails, cause the dependencies cannot be found. http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar ... brought an I/O Exception, trying to download this from a browser show a 404. Are there any other archives or who does maintain this ibiblio.org site? An apache-depencies-host would be great, i guess... Regards, Chris - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEBDHukv8rKBUE/T4RApQIAJ9D4h0gNoV3nOrhkE+SFFcbXlcl+gCfbq3I zNU5CSsxE6fxg1TDI6NXRoo= =ziSf -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [email] ant dist fails / dependencies not found
If you define a property (in build.properties) javamail.jar=c:/myjars/javamail-1.3.3.ar AFAIK, the build.xml will notice this and copy it into ./lib On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dion Gillard wrote: The javamail jars cannot be distributed by themselves as they are licensed under the Sun Binary Code License. I thought the generated ant build.xml would allow you to specify an alternate location of javamail.jar as a a property? is this not working? I got Dumbster, but not these two: * http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar * http://www.ibiblio.org/maven/activation/jars/activation-1.0.2.jar The location is hard-coded in the get/ Tag. Problem is before downloading you have to accept the terms. I think it would be better to kick off these get/ Tags and tell the user he has to download these apis manually. How is this solved with maven? I guess this will result in an error too. Regards, Chris On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: Hello, ant dist fails, cause the dependencies cannot be found. http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar ... brought an I/O Exception, trying to download this from a browser show a 404. Are there any other archives or who does maintain this ibiblio.org site? An apache-depencies-host would be great, i guess... Regards, Chris - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEBDHukv8rKBUE/T4RApQIAJ9D4h0gNoV3nOrhkE+SFFcbXlcl+gCfbq3I zNU5CSsxE6fxg1TDI6NXRoo= =ziSf -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris
DO NOT REPLY [Bug 38798] - [validator] validator argument - resource=false ignored
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=38798. 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=38798 --- Additional Comments From [EMAIL PROTECTED] 2006-02-28 12:38 --- Sorry, I'm not an XDoclet user - you'll have to ask XDoclet about 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]
Re: [email] ant dist fails / dependencies not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dion Gillard wrote: If you define a property (in build.properties) javamail.jar=c:/myjars/javamail-1.3.3.ar AFAIK, the build.xml will notice this and copy it into ./lib No, this doesn't work as expected. Cause the build-file works with get, i get: BUILD FAILED C:\Data\Projects\commons-email\build.xml:211: java.net.MalformedURLException: no protocol: /Data/java-repository/javamail-1.3.3_01/mail.jar when i use slashes, backslashes, double-backslashes, C:, c: and so on. I downloaded the distributions manually and will copy it to the place it have to be, but this is not comfortable. Does maven work with this? Chris. On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: Dion Gillard wrote: The javamail jars cannot be distributed by themselves as they are licensed under the Sun Binary Code License. I thought the generated ant build.xml would allow you to specify an alternate location of javamail.jar as a a property? is this not working? I got Dumbster, but not these two: * http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar * http://www.ibiblio.org/maven/activation/jars/activation-1.0.2.jar The location is hard-coded in the get/ Tag. Problem is before downloading you have to accept the terms. I think it would be better to kick off these get/ Tags and tell the user he has to download these apis manually. How is this solved with maven? I guess this will result in an error too. Regards, Chris On 2/28/06, C. Grobmeier [EMAIL PROTECTED] wrote: Hello, ant dist fails, cause the dependencies cannot be found. http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar http://www.ibiblio.org/maven/javamail/jars/javamail-1.3.3.jar ... brought an I/O Exception, trying to download this from a browser show a 404. Are there any other archives or who does maintain this ibiblio.org site? An apache-depencies-host would be great, i guess... Regards, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEBEdmkv8rKBUE/T4RAtmKAJ0RQbTpSA2FgZyR1cfrethb6a1o4ACgiSCb LC3oBaGCZDTKWWlB3JIMBLg= =0b7x -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] building the site?
Hi Phil, Yes, I'll try to find a solution to use maven 1.1 to build the commons. I'll certainly need to readd xerces to the core :-( to allow you to use XML entities. cheers arnaud On 2/28/06, Phil Steitz [EMAIL PROTECTED] wrote: Both of these requirements - maven 1.0.2 and xdoc 1.9.2 - are included in the getting and installing maven section here http://jakarta.apache.org/commons/building.html Thanks in advance, Arnaud for any help removing the 1.0.2 restriction. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] building the site?
You wouldn't need to read Xerces in any line... you just need to use an org.xml.sax.InputSource which has a properly set system-id. new InputSource(URL) or new InputSource(File) does make it for you. Generally such resolution error happen to be when an InputSource(InputStream) is used for which the parser has no way to resolve a relative file. Maybe that helps ? paul Arnaud HERITIER wrote: Hi Phil, Yes, I'll try to find a solution to use maven 1.1 to build the commons. I'll certainly need to readd xerces to the core :-( to allow you to use XML entities. cheers arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [email] ant dist fails / dependencies not found
C. Grobmeier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dion Gillard wrote: If you define a property (in build.properties) javamail.jar=c:/myjars/javamail-1.3.3.ar AFAIK, the build.xml will notice this and copy it into ./lib No, this doesn't work as expected. Cause the build-file works with get, i get: BUILD FAILED C:\Data\Projects\commons-email\build.xml:211: java.net.MalformedURLException: no protocol: /Data/java-repository/javamail-1.3.3_01/mail.jar when i use slashes, backslashes, double-backslashes, C:, c: and so on. You may want to try the 'file' protocol, like this: file:///Data/java-repository/javamail-1.3.3_01/mail.jar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
publishing commons-modeler jar to maven 2 repo
Hi, Geronimo uses commomns-modeler-1.1.jar. How can I get this jar published to maven2 repository? The repository has 1.1M1. Thanks IN Advance Anita __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [email] ant dist fails / dependencies not found
I'll test this as well. I thought just the file name would work, but will verify the URL approach as well. On 3/1/06, matthew.hawthorne [EMAIL PROTECTED] wrote: C. Grobmeier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dion Gillard wrote: If you define a property (in build.properties) javamail.jar=c:/myjars/javamail-1.3.3.ar AFAIK, the build.xml will notice this and copy it into ./lib No, this doesn't work as expected. Cause the build-file works with get, i get: BUILD FAILED C:\Data\Projects\commons-email\build.xml:211: java.net.MalformedURLException: no protocol: /Data/java-repository/javamail-1.3.3_01/mail.jar when i use slashes, backslashes, double-backslashes, C:, c: and so on. You may want to try the 'file' protocol, like this: file:///Data/java-repository/javamail-1.3.3_01/mail.jar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris
Re: [email] ant dist fails / dependencies not found
matthew.hawthorne wrote: C. Grobmeier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dion Gillard wrote: If you define a property (in build.properties) javamail.jar=c:/myjars/javamail-1.3.3.ar AFAIK, the build.xml will notice this and copy it into ./lib No, this doesn't work as expected. Cause the build-file works with get, i get: BUILD FAILED C:\Data\Projects\commons-email\build.xml:211: java.net.MalformedURLException: no protocol: /Data/java-repository/javamail-1.3.3_01/mail.jar when i use slashes, backslashes, double-backslashes, C:, c: and so on. You may want to try the 'file' protocol, like this: file:///Data/java-repository/javamail-1.3.3_01/mail.jar Matthew is correct, you need to use a correctly formated URL. Here's an example for a Windows machine: activation.jar=file://C:/myjars/activation.jar javamail.jar=file://C:/myjars/mail.jar -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] JCL1 LogFactory incompatibility with WAS
On Mon, 2006-02-27 at 21:19 +, robert burrell donkin wrote: On Mon, 2006-02-27 at 12:13 +0100, Boris Unckel wrote: Hello, hi boris I have tested several other cases, the results and conditions are in the zip. I am really wondering about one case: The delegation mode of all tests is PARENT_LAST, for ear and war. I have put a commons-logging.properties file in the classpath of the EAR and the WAR (each). It still does not work (see subdirectory error). I will not go further on my own (due to time limitation) but if you have a special testcase or a newer version I will test again. thanks for very much for your work - it's very much appreciated :) It certainly is appreciated; testing is what we most need at this point. Thanks Boris. The new diagnostics system appears to be paying off here; the output shows a lot about what's going in with the failed scenario that Boris provides. It looks like IBM Websphere 5.1 uses its own LogFactory implementation rather than the default o.a.c.l.impl.LogFactoryImpl. It appears to set system org.apache.commons.logging.LogFactory to point to class com.ibm.ws.commons.logging.TrLogFactory. The setup that Boris has used doesn't follow the guidelines in the user guide for this situation; the container provides JCL, so the webapp needs to bundle commons-logging-adapters.jar, NOT commons-logging.jar. See: http://people.apache.org/~rdonkin/commons-logging/site2/guide.html#commons-logging-adapters.jar It's a variant on the old xyzLog does not implement Log issue which the adapters jar was created to solve. JCL is already deployed in a shared path AND a full JCL has been deployed in the webapp. As a result, LogFactory is loaded from the webapp path but the custom LogFactory implementation is loaded from an ancestor classloader and therefore is bound to a different LogFactory implementation. There's no way for us to work around this using classloader tricks as far as I can see; the adapters jar is the proper solution. What we *do* need to consider is whether we can improve the documentation or the error messages to make it clear what the correct fix is. Boris, would you please replace commons-logging-1.1-RC5.jar with commons-logging-adapters-1.1-RC5.jar in your webapp and retest? This should solve the problem. It would also be useful if you could try commons-logging.jar from 1.0.4 with this webapp and verify that a logging failure occurs. General comment: the fact that WAS has a custom LogFactory implementation means that most of the improvements we added to the 1.1 release of JCL won't be available to WAS. The only thing we need to do is make sure that the changes we made to the base LogFactory abstract class haven't made anything *worse*. I'll review the changes to LogFactory.java to see if there are any implications for custom implementations. Maybe the user guide could do with a note about the fact that WAS uses a custom LogFactory implementation Cheers, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] JCL1 LogFactory incompatibility with WAS
On Wed, 2006-03-01 at 11:03 +1300, Simon Kitching wrote: On Mon, 2006-02-27 at 21:19 +, robert burrell donkin wrote: On Mon, 2006-02-27 at 12:13 +0100, Boris Unckel wrote: Hello, hi boris I have tested several other cases, the results and conditions are in the zip. I am really wondering about one case: The delegation mode of all tests is PARENT_LAST, for ear and war. I have put a commons-logging.properties file in the classpath of the EAR and the WAR (each). It still does not work (see subdirectory error). I will not go further on my own (due to time limitation) but if you have a special testcase or a newer version I will test again. thanks for very much for your work - it's very much appreciated :) It certainly is appreciated; testing is what we most need at this point. Thanks Boris. The new diagnostics system appears to be paying off here; the output shows a lot about what's going in with the failed scenario that Boris provides. +1 :) It looks like IBM Websphere 5.1 uses its own LogFactory implementation rather than the default o.a.c.l.impl.LogFactoryImpl. It appears to set system org.apache.commons.logging.LogFactory to point to class com.ibm.ws.commons.logging.TrLogFactory. +1 The setup that Boris has used doesn't follow the guidelines in the user guide for this situation; the container provides JCL, so the webapp needs to bundle commons-logging-adapters.jar, NOT commons-logging.jar. See: http://people.apache.org/~rdonkin/commons-logging/site2/guide.html#commons-logging-adapters.jar i've downloaded and installed an evaluation version of WAS to try to confirm that WAS ships with JCL (and if so, where abouts). i also plan to see if i can improve recognition of this situation and (if so) provide a better message. It's a variant on the old xyzLog does not implement Log issue which the adapters jar was created to solve. JCL is already deployed in a shared path AND a full JCL has been deployed in the webapp. As a result, LogFactory is loaded from the webapp path but the custom LogFactory implementation is loaded from an ancestor classloader and therefore is bound to a different LogFactory implementation. There's no way for us to work around this using classloader tricks as far as I can see; the adapters jar is the proper solution. +1 AIUI (haven't verified this as yet) IBM uses a system property to specify the LogFactory implementation so JCL will work fine if the administrator specifies the standard implementation on the command line. i'll also try to verify that adding the latest JCL to the appropriate system classpath also fixes this problem. What we *do* need to consider is whether we can improve the documentation or the error messages to make it clear what the correct fix is. +1 (see above) i have some more material already prepared for the troubleshooting document but nothing IBM specific. any volunteer to create a patch? snip General comment: the fact that WAS has a custom LogFactory implementation means that most of the improvements we added to the 1.1 release of JCL won't be available to WAS. The only thing we need to do is make sure that the changes we made to the base LogFactory abstract class haven't made anything *worse*. I'll review the changes to LogFactory.java to see if there are any implications for custom implementations. Maybe the user guide could do with a note about the fact that WAS uses a custom LogFactory implementation +1 WAS uses the factory to bridge to it's standard logging system. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[logging] testing harmony jchevm
Hi, I am trying logging + log4j with harmony jchevm but when I am using commons-logging-1.0.4 and logging-log4j-1.2.13 I have an exception: +++ java.lang.NoSuchMethodError: org/apache/log4j/Category.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V at java.lang.VMThrowable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:498) at java.lang.Throwable.init(Throwable.java:159) at java.lang.Error.init(Error.java:81) at java.lang.LinkageError.init(LinkageError.java:72) at java.lang.IncompatibleClassChangeError.init(IncompatibleClassChangeError.java:71) at java.lang.NoSuchMethodError.init(NoSuchMethodError.java:72) at java.lang.VMClass.forName(Native Method) at java.lang.Class.forName(Class.java:161) at toto.main(toto.java:8) +++ If I am using logging-log4j-1.3alpha-8 jchevm works ok. Any idea why commons-logging-1.0.4 requires a 1.3x log4j? Cheers Jean-Frederic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] testing harmony jchevm
On Tue, 2006-02-28 at 23:39 +0100, Jean-frederic Clere wrote: Hi, I am trying logging + log4j with harmony jchevm but when I am using commons-logging-1.0.4 and logging-log4j-1.2.13 I have an exception: +++ java.lang.NoSuchMethodError: org/apache/log4j/Category.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V at java.lang.VMThrowable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:498) at java.lang.Throwable.init(Throwable.java:159) at java.lang.Error.init(Error.java:81) at java.lang.LinkageError.init(LinkageError.java:72) at java.lang.IncompatibleClassChangeError.init(IncompatibleClassChangeError.java:71) at java.lang.NoSuchMethodError.init(NoSuchMethodError.java:72) at java.lang.VMClass.forName(Native Method) at java.lang.Class.forName(Class.java:161) at toto.main(toto.java:8) +++ If I am using logging-log4j-1.3alpha-8 jchevm works ok. Any idea why commons-logging-1.0.4 requires a 1.3x log4j? nope, none at all could you retry with the latest release candidate from the 1.1 codestream? http://people.apache.org/~rdonkin/commons-logging/ - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [JEXL] Blocks and an Expression
On 2/27/06, Dion Gillard [EMAIL PROTECTED] wrote: Ok, I've found the cause of the problem. ExpressionFactory.createNewExpression on line 125 does this: SimpleNode node = (SimpleNode) tree.jjtGetChild(0); So only the first statement of the parsed expression is actually evaluated. In the cases of the commented out tests, there are multiple statements which are children of the parse tree. The use of a block here really isn't significant, using a parse string like x =1; y=2; causes the same issue. snip/ Agreed. So, the question becomes, should we support multiple statements for an expression (outside a block), or do we implement ASTJexlScript so that it evaluates each of it's children in turn and returns the last value? snap/ Neither? ;-) Took a peek, the behavior is as advertised since a JEXL Expression is indeed a reference to a single expression, and those semantics need to persist. However, since we use the script grammar for the ExpressionFactory (whereas the grammar for scripts is really a superset of the expression grammar), we parse the (potential) script and pluck out the just first expression even if there are more. The fact that expressions beyond the first are silently ignored probably needs to be addressed. Short of teasing apart two grammars (and/or having a ScriptFactory), perhaps it will be sufficient to trivially log a warning when that happens. WDYT? As an independent question, why doesn't JEXL have Script as a first class entity like Expression (with a ScriptFactory to match)? -Rahul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381826 - /jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/impl/LogFactoryImpl.java
Author: skitching
Date: Tue Feb 28 15:31:20 2006
New Revision: 381826
URL: http://svn.apache.org/viewcvs?rev=381826view=rev
Log:
Minor diagnostics tweak: use word from instead of confusion -.
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/impl/LogFactoryImpl.java
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/impl/LogFactoryImpl.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/impl/LogFactoryImpl.java?rev=381826r1=381825r2=381826view=diff
==
---
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/impl/LogFactoryImpl.java
(original)
+++
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/impl/LogFactoryImpl.java
Tue Feb 28 15:31:20 2006
@@ -476,7 +476,7 @@
} catch(SecurityException e) {
classLoaderName = UNKNOWN;
}
-diagnosticPrefix = [LogFactoryImpl@ + System.identityHashCode(this)
+ - + classLoaderName + ] ;
+diagnosticPrefix = [LogFactoryImpl@ + System.identityHashCode(this)
+ from + classLoaderName + ] ;
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381828 - /jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Author: skitching
Date: Tue Feb 28 15:32:27 2006
New Revision: 381828
URL: http://svn.apache.org/viewcvs?rev=381828view=rev
Log:
Diagnostics changes only:
* Output correct classloader used to load LogFactory implementation
* Use word from instead of confusing -
* Other minor improvements to diagnostics messages.
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java?rev=381828r1=381827r2=381828view=diff
==
---
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
(original)
+++
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Tue Feb 28 15:32:27 2006
@@ -1037,7 +1037,7 @@
if (isDiagnosticsEnabled()) {
logDiagnostic(
Factory class +
logFactoryClass.getName()
-+ loaded from classloader +
objectId(classLoader)
++ loaded from classloader +
objectId(logFactoryClass.getClassLoader())
+ does not extend ' +
LogFactory.class.getName()
+ ' as loaded by this classloader.);
logHierarchy([BAD CL TREE] , classLoader);
@@ -1319,9 +1319,12 @@
// In order to avoid confusion where multiple instances of JCL are
// being used via different classloaders within the same app, we
// ensure each logged message has a prefix of form
-// [LogFactory -- classloader OID]
+// [LogFactory from classloader OID]
+//
// Note that this prefix should be kept consistent with that
-// in LogFactoryImpl
+// in LogFactoryImpl. However here we don't need to output info
+// about the actual *instance* of LogFactory, as all methods that
+// output diagnostics from this class are static.
String classLoaderName;
try {
ClassLoader classLoader = thisClassLoader;
@@ -1333,7 +1336,7 @@
} catch(SecurityException e) {
classLoaderName = UNKNOWN;
}
-diagnosticPrefix = [LogFactory - + classLoaderName + ] ;
+diagnosticPrefix = [LogFactory from + classLoaderName + ] ;
}
/**
@@ -1411,8 +1414,8 @@
}
try {
-logDiagnostic([ENV] Extension directories: +
System.getProperty(java.ext.dir));
-logDiagnostic([ENV] Application classpath: +
System.getProperty(java.class.path));
+logDiagnostic([ENV] Extension directories (java.ext.dir): +
System.getProperty(java.ext.dir));
+logDiagnostic([ENV] Application classpath (java.class.path): +
System.getProperty(java.class.path));
} catch(SecurityException ex) {
logDiagnostic([ENV] Security setting prevent interrogation of
system classpaths.);
}
@@ -1432,7 +1435,7 @@
logDiagnostic(
[ENV] Class + className + was loaded via classloader
+ objectId(classLoader));
-logHierarchy([ENV] , classLoader);
+logHierarchy([ENV] Ancestry of classloader which loaded + className
+ is , classLoader);
}
/**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] testing harmony jchevm
robert burrell donkin wrote: On Tue, 2006-02-28 at 23:39 +0100, Jean-frederic Clere wrote: Hi, I am trying logging + log4j with harmony jchevm but when I am using commons-logging-1.0.4 and logging-log4j-1.2.13 I have an exception: +++ java.lang.NoSuchMethodError: org/apache/log4j/Category.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V at java.lang.VMThrowable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:498) at java.lang.Throwable.init(Throwable.java:159) at java.lang.Error.init(Error.java:81) at java.lang.LinkageError.init(LinkageError.java:72) at java.lang.IncompatibleClassChangeError.init(IncompatibleClassChangeError.java:71) at java.lang.NoSuchMethodError.init(NoSuchMethodError.java:72) at java.lang.VMClass.forName(Native Method) at java.lang.Class.forName(Class.java:161) at toto.main(toto.java:8) +++ If I am using logging-log4j-1.3alpha-8 jchevm works ok. Any idea why commons-logging-1.0.4 requires a 1.3x log4j? nope, none at all could you retry with the latest release candidate from the 1.1 codestream? jchevm works ok with commons-logging-1.1-RC5.jar ;-) Cheers Jean-Frederic http://people.apache.org/~rdonkin/commons-logging/ - robert - 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: [logging] testing harmony jchevm
On Tue, 2006-02-28 at 22:59 +, robert burrell donkin wrote: On Tue, 2006-02-28 at 23:39 +0100, Jean-frederic Clere wrote: Hi, I am trying logging + log4j with harmony jchevm but when I am using commons-logging-1.0.4 and logging-log4j-1.2.13 I have an exception: +++ java.lang.NoSuchMethodError: org/apache/log4j/Category.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V at java.lang.VMThrowable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:498) at java.lang.Throwable.init(Throwable.java:159) at java.lang.Error.init(Error.java:81) at java.lang.LinkageError.init(LinkageError.java:72) at java.lang.IncompatibleClassChangeError.init(IncompatibleClassChangeError.java:71) at java.lang.NoSuchMethodError.init(NoSuchMethodError.java:72) at java.lang.VMClass.forName(Native Method) at java.lang.Class.forName(Class.java:161) at toto.main(toto.java:8) +++ If I am using logging-log4j-1.3alpha-8 jchevm works ok. Any idea why commons-logging-1.0.4 requires a 1.3x log4j? nope, none at all could you retry with the latest release candidate from the 1.1 codestream? http://people.apache.org/~rdonkin/commons-logging/ While it would be nice to have testing with 1.1, we should figure out what's going on here too. Initially it looks to me like the log4j team have accidentally made a 1.2.13 release which is binary-incompatible with 1.2.12. If that proves to be the case we need to tell them so they can fix this. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36927] - [logging] Disabling of TCCL
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=36927. 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=36927 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-03-01 00:50 --- As there's been no response I'll presume the implemented fix is satisfactory. -- 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]
svn commit: r381838 - /jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/Log.java
Author: skitching Date: Tue Feb 28 15:57:11 2006 New Revision: 381838 URL: http://svn.apache.org/viewcvs?rev=381838view=rev Log: Trivial javadoc patch to add return type info for isXXXEnabled methods. Thanks to Boris Unckel for patch; see bugzilla#38783. Modified: jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/Log.java Modified: jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/Log.java URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/Log.java?rev=381838r1=381837r2=381838view=diff == --- jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/Log.java (original) +++ jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/Log.java Tue Feb 28 15:57:11 2006 @@ -71,6 +71,8 @@ * p Call this method to prevent having to perform expensive operations * (for example, codeString/code concatenation) * when the log level is more than debug. /p + * + * @return true if debug is enabled in the underlying logger. */ public boolean isDebugEnabled(); @@ -81,6 +83,8 @@ * p Call this method to prevent having to perform expensive operations * (for example, codeString/code concatenation) * when the log level is more than error. /p + * + * @return true if error is enabled in the underlying logger. */ public boolean isErrorEnabled(); @@ -91,6 +95,8 @@ * p Call this method to prevent having to perform expensive operations * (for example, codeString/code concatenation) * when the log level is more than fatal. /p + * + * @return true if fatal is enabled in the underlying logger. */ public boolean isFatalEnabled(); @@ -101,6 +107,8 @@ * p Call this method to prevent having to perform expensive operations * (for example, codeString/code concatenation) * when the log level is more than info. /p + * + * @return true if info is enabled in the underlying logger. */ public boolean isInfoEnabled(); @@ -111,6 +119,8 @@ * p Call this method to prevent having to perform expensive operations * (for example, codeString/code concatenation) * when the log level is more than trace. /p + * + * @return true if trace is enabled in the underlying logger. */ public boolean isTraceEnabled(); @@ -121,6 +131,8 @@ * p Call this method to prevent having to perform expensive operations * (for example, codeString/code concatenation) * when the log level is more than warn. /p + * + * @return true if warn is enabled in the underlying logger. */ public boolean isWarnEnabled(); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 38783] - [logging][PATCH] Javadoc for jul.Log interface
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=38783. 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=38783 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-03-01 00:57 --- Patch committed. Thanks. -- 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]
Re: [JEXL] Blocks and an Expression
On 3/1/06, Rahul Akolkar [EMAIL PROTECTED] wrote: snip So, the question becomes, should we support multiple statements for an expression (outside a block), or do we implement ASTJexlScript so that it evaluates each of it's children in turn and returns the last value? snap/ Neither? ;-) Took a peek, the behavior is as advertised since a JEXL Expression is indeed a reference to a single expression, and those semantics need to persist. However, since we use the script grammar for the ExpressionFactory (whereas the grammar for scripts is really a superset of the expression grammar), we parse the (potential) script and pluck out the just first expression even if there are more. The fact that expressions beyond the first are silently ignored probably needs to be addressed. Short of teasing apart two grammars (and/or having a ScriptFactory), perhaps it will be sufficient to trivially log a warning when that happens. A warning would be a good idea. I don't want to change the behaviour of Expression to throw an exception if there is more than a single piece. WDYT? As an independent question, why doesn't JEXL have Script as a first class entity like Expression (with a ScriptFactory to match)? This sounds like a good thing to add to 1.1 - Loading and executing scripts. -Rahul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris
svn commit: r381845 - /jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/ExpressionFactory.java
Author: rahul
Date: Tue Feb 28 16:20:54 2006
New Revision: 381845
URL: http://svn.apache.org/viewcvs?rev=381845view=rev
Log:
Log warning instead of silently ignoring expressions beyond the first (if there
are more than one).
Modified:
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/ExpressionFactory.java
Modified:
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/ExpressionFactory.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/ExpressionFactory.java?rev=381845r1=381844r2=381845view=diff
==
---
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/ExpressionFactory.java
(original)
+++
jakarta/commons/proper/jexl/trunk/src/java/org/apache/commons/jexl/ExpressionFactory.java
Tue Feb 28 16:20:54 2006
@@ -120,6 +120,14 @@
tree = parser.parse(new StringReader(expr));
}
+if (tree.jjtGetNumChildren() 1) {
+if (log.isWarnEnabled()) {
+log.warn( The JEXL Expression created will be a reference
++ to the first expression from the supplied script: \
++ expression + \ );
+}
+}
+
// Must be a simple reference, expression, statement or if, otherwise
// throw an exception.
SimpleNode node = (SimpleNode) tree.jjtGetChild(0);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] JCL1 LogFactory incompatibility with WAS
On Thu, 2006-02-23 at 23:05 +, robert burrell donkin wrote: JCL 1.1 is incompatible with WAS. this appears to be an existing standing issue http://www.javablog.com/2005/12/28/1135813600066.html. i haven't managed to with work out why this is case (as yet). it does expose another place where JCL throws a runtime exception where it might well be better to just use diagnostic logging. there appear to be a number of containers who use their own LogFactory implementations so that they can hook JCL into their logging system. given there are issues, i'll close down JCL1 branch for now and continue JCL 1.1 work on trunk. This same issue has been discussed in a different thread on this same list today. However I'll reply here for the sake of people searching the archives for this, and add some more details. The problem is that WAS deploys commons-logging.jar in a shared classpath location, and also forces commons-logging to load a custom LogFactory implementation from the shared classpath by setting system property org.apache.commons.logging.LogFactory to point to custom class com.ibm.ws.commons.logging.TrLogFactory. If a webapp also deploys commons-logging in the webapp then: * user classes bind to the LogFactory loaded via the webapp classloader, due to standard Java rules. * The webap copy of LogFactory has been ordered to load the specified TrLogFactory;it's only available class via the shared classloader and by the standard Java rules this binds to the LogFactory loaded via the shared classloader. * It is then impossible to cast the TrLogFactory to the type expected There's nothing that commons-logging can do to avoid an exception in this case, except possibly fall back to using the standard LogFactoryImpl class. However that would be overriding *explicit* instructions via a system property which isn't something a library should do lightly. The solutions are to change the way in which the classes are deployed instead. In increasing order of complexity: (a) Don't deploy commons-logging in the webapp at all; it's already in the shared classpath. However for most concrete logging libraries this means that there's no way to do per-webapp logging configuration. (b) Don't force commons-logging to load its LogFactory implementation from the shared classpath. In this case, this means ensuring that system property org.apache.commons.logging.LogFactory points to an implementation available at the webapp level. The standard org.apache.commons.logging.impl.LogFactoryImpl will do for example. However this *does* disable whatever functionality was in that special IBM class [I've got no idea what TrLogFactory actually does]. (c) modify the commons-logging.jar file in the webapp to remove the LogFactory and Log classes. (d) Ensure that class com.ibm.ws.commons.logging.TrLogFactory is available in the webapp classloader's path by copying the class there. However this might lead to further problems. In the commons-logging 1.1 release (currently at Release Candidate 5), file commons-logging-adapters.jar is provided which effectively implements option (c) above. Using this jar instead of the full commons-logging.jar should resolve this issue. Just to recap: the issue is caused by having multiple copies of core commons-logging classes in the classpath, not by any bugs in commons-logging itself. The fundamental rules of Java classloading specify that two copies of the same class loaded by two different classloaders are *not* compatible even when byte-for-byte identical. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381879 - /jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Author: skitching
Date: Tue Feb 28 18:49:34 2006
New Revision: 381879
URL: http://svn.apache.org/viewcvs?rev=381879view=rev
Log:
Add a diagnostic message, and add some comments related to issues when a
LogFactory implementation cannot be instantiated.
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java?rev=381879r1=381878r2=381879view=diff
==
---
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
(original)
+++
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Tue Feb 28 18:49:34 2006
@@ -465,6 +465,20 @@
+ ]. Trying alternative implementations...);
}
; // ignore
+} catch(Exception e) {
+// This is not consistent with the behaviour when a bad LogFactory
class is
+// specified in a services file.
+//
+// One possible exception that can occur here is a
ClassCastException when
+// the specified class wasn't castable to this LogFactory type.
+if (isDiagnosticsEnabled()) {
+logDiagnostic(
+[LOOKUP] An exception occurred while trying to create
an
++ instance of the custom factory class
++ : [ + e.getMessage().trim()
++ ] as specified by a system property.);
+}
+throw e;
}
@@ -510,6 +524,9 @@
}
}
} catch( Exception ex ) {
+// note: if the specified LogFactory class wasn't compatible
with LogFactory
+// for some reason, a ClassCastException will be caught here,
and attempts will
+// continue to find a compatible class.
if (isDiagnosticsEnabled()) {
logDiagnostic(
[LOOKUP] A security exception occurred while trying
to create an
@@ -950,6 +967,9 @@
final ClassLoader
contextClassLoader)
throws LogConfigurationException
{
+// Note that any unchecked exceptions thrown by the createFactory
+// method will propagate out of this method; in particular a
+// ClassCastException can be thrown.
Object result = AccessController.doPrivileged(
new PrivilegedAction() {
public Object run() {
@@ -998,7 +1018,11 @@
* Implements the operations described in the javadoc for newFactory.
*
* @param factoryClass
- * @param classLoader
+ *
+ * @param classLoader used to load the specified factory class. This is
+ * expected to be either the TCCL or the classloader which loaded this
+ * class. Note that the classloader which loaded this class might be
+ * null (ie the bootloader) for embedded systems.
*
* @return either a LogFactory object or a LogConfigurationException
object.
* @since 1.1
@@ -1082,7 +1106,19 @@
}
throw e;
}
-// Ignore exception, continue
+
+// Ignore exception, continue. Presumably the classloader
was the
+// TCCL; the code below will try to load the class via
thisClassLoader.
+// This will handle the case where the original calling
class is in
+// a shared classpath but the TCCL has a copy of
LogFactory and the
+// specified LogFactory implementation; we will fall back
to using the
+// LogFactory implementation from the same classloader as
this class.
+//
+// Issue: this doesn't handle the reverse case, where this
LogFactory
+// is in the webapp, and the specified LogFactory
implementation is
+// in a shared classpath. In that case:
+// (a) the class really does implement LogFactory (bad log
msg above)
+// (b) the fallback code will result in exactly the same
problem.
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] JCL1 LogFactory incompatibility with WAS
On Tue, 2006-02-28 at 22:32 +, robert burrell donkin wrote: i've downloaded and installed an evaluation version of WAS to try to confirm that WAS ships with JCL (and if so, where abouts). Great. i also plan to see if i can improve recognition of this situation and (if so) provide a better message. It's a variant on the old xyzLog does not implement Log issue which the adapters jar was created to solve. JCL is already deployed in a shared path AND a full JCL has been deployed in the webapp. As a result, LogFactory is loaded from the webapp path but the custom LogFactory implementation is loaded from an ancestor classloader and therefore is bound to a different LogFactory implementation. There's no way for us to work around this using classloader tricks as far as I can see; the adapters jar is the proper solution. +1 I guess one thing we *could* do is fall back to using LogFactoryImpl if the system property points to a class that we can't cast to LogFactory. That's a pretty scary thing to do though; the application has *explicitly* set a property to tell JCL which class to use but we ignore it and use another one instead? What do you think? i'll also try to verify that adding the latest JCL to the appropriate system classpath also fixes this problem. I don't believe that will fix this situation. What we *do* need to consider is whether we can improve the documentation or the error messages to make it clear what the correct fix is. +1 (see above) We could test the class to see if it has an ancestor whose *name* is org.apache.commons.logging.LogFactory. If it does, then we have multiple copies of JCL in the classpath and could emit a warning that commons-logging-adapters.jar should be used instead. That seems like a good idea to me, so unless someone speaks up quickly I'll add code to do that. Cheers, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381886 - /jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Author: skitching
Date: Tue Feb 28 19:11:41 2006
New Revision: 381886
URL: http://svn.apache.org/viewcvs?rev=381886view=rev
Log:
* Fix minor syntax error in previous checkin (oops).
* Improve error message when custom LogFactory class cannot be instantiated due
to class cast issues.
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java?rev=381886r1=381885r2=381886view=diff
==
---
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
(original)
+++
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Tue Feb 28 19:11:41 2006
@@ -465,7 +465,7 @@
+ ]. Trying alternative implementations...);
}
; // ignore
-} catch(Exception e) {
+} catch(RuntimeException e) {
// This is not consistent with the behaviour when a bad LogFactory
class is
// specified in a services file.
//
@@ -1096,15 +1096,23 @@
// ignore exception, continue
} catch(ClassCastException e) {
if (classLoader == thisClassLoader) {
-// This cast exception is not due to classloader
issues;
-// the specified class *really* doesn't extend the
-// required LogFactory base class.
+// There's no point in falling through to the code
below that
+// tries again with thisClassLoader, because we've
just tried
+// loading with that loader (not the TCCL). Just throw
an
+// appropriate exception here.
+
+String msg =
+Class ' + factoryClass + ' cannot be converted
to '
++ LogFactory.class.getName() + '.
++ Perhaps you have multiple copies of LogFactory
in
++ the classpath?;
+
if (isDiagnosticsEnabled()) {
-logDiagnostic(
-Class ' + factoryClass + ' really does
not extend '
-+ LogFactory.class.getName() + ');
+logDiagnostic(msg);
}
-throw e;
+
+ClassCastException ex = new ClassCastException(msg);
+throw ex;
}
// Ignore exception, continue. Presumably the classloader
was the
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381887 - /jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Author: skitching
Date: Tue Feb 28 19:15:40 2006
New Revision: 381887
URL: http://svn.apache.org/viewcvs?rev=381887view=rev
Log:
Another minor diagnostics tweak.
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Modified:
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java?rev=381887r1=381886r2=381887view=diff
==
---
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
(original)
+++
jakarta/commons/proper/logging/trunk/src/java/org/apache/commons/logging/LogFactory.java
Tue Feb 28 19:15:40 2006
@@ -1104,8 +1104,9 @@
String msg =
Class ' + factoryClass + ' cannot be converted
to '
+ LogFactory.class.getName() + '.
-+ Perhaps you have multiple copies of LogFactory
in
-+ the classpath?;
++ Perhaps you have multiple copies of LogFactory
in
++ the classpath? If so, consider using the
++ commons-logging-adapters.jar file.;
if (isDiagnosticsEnabled()) {
logDiagnostic(msg);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] JCL1 LogFactory incompatibility with WAS
On Wed, 2006-03-01 at 14:32 +1300, Simon Kitching wrote: I guess one thing we *could* do is fall back to using LogFactoryImpl if the system property points to a class that we can't cast to LogFactory. That's a pretty scary thing to do though; the application has *explicitly* set a property to tell JCL which class to use but we ignore it and use another one instead? What do you think? i'll also try to verify that adding the latest JCL to the appropriate system classpath also fixes this problem. I don't believe that will fix this situation. What we *do* need to consider is whether we can improve the documentation or the error messages to make it clear what the correct fix is. +1 (see above) We could test the class to see if it has an ancestor whose *name* is org.apache.commons.logging.LogFactory. If it does, then we have multiple copies of JCL in the classpath and could emit a warning that commons-logging-adapters.jar should be used instead. That seems like a good idea to me, so unless someone speaks up quickly I'll add code to do that. Ok, I've enhanced the diagnostics somewhat. The code is rather complicated and twisty so I wasn't able to add the test I wanted; instead I just give a suggestion about checking for duplicate classes and using the commons-logging-adapters jar file. Cheers, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381905 - /jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/AbstractStateMachine.java
Author: rahul
Date: Tue Feb 28 20:50:53 2006
New Revision: 381905
URL: http://svn.apache.org/viewcvs?rev=381905view=rev
Log:
The AbstractStateMachine class demonstrates one approach for providing the base
functionality needed by classes representing stateful entities, whose behaviors
are defined via SCXML documents.
Added:
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/AbstractStateMachine.java
(with props)
Added:
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/AbstractStateMachine.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/AbstractStateMachine.java?rev=381905view=auto
==
---
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/AbstractStateMachine.java
(added)
+++
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/AbstractStateMachine.java
Tue Feb 28 20:50:53 2006
@@ -0,0 +1,295 @@
+/*
+ *
+ * Copyright 2006 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.
+ *
+ */
+package org.apache.commons.scxml.env;
+
+import java.io.IOException;
+import java.lang.reflect.InvocationTargetException;
+import java.lang.reflect.Method;
+import java.net.URL;
+
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
+import org.apache.commons.scxml.Context;
+import org.apache.commons.scxml.Evaluator;
+import org.apache.commons.scxml.SCXMLExecutor;
+import org.apache.commons.scxml.SCXMLListener;
+import org.apache.commons.scxml.TriggerEvent;
+import org.apache.commons.scxml.env.jexl.JexlContext;
+import org.apache.commons.scxml.env.jexl.JexlEvaluator;
+import org.apache.commons.scxml.io.SCXMLDigester;
+import org.apache.commons.scxml.model.ModelException;
+import org.apache.commons.scxml.model.SCXML;
+import org.apache.commons.scxml.model.Transition;
+import org.apache.commons.scxml.model.TransitionTarget;
+import org.xml.sax.ErrorHandler;
+import org.xml.sax.SAXException;
+
+/**
+ * This class demonstrates one approach for providing the base
+ * functionality needed by classes representing stateful entities,
+ * whose behaviors are defined via SCXML documents.
+ *
+ * SCXML documents (more generically, UML state chart diagrams) can be
+ * used to define stateful behavior of objects, and Commons SCXML enables
+ * developers to use this model directly into the corresponding code
+ * artifacts. The resulting artifacts tend to be much simpler, embody
+ * a useful separation of concerns and are easier to understand and
+ * maintain. As the size of the modeled entity grows, these benefits
+ * become more apparent.
+ *
+ * This approach functions by registering an SCXMLListener that gets
+ * notified onentry, and calls the namesake method for each state that
+ * has been entered.
+ *
+ * This class swallows all exceptions only to log them. Developers of
+ * subclasses should think of themselves as quot;component developersquot;
+ * catering to other end users, and therefore ensure that the subclasses
+ * are free of codeModelException/codes and the like. Most methods
+ * are codeprotected/code for ease of subclassing.
+ *
+ */
+public abstract class AbstractStateMachine {
+
+/**
+ * The state machine that will drive the instances of this class.
+ */
+private static SCXML stateMachine;
+
+/**
+ * The instance specific SCXML engine.
+ */
+private SCXMLExecutor engine;
+
+/**
+ * The log.
+ */
+private Log log;
+
+/**
+ * The method signature for the activities corresponding to each
+ * state in the SCXML document.
+ */
+private static final Class[] SIGNATURE = new Class[0];
+
+/**
+ * The method parameters for the activities corresponding to each
+ * state in the SCXML document.
+ */
+private static final Object[] PARAMETERS = new Object[0];
+
+/**
+ * Convenience constructor.
+ *
+ * @param scxmlDocument The URL pointing to the SCXML document that
+ * describes the quot;lifecyclequot; of the
+ * instances of this class.
+ */
+public AbstractStateMachine(final URL scxmlDocument) {
+// default is JEXL
+this(scxmlDocument, new JexlContext(), new JexlEvaluator());
+}
+
+/**
+ * Primary
svn commit: r381907 - in /jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env: StopWatch.java stopwatch.xml
Author: rahul
Date: Tue Feb 28 21:12:20 2006
New Revision: 381907
URL: http://svn.apache.org/viewcvs?rev=381907view=rev
Log:
Towards BZ 38274
[scxml] Write Use Case for Stand-alone Application Modelling a Stop Watch
A SCXML driven stop watch. Thanks to:
* Stephen Colebourne, the state machine and stopwatch usecase is inspired by
Stephen's slides for his Javapolis talk '05 (New and Upcoming in Jakarta
Commons)
* Tim O'Brien, for the nudge
Added:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatch.java
(with props)
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatch.xml
(with props)
Added:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatch.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatch.java?rev=381907view=auto
==
---
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatch.java
(added)
+++
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatch.java
Tue Feb 28 21:12:20 2006
@@ -0,0 +1,131 @@
+/*
+ * Copyright 2006 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.
+ */
+package org.apache.commons.scxml.env;
+
+import java.util.Set;
+import java.util.Timer;
+import java.util.TimerTask;
+
+import org.apache.commons.scxml.env.AbstractStateMachine;
+
+/**
+ * A SCXML document driven stop watch.
+ *
+ * Using SCXML makes the StopWatch class simplistic; you are neither
+ * managing the stopwatch lifecycle nor coding any transitions,
+ * that information is pulled in straight from the behavioral model
+ * of the stop watch, which is encapsulated in the SCXML document
+ * the constructor points to (which in turn may be generated straight
+ * from the UML model).
+ */
+public class StopWatch extends AbstractStateMachine {
+
+/** The events for the stop watch. */
+public static final String EVENT_START = watch.start,
+EVENT_STOP = watch.stop, EVENT_SPLIT = watch.split,
+EVENT_UNSPLIT = watch.unsplit, EVENT_RESET = watch.reset;
+
+/** The fragments of the elapsed time. */
+private int hr, min, sec, fract;
+/** The fragments of the display time. */
+private int dhr, dmin, dsec, dfract;
+/** The stopwatch split (display freeze). */
+private boolean split;
+/** The Timer to keep time. */
+private Timer timer;
+/** The display decorations. */
+private static final String DELIM = :, DOT = ., EMPTY = , ZERO = 0;
+
+public StopWatch() {
+super(StopWatch.class.getClassLoader().
+getResource(org/apache/commons/scxml/env/stopwatch.xml));
+}
+
+// Each method below is the activity corresponding to a state in the
+// SCXML document (see class constructor for pointer to the document).
+public void reset() {
+hr = min = sec = fract = dhr = dmin = dsec = dfract = 0;
+split = false;
+}
+
+public void running() {
+split = false;
+if (timer == null) {
+timer = new Timer(true);
+timer.scheduleAtFixedRate(new TimerTask() {
+public void run() {
+increment();
+}
+}, 100, 100);
+}
+}
+
+public void paused() {
+split = true;
+}
+
+public void stopped() {
+timer.cancel();
+timer = null;
+}
+
+public String getDisplay() {
+String padhr = dhr 9 ? EMPTY : ZERO;
+String padmin = dmin 9 ? EMPTY : ZERO;
+String padsec = dsec 9 ? EMPTY : ZERO;
+return new StringBuffer().append(padhr).append(dhr).append(DELIM).
+append(padmin).append(dmin).append(DELIM).append(padsec).
+append(dsec).append(DOT).append(dfract).toString();
+}
+
+// used by the demonstration (see StopWatchDisplay usecase)
+public String getCurrentState() {
+Set states = getEngine().getCurrentStatus().getStates();
+return ((org.apache.commons.scxml.model.State) states.iterator().
+next()).getId();
+}
+
+private void increment() {
+if (fract 9) {
+fract++;
+} else {
+fract = 0;
+if (sec 59) {
+sec++;
+} else {
+
svn commit: r381909 - in /jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env: EnvTestSuite.java StopWatchTest.java
Author: rahul
Date: Tue Feb 28 21:18:41 2006
New Revision: 381909
URL: http://svn.apache.org/viewcvs?rev=381909view=rev
Log:
A test case for the stop watch usecase.
Added:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatchTest.java
(with props)
Modified:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/EnvTestSuite.java
Modified:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/EnvTestSuite.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/EnvTestSuite.java?rev=381909r1=381908r2=381909view=diff
==
---
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/EnvTestSuite.java
(original)
+++
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/EnvTestSuite.java
Tue Feb 28 21:18:41 2006
@@ -49,6 +49,7 @@
suite.setName(Commons-SCXML Environments Tests);
suite.addTest(LogUtilsTest.suite());
suite.addTest(SimpleContextTest.suite());
+suite.addTest(StopWatchTest.suite());
return suite;
}
}
Added:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatchTest.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatchTest.java?rev=381909view=auto
==
---
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatchTest.java
(added)
+++
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatchTest.java
Tue Feb 28 21:18:41 2006
@@ -0,0 +1,69 @@
+/*
+ * Copyright 2006 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.
+ */
+package org.apache.commons.scxml.env;
+
+
+import junit.framework.Test;
+import junit.framework.TestCase;
+import junit.framework.TestSuite;
+
+public class StopWatchTest extends TestCase {
+
+public StopWatchTest(String testName) {
+super(testName);
+}
+
+public static Test suite() {
+return new TestSuite(StopWatchTest.class);
+}
+
+public static void main(String args[]) {
+String[] testCaseName = { StopWatchTest.class.getName()};
+junit.textui.TestRunner.main(testCaseName);
+}
+
+private StopWatch stopWatch;
+
+/**
+ * Set up instance variables required by this test case.
+ */
+public void setUp() {
+stopWatch = new StopWatch();
+}
+
+/**
+ * Tear down instance variables required by this test case.
+ */
+public void tearDown() {
+stopWatch = null;
+}
+
+public void testStopWatch() {
+assertEquals(reset, stopWatch.getCurrentState());
+stopWatch.fireEvent(StopWatch.EVENT_START);
+assertEquals(running, stopWatch.getCurrentState());
+stopWatch.fireEvent(StopWatch.EVENT_SPLIT);
+assertEquals(paused, stopWatch.getCurrentState());
+stopWatch.fireEvent(StopWatch.EVENT_UNSPLIT);
+assertEquals(running, stopWatch.getCurrentState());
+stopWatch.fireEvent(StopWatch.EVENT_STOP);
+assertEquals(stopped, stopWatch.getCurrentState());
+stopWatch.fireEvent(StopWatch.EVENT_RESET);
+assertEquals(reset, stopWatch.getCurrentState());
+}
+
+}
+
Propchange:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatchTest.java
--
svn:eol-style = native
Propchange:
jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/StopWatchTest.java
--
svn:keywords = Date Author Id Revision HeadURL
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381912 - /jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatch.gif
Author: rahul Date: Tue Feb 28 21:27:52 2006 New Revision: 381912 URL: http://svn.apache.org/viewcvs?rev=381912view=rev Log: My rendition of a stopwatch. The beginnings of a UI. Miss gimp, but freestyle paint will have to do. Added: jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatch.gif (with props) Added: jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatch.gif URL: http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatch.gif?rev=381912view=auto == Binary file - no diff available. Propchange: jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatch.gif -- svn:mime-type = image/gif - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r381913 - /jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatchicon.gif
Author: rahul Date: Tue Feb 28 21:32:26 2006 New Revision: 381913 URL: http://svn.apache.org/viewcvs?rev=381913view=rev Log: Will throw in a stopwatch icon while I'm at it. Added: jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatchicon.gif (with props) Added: jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatchicon.gif URL: http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatchicon.gif?rev=381913view=auto == Binary file - no diff available. Propchange: jakarta/commons/sandbox/scxml/trunk/src/test/java/org/apache/commons/scxml/env/stopwatchicon.gif -- svn:mime-type = image/gif - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
