RE: Dormancy proposals
Henri Yandell wrote on Wednesday, February 21, 2007 8:43 AM: On 2/20/07, Jörg Schaible [EMAIL PROTECTED] wrote: Henri Yandell wrote on Wednesday, February 21, 2007 3:33 AM: I'd like to propose that the following be moved from the Sandbox into Dormant. * i18n I am using an older snapshot in production and I have added contributions to JIRA - it's just that I never committed directly. If nobody else cares I can do something and you may give it also a 3 month review ... Sure. I'll consider that a -1 and add to the three month review. If I remember in 3 months. And I find this thread :) Hehehe :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (SANDBOX-106) [jci] Remove utils package
[
https://issues.apache.org/jira/browse/SANDBOX-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Curdt reopened SANDBOX-106:
---
[jci] Remove utils package
--
Key: SANDBOX-106
URL: https://issues.apache.org/jira/browse/SANDBOX-106
Project: Commons Sandbox
Issue Type: Bug
Components: JCI
Environment: Operating System: All
Platform: Other
Reporter: elharo
Assigned To: Torsten Curdt
The org.apache.commons.jci.utils package contains one simple class that does
this:
package org.apache.commons.jci.utils;
public final class ThreadUtils {
public static void sleep( final long pDelay ) {
try {
Thread.sleep(pDelay);
} catch (final InterruptedException e) {
}
}
}
That's way too little to justify a package. This class is:
1. Trivial.
2. Outside the scope of the JCI Project
There is little reason for this to be a public API. This method should be
inlined and the package removed; or, at the very least, this class could be
duplicated as a non-public class within whichever other packages actually use
it.
Keeping the public API footprint to a minimum is important for future
extensibility and maintainability.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (SANDBOX-106) [jci] Remove utils package
[
https://issues.apache.org/jira/browse/SANDBOX-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Torsten Curdt closed SANDBOX-106.
-
Resolution: Fixed
[jci] Remove utils package
--
Key: SANDBOX-106
URL: https://issues.apache.org/jira/browse/SANDBOX-106
Project: Commons Sandbox
Issue Type: Bug
Components: JCI
Environment: Operating System: All
Platform: Other
Reporter: elharo
Assigned To: Torsten Curdt
The org.apache.commons.jci.utils package contains one simple class that does
this:
package org.apache.commons.jci.utils;
public final class ThreadUtils {
public static void sleep( final long pDelay ) {
try {
Thread.sleep(pDelay);
} catch (final InterruptedException e) {
}
}
}
That's way too little to justify a package. This class is:
1. Trivial.
2. Outside the scope of the JCI Project
There is little reason for this to be a public API. This method should be
inlined and the package removed; or, at the very least, this class could be
duplicated as a non-public class within whichever other packages actually use
it.
Keeping the public API footprint to a minimum is important for future
extensibility and maintainability.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: jira issue open or closed?
cool ...worked cheers -- Torsten On 21.02.2007, at 01:57, Henri Yandell wrote: It's closed, but unresolved. It's a bug in the bugzilla import where the resolution doesn't seem to get set, you have to open the issue and then close it again. I've not seen a great rhyme nor reason for it. Hen On 2/20/07, Torsten Curdt [EMAIL PROTECTED] wrote: https://issues.apache.org/jira/browse/SANDBOX-106 In my summary this issue is still listed as open issue assigned to me When I drill down into the issue it is already close. Anyone a clue? cheers -- Torsten - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (EMAIL-64) Use wiser instead of dumbster for test cases
[ https://issues.apache.org/jira/browse/EMAIL-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474746 ] Jon Stevens commented on EMAIL-64: -- Hi everyone, SubEtha SMTP and Wiser are not dead at all. It's very actively maintained (for a project that is essentially functionally complete) and has no known major bugs. I'm working with a contributor to add AUTH support as well as doing a re-write with apache mina as the core networking engine. As for maven... well, the pom.xml files were donated by someone else. I personally *hate* maven and wouldn't use it if my life depended on it (and yes, i understand how maven works and have tried to use it). If you guys want to see the latest version of subethasmtp up on the iblibio repo, then you get to figure out how to make that happen. As for JDK 1.4 compatibility... the ant build files will produce a jdk 1.4 version using the retroweaver stuff. it works great. As for the LGPL... it's an issue for the ASF to depend on it. I'll eventually change the license to an ASF license, so don't worry about it. Go ahead and use it. Oh and I was the one who started this project ya'll are working on right now. So phewy on you Dion. =) =) I'm just glad to see there is still people who use and develop it. cheers! -jon stevens Use wiser instead of dumbster for test cases Key: EMAIL-64 URL: https://issues.apache.org/jira/browse/EMAIL-64 Project: Commons Email Issue Type: Improvement Affects Versions: 1.1 Reporter: Ben Speakmon Fix For: 1.1 Attachments: dumbster_to_wiser.patch, dumbster_to_wiser_jdk14_pom.diff, dumbster_to_wiser_xdocs.patch Since the test cases depend on a snapshot of the dead project dumbster, the tests should be changed to use the wiser test email server instead. Marking as 1.1 fix since this should get done before 1.1 goes out the door. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-soap (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-soap has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 109 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-soap : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-soap-21022007.jar] identifier set to project name -ERROR- No such project [ws-jaxme] for property. -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on Project:commons-jelly-tags-soap -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.axis. -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.jaxrpc-api. -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.saaj-api. -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for property maven.jar.servletapi. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3521022007, vmgump.apache.org:vmgump-public:3521022007 Gump E-mail Identifier (unique within run) #43. -- 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-jelly-tags-soap (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-soap has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 109 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-soap : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-soap-21022007.jar] identifier set to project name -ERROR- No such project [ws-jaxme] for property. -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on Project:commons-jelly-tags-soap -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.axis. -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.jaxrpc-api. -DEBUG- Dependency on ws-axis exists, no need to add for property maven.jar.saaj-api. -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for property maven.jar.servletapi. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-soap/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3521022007, vmgump.apache.org:vmgump-public:3521022007 Gump E-mail Identifier (unique within run) #43. -- 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-jelly-tags-jaxme (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 109 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jaxme : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jaxme-21022007.jar] identifier set to project name -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-js on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-xs on: Maven on Project:commons-jelly-tags-jaxme -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3521022007, vmgump.apache.org:vmgump-public:3521022007 Gump E-mail Identifier (unique within run) #46. -- 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-jelly-tags-jaxme (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 109 runs. The current state of this project is 'Failed', with reason 'Configuration Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jaxme : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-jelly-tags-jaxme-21022007.jar] identifier set to project name -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- No such project [ws-jaxme] for property. -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-js on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-api on: Maven on Project:commons-jelly-tags-jaxme -ERROR- Cannot resolve output/outputpath of *unknown* [ws-jaxme] -ERROR- Unhandled Property: maven.jar.jaxme-xs on: Maven on Project:commons-jelly-tags-jaxme -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: ws-jaxme unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/rss.xml - Atom: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3521022007, vmgump.apache.org:vmgump-public:3521022007 Gump E-mail Identifier (unique within run) #46. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r510126 - /jakarta/commons/proper/fileupload/tags/commons-fileupload-1.2/
Author: jochen Date: Wed Feb 21 10:04:33 2007 New Revision: 510126 URL: http://svn.apache.org/viewvc?view=revrev=510126 Log: Release of 1.2 Added: jakarta/commons/proper/fileupload/tags/commons-fileupload-1.2/ - copied from r510125, jakarta/commons/proper/fileupload/tags/commons-fileupload-1.2rc4/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (EMAIL-64) Use wiser instead of dumbster for test cases
[ https://issues.apache.org/jira/browse/EMAIL-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474783 ] Ben Speakmon commented on EMAIL-64: --- Um, hi Jon, fancy meeting you here. :) So it looks like getting subetha/wiser into the maven repository is on us. We should be good neighbors and upload both the 1.5 and 1.4-compatible versions. I don't know the maven handwave for doing that, and I've never submitted a pom/jar to the repo before; anybody else know how to do it and feel like volunteering? Licensing: boy, am I *NOT* qualified to speak on that topic. Dion? Henri? Use wiser instead of dumbster for test cases Key: EMAIL-64 URL: https://issues.apache.org/jira/browse/EMAIL-64 Project: Commons Email Issue Type: Improvement Affects Versions: 1.1 Reporter: Ben Speakmon Fix For: 1.1 Attachments: dumbster_to_wiser.patch, dumbster_to_wiser_jdk14_pom.diff, dumbster_to_wiser_xdocs.patch Since the test cases depend on a snapshot of the dead project dumbster, the tests should be changed to use the wiser test email server instead. Marking as 1.1 fix since this should get done before 1.1 goes out the door. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Announce: Commons Fileupload 1.2
Hi, the Jakarta Commons team is glad to announce the availability of commons-fileupload 1.2. Commons Fileupload is a framework for handling HTTP file upload requests in servlets, portlets, and similar server side Java applications. Compared to the previous version 1.1.1, the following notable changes have been made: - A streaming API has been added. The streaming API allows to handle arbitrarily large files without intermediary files while still keeping an extremely low memory profile. - The presence of a content-length header is no longer required. - Added support for progress listeners. - Added support for header continuation lines. - Added support for limiting the actual file size, as opposed to the request size. Commons Fileupload 1.2 is available from http://jakarta.apache.org/site/downloads/downloads_commons-fileupload.cgi Jochen Wiedmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 38 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-jsl-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on ant exists, no need to add for property maven.jar.ant-optional. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build) Work ended in a state of : Failed Elapsed: 31 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] 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:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-21022007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21022007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21022007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-21022007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [junit] at org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:64) [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:59) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:263) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:66) [junit] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:113) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:187) [junit] at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:161) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59) [junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80) [junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171) [junit]
[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-fmt-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 38 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly-tags-fmt-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -WARNING- Overriding Maven properties: [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-fmt-test/gump_work/build_commons-jelly_commons-jelly-tags-fmt-test.html Work Name: build_commons-jelly_commons-jelly-tags-fmt-test (Type: Build) Work ended in a state of : Failed Elapsed: 21 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt] 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:/usr/local/gump/packages/bsh-2.0b4/bsh-commands-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-classpath-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-core-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-bsf-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-reflect-2.0b4.jar:/usr/local/gump/packages/bsh-2.0b4/bsh-util-2.0b4.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-21022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21022007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-21022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-21022007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-21022007.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/fmt/target/commons-jelly-tags-fmt-21022007.jar - [junit] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) [junit] at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) [junit] at java.net.URLClassLoader.access$100(URLClassLoader.java:56) [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:195) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [junit] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [junit] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) [junit] at org.apache.commons.jelly.tags.ant.AntTagLibrary.createProject(AntTagLibrary.java:128)
svn commit: r510273 - in /jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl: EnvJexlTestSuite.java StaticMethodTest.java static-method.xml
Author: rahul
Date: Wed Feb 21 14:30:08 2007
New Revision: 510273
URL: http://svn.apache.org/viewvc?view=revrev=510273
Log:
Add a test case illustrating static method invocation, when using JEXL.
Added:
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/StaticMethodTest.java
(with props)
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/static-method.xml
(with props)
Modified:
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/EnvJexlTestSuite.java
Modified:
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/EnvJexlTestSuite.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/EnvJexlTestSuite.java?view=diffrev=510273r1=510272r2=510273
==
---
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/EnvJexlTestSuite.java
(original)
+++
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/EnvJexlTestSuite.java
Wed Feb 21 14:30:08 2007
@@ -49,6 +49,7 @@
TestSuite suite = new TestSuite();
suite.setName(Commons-SCXML JEXL Environment Tests);
suite.addTest(JexlContextTest.suite());
+suite.addTest(StaticMethodTest.suite());
return suite;
}
}
Added:
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/StaticMethodTest.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/StaticMethodTest.java?view=autorev=510273
==
---
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/StaticMethodTest.java
(added)
+++
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/StaticMethodTest.java
Wed Feb 21 14:30:08 2007
@@ -0,0 +1,74 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You 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.jexl;
+
+import java.net.URL;
+import java.util.Set;
+
+import junit.framework.Test;
+import junit.framework.TestCase;
+import junit.framework.TestSuite;
+
+import org.apache.commons.scxml.Context;
+import org.apache.commons.scxml.SCXMLExecutor;
+import org.apache.commons.scxml.SCXMLTestHelper;
+import org.apache.commons.scxml.model.State;
+
+public class StaticMethodTest extends TestCase {
+
+private URL staticmethod;
+
+public StaticMethodTest(String testName) {
+super(testName);
+}
+
+public static Test suite() {
+return new TestSuite(StaticMethodTest.class);
+}
+
+public static void main(String args[]) {
+String[] testCaseName = {StaticMethodTest.class.getName()};
+junit.textui.TestRunner.main(testCaseName);
+}
+
+/**
+ * Set up instance variables required by this test case.
+ */
+public void setUp() {
+staticmethod = this.getClass().getClassLoader().
+getResource(org/apache/commons/scxml/env/jexl/static-method.xml);
+}
+
+/**
+ * Tear down instance variables required by this test case.
+ */
+public void tearDown() {
+staticmethod = null;
+}
+
+public void testJexlStaticMethodInvocation() {
+Context jc = new JexlContext();
+jc.set(System, System.class);
+SCXMLExecutor exec = SCXMLTestHelper.getExecutor(staticmethod,
+jc, new JexlEvaluator());
+Set currentStates = exec.getCurrentStatus().getStates();
+assertEquals(1, currentStates.size());
+assertEquals(static, ((State)currentStates.iterator().
+next()).getId());
+}
+
+}
Propchange:
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/StaticMethodTest.java
--
svn:eol-style = native
Propchange:
jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/StaticMethodTest.java
Re: [VOTE] Release Commons DBCP 1.2.2
On 2/20/07, Jörg Schaible [EMAIL PROTECTED] wrote: Hi Phil, Phil Steitz wrote: On 2/15/07, Jörg Schaible [EMAIL PROTECTED] wrote: Hi Phil, sorry I am late and I downloaded the source package, compiled and run all tests in Gentoo Linux with Maven for Sun JDK 1.4.2, Sun JDK 1.5.0, Blackdown JDK 1.4.2_03, IBM JDK 1.4.2.7, and IBM JDK 1.5.0.3 and all tests run fine for these. It fails for JRockit 1.4.2.11 and 1.5.0.6 though with: I tested with the latest JRockit Linux releases .12 , .8 respectively and the tests all passed. I did see the failure on the 1.5.0.6 release, though. I can't find anything like meaningful release notes for JRockit, so can't tell if this was a bug fix. Any ideas where to release notes for JRockit? Phil == % == Testsuite: org.apache.commons.dbcp.TestBasicDataSource Tests run: 33, Failures: 1, Errors: 0, Time elapsed: 4,364 sec Testcase: testCreateDataSourceCleanupThreads( org.apache.commons.dbcp.TestBasicDataSource): FAILED expected:1 but was:2 junit.framework.AssertionFailedError: expected:1 but was:2 at org.apache.commons.dbcp.TestBasicDataSource.testCreateDataSourceCleanupThreads (TestBasicDataSource.java:334) at jrockit.reflect.VirtualNativeMethodInvoker.invoke( Ljava.lang.Object [Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) == % == Ugh. The test that is failing is to confirm the fix for DBCP-93, which is essentially a thread leak. In retrospect, it was probably not a good idea to include a check of the form assertEquals(threadCount, Thread.activeCount()), as appears in this test, since Thread.activeCount is not really guaranteed to be accurate. In the case of JRockit, the docs mention something to the effect of monitoring threads being spawned periodically. Before the fix, the test case would have orphaned 10 threads, post fix JRockit is reporting one extra thread. I think it is best to do something to fix this, but am not sure what would be best. Eliminating the test is one option, or changing the test to allow one or two extra threads would also work. I see this as a blocker, since this test was introduced in 1.2.2 and the build should succeed on JRockit. Any suggestions? When I try to run the tests from within Eclipse with the JRockit JDK, anything works. OTOH when I tried to run the tests yesterday with Maven under heavy load of my machine (compiling KOffice), the test succeeded also, but two others were failing :-/ Nevertheless, the test above fails on normal terms always on my machine with Maven/JRockit, so it at least repeatable. I looked at the test, but it seems I don't grok from a quick look enough of the internals of dbcp to say anything useful. Since I have some experience with other concurrent tests, what about joining the evictor thread and wait for it to stop (at least for a reasonable time)? If it has a unique name, you can address it from the test ... Additionally, you've realized that the complete package is no longer compatible with JDK 6? I don't know what we can really do about it, since the new JDBC version defines a lot of new methods for java.sql.Statement and java.sql.Connection and - even worse - some of those methods have arguments or return values only avalable in JDK 6. This is being tracked as DBCP-191. We can discuss this post 1.2.2, at which time we may want to create a separate 1.6 branch and version. OK, I did not recognized this. Unless someone comes up with a really clever solution, there's nothing we can do about it and this is not even documented somewhere in the release. Yes, should probably have included DBCP-191 in the significant open issues in the release notes. I will do that. Thanks for the feedback and testing. Cheers, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
