svn commit: r508878 - /jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

2007-02-17 Thread bayard
Author: bayard
Date: Sat Feb 17 22:26:09 2007
New Revision: 508878

URL: http://svn.apache.org/viewvc?view=rev&rev=508878
Log:
Missed a bit of HTML. The versioned issues weren't being linked

Modified:
jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

Modified: jakarta/commons/proper/commons-nightly/trunk/jira-email.vm
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-nightly/trunk/jira-email.vm?view=diff&rev=508878&r1=508877&r2=508878
==
--- jakarta/commons/proper/commons-nightly/trunk/jira-email.vm (original)
+++ jakarta/commons/proper/commons-nightly/trunk/jira-email.vm Sat Feb 17 
22:26:09 2007
@@ -45,7 +45,7 @@
 #if( $notableIssues.size() != 0 )
 
 #foreach( $issue in $notableIssues )
-[$issue.key] ($issue.votes votes | $issue.comments.size() comments) 
$issue.summary
+[https://issues.apache.org/jira/browse/$issue.key";>$issue.key] 
($issue.votes votes | $issue.comments.size() comments) $issue.summary
 #end
 
 #end



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r508874 - /jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

2007-02-17 Thread bayard
Author: bayard
Date: Sat Feb 17 21:57:58 2007
New Revision: 508874

URL: http://svn.apache.org/viewvc?view=rev&rev=508874
Log:
HTMLized

Modified:
jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

Modified: jakarta/commons/proper/commons-nightly/trunk/jira-email.vm
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-nightly/trunk/jira-email.vm?view=diff&rev=508874&r1=508873&r2=508874
==
--- jakarta/commons/proper/commons-nightly/trunk/jira-email.vm (original)
+++ jakarta/commons/proper/commons-nightly/trunk/jira-email.vm Sat Feb 17 
21:57:58 2007
@@ -18,7 +18,9 @@
 ##
 #set( $jira = 
$xmlrpc.connect("${username}:${password}","http://issues.apache.org/jira/rpc/xmlrpc";)
 )
 ##
-Commons JIRA Report
+
+
+Commons JIRA Report
 
 #set( $projects = $jira.getProjects() )
 ##
@@ -27,7 +29,8 @@
 #set( $versions = $jira.getVersions($project_key) )
 #set( $versions = $versions.subtract($versions.equals("id", "-1")) )
 #set( $project = $projects.equals("key", $project_key).get(0) )
-${project.name}
+${project.name} - [https://issues.apache.org/jira/browse/${project.key}";>jira]
+
 ##
 #foreach( $version in $versions )
 ##
@@ -36,11 +39,16 @@
 #set( $issues = $rss.fetch($url).issues )
 #set( $unresolvedIssues = $issues.equals("resolution", "Unresolved") )
 #set( $resolvedIssues = $issues.subtract($unresolvedIssues) )
+#set( $notableIssues = $unresolvedIssues.greater("votes", 1) )
 #if( $issues.size() != 0 )
-  ${version} - ${resolvedIssues.size()} / ${issues.size()}
+https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=${project.id}&fixfor=${version.id}";>${version}
 - ${resolvedIssues.size()} / ${issues.size()}
+#if( $notableIssues.size() != 0 )
+
+#foreach( $issue in $notableIssues )
+[$issue.key] ($issue.votes votes | $issue.comments.size() comments) 
$issue.summary
+#end
+
 #end
-#foreach( $issue in $unresolvedIssues.greater("votes", 1) )
-[$issue.key] ($issue.votes votes | $issue.comments.size() comments) 
$issue.summary 
 #end
 #end
 #end
@@ -48,11 +56,17 @@
 #set( $url = 
"http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&decorator=none&reset=true&pid=${project.id}&fixfor=-1";
 )
 #set( $issues = $rss.fetch($url).issues )
 #set( $issues = $issues.equals("resolution", "Unresolved") )
-  Unversioned - ${issues.size()}
+#if( $issues.size() != 0 )
+https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=${project.id}&fixfor=-1";>Unversioned
 - ${issues.size()}
+
 #foreach( $issue in $issues )
-[$issue.key] ($issue.votes votes | $issue.comments.size() comments) 
$issue.summary 
+[https://issues.apache.org/jira/browse/$issue.key";>$issue.key] 
($issue.votes votes | $issue.comments.size() comments) $issue.summary
 #end
-
+
+#end
+
 #end
+
+
 
 ## Do I need to xmlrpc.logout?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release commons-parent 2

2007-02-17 Thread Jochen Wiedmann

+1

--
Emacs 22 will support MacOS and CygWin. It is not yet decided, whether
these will be used to run Emacs or the other way round.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) failed

2007-02-17 Thread commons-jelly-tags-fmt development
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 32 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: 18 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-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-17022007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-17022007.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-17022007.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)
[ju

[EMAIL PROTECTED]: Project commons-jelly-tags-fmt-test (in module commons-jelly) failed

2007-02-17 Thread commons-jelly-tags-fmt development
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 32 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: 18 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-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/beanshell/target/commons-jelly-tags-beanshell-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-17022007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-17022007.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-17022007.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)
[ju

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-02-17 Thread commons-jelly-tags-jsl development
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 32 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: 26 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-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-17022007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-17022007.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] at

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2007-02-17 Thread commons-jelly-tags-jsl development
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 32 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: 26 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-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-17022007.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-17022007.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-17022007.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-17022007.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] at

Re: [VOTE] Release commons-parent 2

2007-02-17 Thread Henri Yandell

+1

On 2/17/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:

+1

Version 2 needs to be tagged (setting the version number to 2 and
changing the  section to point to the version 2 tag).

Niall

On 2/17/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> It is time to release a new version of commons-parent. There are a
> couple of pending releases that would like to use the features in this
> new version. Here's a run-down on the changes that has been made since
> version 1 was released:
>
> A site.xml file has been added to enable Maven 2 generated sites. It is
> using the new commons-skin to give the sites the commons look-and-feel.
>
> Changes to pom.xml:
> - Add maven-jar-plugin with locked down version. Also add the necessary
> entires into the manifest.
> - Add maven-gpg-plugin used to sign the artifacts during the release.
> - Add standard set of reports: javadoc, jxr, surefire, jdepend.
> - Add rat-maven-plugin.
> - Configure maven-site-plugin to exclude the special Maven 1 files
> navigation.xml and changes.xml from site generation.
> - Make the deployment protocol configurable, uses scp by default.
> - Add snapshot repo for rc profile.
> - Compile properties are now set to 1.3 as a default value. It can be
> overridden by components using another version.
>
> The revision of the last change is 507361.
>
> The vote will be open for the usual 72 hours.
>
> Here's my +1
>
> --
> Dennis Lundberg
>
> -
> 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]



svn commit: r508778 - /jakarta/commons/proper/commons-parent/trunk/NOTICE.txt

2007-02-17 Thread niallp
Author: niallp
Date: Sat Feb 17 08:46:41 2007
New Revision: 508778

URL: http://svn.apache.org/viewvc?view=rev&rev=508778
Log:
Add copyright statement to NOTICE.txt

Modified:
jakarta/commons/proper/commons-parent/trunk/NOTICE.txt

Modified: jakarta/commons/proper/commons-parent/trunk/NOTICE.txt
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk/NOTICE.txt?view=diff&rev=508778&r1=508777&r2=508778
==
--- jakarta/commons/proper/commons-parent/trunk/NOTICE.txt (original)
+++ jakarta/commons/proper/commons-parent/trunk/NOTICE.txt Sat Feb 17 08:46:41 
2007
@@ -1,2 +1,5 @@
+Apache Jakarta Commons Parent
+Copyright 2006-2007 The Apache Software Foundation
+
 This product includes software developed by
 The Apache Software Foundation (http://www.apache.org/).



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release commons-parent 2

2007-02-17 Thread Niall Pemberton

+1

Version 2 needs to be tagged (setting the version number to 2 and
changing the  section to point to the version 2 tag).

Niall

On 2/17/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:

It is time to release a new version of commons-parent. There are a
couple of pending releases that would like to use the features in this
new version. Here's a run-down on the changes that has been made since
version 1 was released:

A site.xml file has been added to enable Maven 2 generated sites. It is
using the new commons-skin to give the sites the commons look-and-feel.

Changes to pom.xml:
- Add maven-jar-plugin with locked down version. Also add the necessary
entires into the manifest.
- Add maven-gpg-plugin used to sign the artifacts during the release.
- Add standard set of reports: javadoc, jxr, surefire, jdepend.
- Add rat-maven-plugin.
- Configure maven-site-plugin to exclude the special Maven 1 files
navigation.xml and changes.xml from site generation.
- Make the deployment protocol configurable, uses scp by default.
- Add snapshot repo for rc profile.
- Compile properties are now set to 1.3 as a default value. It can be
overridden by components using another version.

The revision of the last change is 507361.

The vote will be open for the usual 72 hours.

Here's my +1

--
Dennis Lundberg

-
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]



[VOTE] Release commons-parent 2

2007-02-17 Thread Dennis Lundberg
It is time to release a new version of commons-parent. There are a 
couple of pending releases that would like to use the features in this 
new version. Here's a run-down on the changes that has been made since 
version 1 was released:


A site.xml file has been added to enable Maven 2 generated sites. It is 
using the new commons-skin to give the sites the commons look-and-feel.


Changes to pom.xml:
- Add maven-jar-plugin with locked down version. Also add the necessary 
entires into the manifest.

- Add maven-gpg-plugin used to sign the artifacts during the release.
- Add standard set of reports: javadoc, jxr, surefire, jdepend.
- Add rat-maven-plugin.
- Configure maven-site-plugin to exclude the special Maven 1 files 
navigation.xml and changes.xml from site generation.

- Make the deployment protocol configurable, uses scp by default.
- Add snapshot repo for rc profile.
- Compile properties are now set to 1.3 as a default value. It can be 
overridden by components using another version.


The revision of the last change is 507361.

The vote will be open for the usual 72 hours.

Here's my +1

--
Dennis Lundberg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release commons-fileupload 1.2 (4th attempt)

2007-02-17 Thread Jörg Schaible
Stephen Colebourne wrote:

> Jochen Wiedmann wrote:
>> On 2/16/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
>> 
>>> > (1) The md5 files do not contain the file name, which is standard for
>>> > commons components (see section 2 of [1]).
>>>
>>> This is the way Maven 2 generates *and* checks it. So if you change
>>> those, I
>>> am quite sure, that every M2 user will get always a warning because of
>>> the
>>> checksum!
>> 
>> I believe that Olivers and your concerms can be resolved by proposing
>> that the files that go into /www/www.apache.org/dist are distributed
>> as proposed by Oliver. OTOH, the files that go into the Maven
>> repository won't have a file name.
> 
> See commons-io in the maven2 repository:
>
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-io/commons-io/1.3/commons-io-1.3.jar.md5
> 
> The *filename part is present.
> 
> Does it cause any issues? I don't know, I don't use maven 2. I doubt it
> though as no ones ever complained.

Well, I said *if* any user gets a warning I am -1 to such a change. Honestly
I don't know either, but M2 is not the only software anymore accessing the
public repos. Interfering in the way the deploy plugin works is at current
stage a major hassle and IMHO not worth to prevent a release. If we wanna
have such a change, we have to change the way the plugin works.

- Jörg

- Jörg

> 
> Stephen



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release Commons DBCP 1.2.2

2007-02-17 Thread Niall Pemberton

+1 from me - all looks good, RAT report was clean, rebuilds from
source, tests pass and everything looks in place.

Niall

On 2/12/07, Phil Steitz <[EMAIL PROTECTED]> wrote:

Votes, please.  The vote will close end of day (GMT) 15-Feb-2007.

-
[  ] +1 - Yes, release these bits
[  ] +0  - OK...
[  ] -0  -  OK, but...
[  ] -1  - No, because



-
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

2007-02-17 Thread commons-jelly-tags-jaxme development
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 103 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-17022007.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 2617022007, vmgump.apache.org:vmgump-public:2617022007
Gump E-mail Identifier (unique within run) #44.

--
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

2007-02-17 Thread commons-jelly-tags-jaxme development
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 103 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-17022007.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 2617022007, vmgump.apache.org:vmgump-public:2617022007
Gump E-mail Identifier (unique within run) #44.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release commons-fileupload 1.2 (4th attempt)

2007-02-17 Thread Niall Pemberton

On 2/14/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:


[X] +1
[ ] =0
[ ] -1


I do have a few comments on the site/docs - none of which IMO should
prevent the release - and my +1 vote is unconditional.

There are a couple of maven2 issues with the site generation which
makes me think that it might be better to exclude the site from the
distro (just including the JavaDocs):

- Links are being converted to relative ones, so for example the
Commons & Jakarta links don't work for the site/docs included in the
distro.
- The changes report for m2 doesn't like html markup and entries that
have it appear as blank. For fileupload there are a few such blank
entries in the previous releases section.

I can understand you wanting to get the release out and not wait for
the next Commons POM release - it does mean that the site/docs don't
have the standard Commons L&F and perhaps another reason for excluding
them - but as long as that isn't whats published as the FileUpload web
site, thats the main thing.

Niall

-
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

2007-02-17 Thread commons-jelly-tags-soap development
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 103 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-17022007.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 2617022007, vmgump.apache.org:vmgump-public:2617022007
Gump E-mail Identifier (unique within run) #41.

--
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

2007-02-17 Thread commons-jelly-tags-soap development
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 103 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-17022007.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 2617022007, vmgump.apache.org:vmgump-public:2617022007
Gump E-mail Identifier (unique within run) #41.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [VOTE] Release commons-fileupload 1.2 (4th attempt)

2007-02-17 Thread Stephen Colebourne

Jochen Wiedmann wrote:

On 2/16/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:


> (1) The md5 files do not contain the file name, which is standard for
> commons components (see section 2 of [1]).

This is the way Maven 2 generates *and* checks it. So if you change 
those, I
am quite sure, that every M2 user will get always a warning because of 
the

checksum!


I believe that Olivers and your concerms can be resolved by proposing
that the files that go into /www/www.apache.org/dist are distributed
as proposed by Oliver. OTOH, the files that go into the Maven
repository won't have a file name.


See commons-io in the maven2 repository:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-io/commons-io/1.3/commons-io-1.3.jar.md5

The *filename part is present.

Does it cause any issues? I don't know, I don't use maven 2. I doubt it 
though as no ones ever complained.


Stephen


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[all] jira report

2007-02-17 Thread Henri Yandell

Thought I'd mention this again. It's cron'd nightly:

http://people.apache.org/~bayard/jira-report-for-commons.txt

I often randomly click through the JIRA projects - and it was much
nicer to run down the report and look at each project. The above was
made for an email, but I'll probably go ahead and html it up so the
links are clickable etc.

Interesting things that it implies to me (with a dumb set of mental rules):

Configuration 1.4 is ready for a release (surprise!)
FileUpload 1.2 is ready (shock!)
DBCP 1.2.2 is ready for a release (you're stunned)
CLI 1.1 seems close to a release (no one cares)
JXPath 1.3 is nearly ready (?)
Net 2.0 is ready (?)

Chain 1.3 might be ready for a release
Logging 1.1.1 might be ready for a release (we all know it is)
Pool 2.0 might be ready for a release (probably not I presume)
Net 1.5 might be ready for release

Fixing versions on the Nightly Build seems odd (Digester has 1, Pool
has 4, VFS has 3). You can't later tell what version they went in. If
it was a fix for something like the website and didn't go in a
version, I'd either use the next version or have it have no fix
version.

Hen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r508749 - /jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

2007-02-17 Thread bayard
Author: bayard
Date: Sat Feb 17 02:06:56 2007
New Revision: 508749

URL: http://svn.apache.org/viewvc?view=rev&rev=508749
Log:
Ignore DAEMON

Modified:
jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

Modified: jakarta/commons/proper/commons-nightly/trunk/jira-email.vm
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-nightly/trunk/jira-email.vm?view=diff&rev=508749&r1=508748&r2=508749
==
--- jakarta/commons/proper/commons-nightly/trunk/jira-email.vm (original)
+++ jakarta/commons/proper/commons-nightly/trunk/jira-email.vm Sat Feb 17 
02:06:56 2007
@@ -22,7 +22,7 @@
 
 #set( $projects = $jira.getProjects() )
 ##
-#foreach( $project_key in 
["BEANUTILS","BETWIXT","CHAIN","CLI","CODEC","COLLECTIONS","CONFIGURATION","DAEMON","DBCP","DBUTILS","DIGESTER","EMAIL","FILEUPLOAD","IO","JEXL","JXPATH","LANG","LOGGING","MATH","NET","POOL","SCXML","VALIDATOR","VFS"])
+#foreach( $project_key in 
["BEANUTILS","BETWIXT","CHAIN","CLI","CODEC","COLLECTIONS","CONFIGURATION","DBCP","DBUTILS","DIGESTER","EMAIL","FILEUPLOAD","IO","JEXL","JXPATH","LANG","LOGGING","MATH","NET","POOL","SCXML","VALIDATOR","VFS"])
 ##foreach( $project_key in ["JELLY"])
 #set( $versions = $jira.getVersions($project_key) )
 #set( $versions = $versions.subtract($versions.equals("id", "-1")) )



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (IO-115) FileUtilsCleanDirectoryTestCase fails on Windoes if command chmod is available

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/IO-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated IO-115:
-

Fix Version/s: (was: 1.3.1)
   1.4

> FileUtilsCleanDirectoryTestCase fails on Windoes if command chmod is available
> --
>
> Key: IO-115
> URL: https://issues.apache.org/jira/browse/IO-115
> Project: Commons IO
>  Issue Type: Bug
>  Components: Utilities
>Affects Versions: 1.3.1
>Reporter: Joerg Schaible
> Fix For: 1.4
>
>
> Some tests in FileUtilsCleanDirectoryTestCase try to delete files that have 
> been set to read-only. This is expected to throw an exception. To set the 
> read-only flag the method chmod() tries to execute the unix "chmod" command. 
> If this fails (which should normally be the case on windows), the test is 
> ignored.
> If Posix tools are available e.g. from Cygwin, MKS Toolkit, Microsoft's Posix 
> Tools or similar ones the test fails.

-- 
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] Resolved: (IO-111) FileSystemUtils.freeDiskSpaceUnix does not work if df is not in the shell path

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/IO-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell resolved IO-111.
--

Resolution: Won't Fix

Resolving wontfix as per previous comment.

> FileSystemUtils.freeDiskSpaceUnix does not work if df is not in the shell path
> --
>
> Key: IO-111
> URL: https://issues.apache.org/jira/browse/IO-111
> Project: Commons IO
>  Issue Type: Bug
>Affects Versions: 1.2, 1.3
> Environment: Solaris
>Reporter: Xavier Soudan
>Priority: Minor
>
> if the df command is not in the path, the method freeSpaceUnix throws an 
> exception:
> java.io.IOException: df: not found
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.(UNIXProcess.java:53)
> at java.lang.ProcessImpl.start(ProcessImpl.java:65)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
> at java.lang.Runtime.exec(Runtime.java:591)
> at java.lang.Runtime.exec(Runtime.java:464)
> at 
> org.apache.commons.io.FileSystemUtils.openProcessStream(FileSystemUtils.java:357)
> at 
> org.apache.commons.io.FileSystemUtils.freeSpaceUnix(FileSystemUtils.java:298)
> Rather than expecting df is in the path, it should be searched in the 
> following standard location:
> /usr/bin/df
> /usr/sbin/df
> /bin/df
> /sbin/df
> /usr/ucb/df
> /usr/xpg4/bin/df

-- 
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] Updated: (EMAIL-50) [email] HTML Emails with images don't display in Outlook 2000

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-50:
---

Fix Version/s: 1.1

> [email] HTML Emails with images don't display in Outlook 2000
> -
>
> Key: EMAIL-50
> URL: https://issues.apache.org/jira/browse/EMAIL-50
> Project: Commons Email
>  Issue Type: Improvement
>Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
>Reporter: Andrew Liles
>Priority: Minor
> Fix For: 1.1
>
> Attachments: html-embed-images.patch, HtmlEmail.java.patch, 
> HtmlEmail2.java
>
>
> I was having a problem sending HTML Emails with inline image attachments 
> against
> the client Microsoft Outlook 2000 SP-3.  I am using commons-email-1.0.jar.
> This bug report proposes a solution include code.
> Suppose with an HtmlEmail I am embedding 2 images, adding an HTML part and 
> Text
> part.
> The resultant Body structure is:
> EntityContent-TypeEncoding
> 1 text/plain  7bit
> 2 multipart/related
> 2.1   text/html   7bit
> 2.2   image/jpeg  base64
> 2.3   image/jpeg  base64
> Outlook, by default, shows the text part with the HTML email as an attachment
> (correctly showing the images).  My "problem" is that I think the HTML should 
> be
> shown by default.
> I am guessing that it is an issue with this particular email client and the 
> Body
> Structure format ?  (see here, for example: COM-1526)
> ---
> I have fixed this for my own purposes and am recording the details here for 
> the
> benefit of others.  I don't know whether this should be categorised as a bug 
> in
> commons-email-1.0.jar or a bug in Outlook.  I suspect the latter, but since 
> back
> versions of Outlook will never get fixed, the pragmatic solution is to alter
> commons-email, particularly in cases if you are targeting a known finite set 
> of
> email clients.
> I am fully expecting a committer to categorize this as WONTFIX, but at least 
> the
> attachment I will add may allow others to use my code.
> My code has been tested to work on:
>   Microsoft Outlook Express 6.00
>   Microsoft Outlook 2000 SP-3
>   Microsoft Outlook 2002
>   Microsoft Outlook 2003 
>   Qualcomm Eudora 6.0.3.0
>   SquirrelMail 1.5.1 (webmail client)
>   Hotmail (as of November 2005)
>   Gmail (as of November 2005)
> These clients are all happy to receive and display HTML emails in the expected
> way using this Body Structure:
> EntityContent-TypeEncoding
> 1 multipart/alternative 
> 1.1   text/plain  7bit
> 1.2   text/html   7bit
> 2 image/jpeg  base64
> 3 image/jpeg  base64
> I have not tested with attachments that do not relate to the HTML and may not
> support this scenario; however this is not normal usage scenario (well, for me
> anyway).

-- 
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] Commented: (EMAIL-56) [Email] Parsing MIME content.

2007-02-17 Thread Henri Yandell (JIRA)

[ 
https://issues.apache.org/jira/browse/EMAIL-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473909
 ] 

Henri Yandell commented on EMAIL-56:


(Setting fixVersion to 1.1 not to imply that it should be fixed in 1.1, but 
that a decision should be made on this issue as a part of 1.1)

> [Email] Parsing MIME content.
> -
>
> Key: EMAIL-56
> URL: https://issues.apache.org/jira/browse/EMAIL-56
> Project: Commons Email
>  Issue Type: Improvement
> Environment: Operating System: Windows XP
> Platform: Other
>Reporter: Jose M. Ordax
>Priority: Minor
> Fix For: 1.1
>
>
> This is not a bug, it is a Feature Request.
> It should be nice if the framework implements a way to create a 
> MultiPartMessage
> from an InputStream or a String with all the content of a real message got 
> from
> a POP3 or NNTP server.
> Currently it seems you have to create it manually adding headers and parts via
> methods. And I think in this way is not really useful.
> Thanks,
>Chemi.

-- 
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] Updated: (EMAIL-52) [email] Identical Inline images should share same BodyPart

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-52:
---

Fix Version/s: 1.1

> [email] Identical Inline images should share same BodyPart
> --
>
> Key: EMAIL-52
> URL: https://issues.apache.org/jira/browse/EMAIL-52
> Project: Commons Email
>  Issue Type: Improvement
>Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
>Reporter: Andrew Liles
>Priority: Minor
> Fix For: 1.1
>
>
> If you have an HTML email with "spacer.gif" repeated several times, then you 
> get
> that image included several times in the payload of the email.  An 
> optimization
> would be to "share" the sid across the several references.
> I have adapted HTMLEmail for my own purposes, and one of the "fixes" I have
> added is just such an optimization.
> Please could a Committer register their interest in this, and I will make a
> patch and submit for your consideration.

-- 
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] Updated: (EMAIL-54) [email] Add new class Charset

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-54:
---

Fix Version/s: 1.1

> [email] Add new class Charset
> -
>
> Key: EMAIL-54
> URL: https://issues.apache.org/jira/browse/EMAIL-54
> Project: Commons Email
>  Issue Type: Improvement
>Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
>Reporter: Piero Ottuzzi
>Priority: Minor
> Fix For: 1.1
>
> Attachments: charset-support.patch, Charset.java, Email.java.patch
>
>
> Add new class Charset the let the whole thing extensible and less error prone

-- 
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] Updated: (EMAIL-28) [email] Problems with HTML emails with attachments and embedded images

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-28:
---

Fix Version/s: 1.1

> [email] Problems with HTML emails with attachments and embedded images
> --
>
> Key: EMAIL-28
> URL: https://issues.apache.org/jira/browse/EMAIL-28
> Project: Commons Email
>  Issue Type: Bug
>Affects Versions: 1.0
> Environment: Operating System: Windows XP
> Platform: PC
>Reporter: Phil Bretherton
> Fix For: 1.1
>
>
> I have three problems that are probably related. The results are using Mozilla
> Thunderbird.
> 1. When I send an HtmlEmail with attachments, embedded images, an HTML body 
> and
> an alternative text body both the alternative text and the HTML are displayed.
> 2. When I send an HtmlEmail with embedded images, no attachments, an HTML body
> and I do not provide an alternative text body, the HTML body is not displayed.
> 3. When I send an HtmlEmail with attachments, embedded images, an HTML body 
> and
> I do not provide an alternative text, everything works almost fine. The only
> problem is that when the SMTP server is sending emails outside its domain it
> adds a disclaimer. The addition of this disclaimer means that only the
> disclaimer is displayed. This does not happend when using Javamail.
> Below is the class that I used for my tests.
> import java.net.MalformedURLException;
> import java.net.URL;
> import org.apache.commons.mail.EmailAttachment;
> import org.apache.commons.mail.EmailException;
> import org.apache.commons.mail.HtmlEmail;
> public class CommonsEmailTest {
>   /**
>* @param args
>*/
>   public static void main(String[] args) {
>   try {
>   testHtmlEmailWithAttachmentsAndEmbeddedImages();
>   testHtmlEmailWithoutAttachmentsOrText();
>   testHtmlEmailWithAttachmentsAndEmbeddedImagesNoText();
>   } catch (MalformedURLException e) {
>   e.printStackTrace();
>   } catch (EmailException e) {
>   e.printStackTrace();
>   }
>   }
>   
>   /**
>* This method sends an HTML email with attachments, embedded images,
>* an HTML body and an alternative text body. The result is that both
>* the HTML and the text are displayed.
>* 
>* @throws EmailException
>* @throws MalformedURLException
>*/
>   public static void testHtmlEmailWithAttachmentsAndEmbeddedImages() 
> throws
> EmailException, MalformedURLException {
>   
>   // Create the email message
>   HtmlEmail email = new HtmlEmail();
>   email.setHostName("smtp.capgemini.fr");
>   email.addTo("[EMAIL PROTECTED]", "You");
>   email.setFrom("[EMAIL PROTECTED]", "Me");
>   email.setSubject("Test email with inline image and attachment");
>   
>   // Create the attachment
>   EmailAttachment attachment = new EmailAttachment();
>   attachment.setPath("D:/temp/mypic.jpg");
>   attachment.setDisposition(EmailAttachment.ATTACHMENT);
>   attachment.setDescription("A picture");
>   attachment.setName("Thingy");
>   
>   email.attach(attachment);
>   // embed the image and get the content id
>   URL url = new 
> URL("http://www.apache.org/images/asf_logo_wide.gif";);
>   String cid = email.embed(url, "Apache logo");
>   // set the html message
>   email.setHtmlMsg("The apache logo -  src=\"cid:"+cid+"\">");
>   // set the alternative message
>   email.setTextMsg("Your email client does not support HTML 
> messages");
>   // send the email
>   email.send();   
>   }
>   /**
>* This method sends an HTML email with embedded images,
>* an HTML body and no alternative text body. The result is that both
>* the HTML is not displayed.
>* 
>* @throws EmailException
>* @throws MalformedURLException
>*/
>   public static void testHtmlEmailWithoutAttachmentsOrText() throws
> EmailException, MalformedURLException {
>   
>   // Create the email message
>   HtmlEmail email = new HtmlEmail();
>   email.setHostName("smtp.capgemini.fr");
>   email.addTo("[EMAIL PROTECTED]", "You");
>   email.setFrom("[EMAIL PROTECTED]", "Me");
>   email.setSubject("Test email with inline image and no 
> alternative text");
>   
>   // embed the image and get the content id
>   URL ur

[jira] Updated: (EMAIL-14) [email] not support content charset gb2312

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-14:
---

Fix Version/s: 1.1

> [email] not support content  charset gb2312
> ---
>
> Key: EMAIL-14
> URL: https://issues.apache.org/jira/browse/EMAIL-14
> Project: Commons Email
>  Issue Type: Bug
>Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
>Reporter: locka
> Fix For: 1.1
>
> Attachments: commons-email-utf8.patch.txt, patch.java
>
>
> when i try the example :
> Email email=new SimpleEmail();
>   email.setHostName("129.1.1.129");
>   email.setAuthentication("admin","1");
>   email.addTo("[EMAIL PROTECTED]", "wjq");
>   email.setFrom("[EMAIL PROTECTED]", "Me");
>   email.setCharset("gb2312");
>   email.setSubject("²âÊÔ¼òµ¥Óʼþ");
>   email.setMsg("ÕâÊDzâÊÔ¼òµ¥Óʼþ");   
>   email.send();   
> the received mail content like "" ,when change Email.TEXT_PLAIN 
> = "text/plain" to  TEXT_PLAIN = "text/plain;charset=gb2312"  , all are right

-- 
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] Updated: (EMAIL-56) [Email] Parsing MIME content.

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-56:
---

Fix Version/s: 1.1

> [Email] Parsing MIME content.
> -
>
> Key: EMAIL-56
> URL: https://issues.apache.org/jira/browse/EMAIL-56
> Project: Commons Email
>  Issue Type: Improvement
> Environment: Operating System: Windows XP
> Platform: Other
>Reporter: Jose M. Ordax
>Priority: Minor
> Fix For: 1.1
>
>
> This is not a bug, it is a Feature Request.
> It should be nice if the framework implements a way to create a 
> MultiPartMessage
> from an InputStream or a String with all the content of a real message got 
> from
> a POP3 or NNTP server.
> Currently it seems you have to create it manually adding headers and parts via
> methods. And I think in this way is not really useful.
> Thanks,
>Chemi.

-- 
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] Updated: (EMAIL-1) [email] setCharset() in Email does not set the charset for the message content

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-1:
--

Fix Version/s: 1.1

> [email] setCharset() in Email does not set the charset for the message content
> --
>
> Key: EMAIL-1
> URL: https://issues.apache.org/jira/browse/EMAIL-1
> Project: Commons Email
>  Issue Type: Bug
>Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
>Reporter: James Mc Millan
> Fix For: 1.1
>
> Attachments: email-1.patch
>
>
> Hello
> More accurately, the charset is not used in buildMimeMessage() as it is not 
> part
> of the contentType used when calling message.setContent(). Since
> setContentType() updates the charset, I think it makes for setCharset() to
> update the contentType?
> James

-- 
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] Updated: (EMAIL-35) [email] Embedding raw DataSource Attachments

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-35:
---

Fix Version/s: 1.1

> [email] Embedding raw DataSource Attachments
> 
>
> Key: EMAIL-35
> URL: https://issues.apache.org/jira/browse/EMAIL-35
> Project: Commons Email
>  Issue Type: Bug
>Affects Versions: 1.0
> Environment: Operating System: All
> Platform: All
>Reporter: Brandon Wolfe
> Fix For: 1.1
>
> Attachments: EnhancedHtmlEmail.java, HtmlEmail.patch, 
> HtmlEmailTest.patch
>
>
> I kick myself for not submitting this prior to 1.0.  An important feature
> missing from org.apache.commons.mail.HtmlEmail is the ability to embed an
> arbitrary DataSource object.  The current API only allows you to embed from a
> URL.  My usage of CommonsEmail often includes the generation of image data
> on-the-fly, where it does not exist at a pre-defined URL.  
> I propose the addition of a key method:
> public String embed(DataSource datasource, String name, String cid) throws
> EmailException
> This will allow us to attach our own datasources in addition to defining our 
> own
> content-ids.  Helper methods can be created to auto-generate CIDs when needed
> and allow for backwards compatability.  I've found that being able to provide 
> my
> own defined CIDs has been very helpful in referencing them in my velocity 
> email
> templates.
> I will attach the current EnhancedHtmlEmail class that I have been using for a
> year or so.  It extends HtmlEmail to provide the methods explained above.  I
> would hope to have this capability introduced into the HtmlEmail class.
> Feel free to contact me to discuss further!  Thanks.

-- 
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] Updated: (EMAIL-25) [email] Address char-set can not be individually set

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/EMAIL-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated EMAIL-25:
---

Fix Version/s: 1.1
Affects Version/s: 1.0

> [email] Address char-set can not be individually set
> 
>
> Key: EMAIL-25
> URL: https://issues.apache.org/jira/browse/EMAIL-25
> Project: Commons Email
>  Issue Type: Bug
>Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
>Reporter: James Huang
>Priority: Critical
> Fix For: 1.1
>
>
> The commons-email-1.0 release API has a critical flaw: you can't specify char-
> set for individual addresses. This is the case with some Japanese mail 
> systems.
> Currently, org.apache.commons.mail.Email class only has methods like
>add(String email, String name);
> but no such methods:
>addXXX(String email, String name, String charset);
> In addition, I believe the API should allow
>addXXX(javax.mail.internt.InternetAddress);
> If you want to hide InternetAddress, I don't mind to even have a 
> addXXX(Object).
> Thanks,
> -James Huang

-- 
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] Commented: (BEANUTILS-269) Boolean Support

2007-02-17 Thread Henri Yandell (JIRA)

[ 
https://issues.apache.org/jira/browse/BEANUTILS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473908
 ] 

Henri Yandell commented on BEANUTILS-269:
-

If you look in the BeanUtils tests, you'll see that the isXxx pattern is tested 
for by various tests on the TestBean.isBooleanSecond method. So it seems that 
BeanUtils supports it.

However, BeanUtils doesn't have anything to do with xpath. Do you have the 
wrong project?

> Boolean Support
> ---
>
> Key: BEANUTILS-269
> URL: https://issues.apache.org/jira/browse/BEANUTILS-269
> Project: Commons BeanUtils
>  Issue Type: New Feature
>Affects Versions: 1.7.0
>Reporter: maomaode
>
> I have a bean class "Cache" which is generated from jaxb , which has the 
> isEnable method, i can not use the xpath expression "/cache/enable"to retrive 
> the result, is that means BeanUtils only support setXXX getXXX? not support 
> isXXX for boolean values?

-- 
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] Updated: (BEANUTILS-265) Allow access to public methods from not public classes

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/BEANUTILS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated BEANUTILS-265:


Fix Version/s: LATER THAN 1.8.0

> Allow access to public methods from not public classes
> --
>
> Key: BEANUTILS-265
> URL: https://issues.apache.org/jira/browse/BEANUTILS-265
> Project: Commons BeanUtils
>  Issue Type: New Feature
>  Components: Bean / Property Utils
>Affects Versions: 1.7.0
>Reporter: Tom Schindl
> Fix For: LATER THAN 1.8.0
>
> Attachments: beanutils.txt
>
>
> Currently BeanUtils doesn't provide the possibility to access getters and 
> setters in classes who are package-scoped!
> ---8<---
> class HiddenBean {
>   private String a;
>   
>   protected HiddenBean() {
>   
>   }
>   
>   public void setA(String a) {
>   this.a = a;
>   }
>   
>   public String getA() {
>   return this.a;
>   }
> }
> public class PublicBean extends HiddenBean {
> }
> ---8<---

-- 
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] Resolved: (BEANUTILS-209) [beanutils] Change propertyUtilsBean.findNextNestedIndex(String) modifier to protected ?

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/BEANUTILS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell resolved BEANUTILS-209.
-

Resolution: Won't Fix

No objections recorded, so wontfixing.

> [beanutils] Change propertyUtilsBean.findNextNestedIndex(String) modifier to 
> protected ?
> 
>
> Key: BEANUTILS-209
> URL: https://issues.apache.org/jira/browse/BEANUTILS-209
> Project: Commons BeanUtils
>  Issue Type: Improvement
>  Components: Expression Syntax
> Environment: Operating System: All
> Platform: All
>Reporter: Marc DeXeT
>Priority: Minor
>
> Could be be changed findNextNestedIndex modifier from "private" to "protected"
> ?
> It's to avoid to senselessly copy out this algo in custom PropertyUtilsBean
> subclasses to get exactly same feature.
> Thanks.

-- 
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] Resolved: (BEANUTILS-206) Check registered Converters for super classes if not found

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/BEANUTILS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell resolved BEANUTILS-206.
-

Resolution: Won't Fix

No views expressed since I suggested resolving this wontfix, so doing so.

> Check registered Converters for super classes if not found
> --
>
> Key: BEANUTILS-206
> URL: https://issues.apache.org/jira/browse/BEANUTILS-206
> Project: Commons BeanUtils
>  Issue Type: Improvement
>  Components: ConvertUtils & Converters
> Environment: Operating System: other
> Platform: Other
>Reporter: ittay
>Priority: Minor
>
> 1. add the ability to register other converters
> 2. if no converter is registered for a class, check if there is a converter 
> for
> one of its super classes. if not, try to find if the class has a conversion
> method (e.g., convert(String))
> thanx,
> ittay

-- 
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] Resolved: (BEANUTILS-187) [beanutils] Methods ConvertUtilsBean.convert could check for converters registered with base classes

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/BEANUTILS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell resolved BEANUTILS-187.
-

Resolution: Won't Fix

No views expressed since I suggested resolving this wontfix, so doing so.

> [beanutils] Methods ConvertUtilsBean.convert could check for converters 
> registered with base classes
> 
>
> Key: BEANUTILS-187
> URL: https://issues.apache.org/jira/browse/BEANUTILS-187
> Project: Commons BeanUtils
>  Issue Type: Improvement
>  Components: ConvertUtils & Converters
> Environment: Operating System: other
> Platform: Other
>Reporter: Alexander Borschet
>Priority: Minor
>
> When converting a value to a class instance it is possible tu register user
> defined classes that implement the converter interface.
> The method convert(String value, Class clazz) in ConvertUtilsBean tries to get
> an instance of a converter class simply by checking the collection of 
> registered
> converters.
> Unfortunately converters that have been registered for super classes are not
> considered.
> REQUEST: How about improving the method convert by the following code lines:
> Class baseclazz = clazz;
> Converter converter = null;
> do {
>   converter = (Converter) converters.get(baseclazz);
>   if (converter != null)
>   break;
>   baseclazz = clazz.getSuperclass();
> } while (baseclazz != null);

-- 
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] Updated: (CODEC-53) build.xml "dist" target refers to ../LICENSE

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/CODEC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated CODEC-53:
---

Fix Version/s: (was: Nightly Builds)

> build.xml "dist" target refers to ../LICENSE
> 
>
> Key: CODEC-53
> URL: https://issues.apache.org/jira/browse/CODEC-53
> Project: Commons Codec
>  Issue Type: Bug
>Affects Versions: 1.3
> Environment: Cygwin 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin
> But probably applicable to any system
>Reporter: Max Polk
>Priority: Minor
>
> The source distribution for commons-codec-1.3/build.xml file has a "dist" and 
> "jar" targets that refer to ../LICENSE which does not exist.  Therefore, an 
> "ant dist" build fails at the "copy" tasks that refer to this missing file 
> one directory *back* from the unpacked "commons-codec-1.3" directory, such as:
> BUILD FAILED
> C:\Apps\Libraries\Java\commons-codec-1.3\build.xml:93: Warning: Could not 
> find file C:\Apps\Libraries\Java\LICENSE to copy.
> Please (1) include the LICENSE file itself in "commons-codec-1.3" directory, 
> and then (2) fix lines 93 and 100 of build.xml to refer to "LICENSE" and not 
> "../LICENSE".

-- 
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: (COMMONSSITE-15) Only show open voted on issues

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/COMMONSSITE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed COMMONSSITE-15.


Resolution: Fixed

svn ci -m "Nice and easy - fixing COMMONSSITE-15 so that only unresolved issues 
are listed when showing the ones with votes" jira-email.vm
Sendingjira-email.vm
Transmitting file data .
Committed revision 508745.

> Only show open voted on issues
> --
>
> Key: COMMONSSITE-15
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-15
> Project: Commons All
>  Issue Type: Improvement
>  Components: Nightly
>Reporter: Henri Yandell
> Assigned To: Henri Yandell
>
> When showing the list of voted on issues in a version, only show them for the 
> unresolved issues.

-- 
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]



svn commit: r508745 - /jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

2007-02-17 Thread bayard
Author: bayard
Date: Sat Feb 17 01:27:18 2007
New Revision: 508745

URL: http://svn.apache.org/viewvc?view=rev&rev=508745
Log:
Nice and easy - fixing COMMONSSITE-15 so that only unresolved issues are listed 
when showing the ones with votes

Modified:
jakarta/commons/proper/commons-nightly/trunk/jira-email.vm

Modified: jakarta/commons/proper/commons-nightly/trunk/jira-email.vm
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/commons-nightly/trunk/jira-email.vm?view=diff&rev=508745&r1=508744&r2=508745
==
--- jakarta/commons/proper/commons-nightly/trunk/jira-email.vm (original)
+++ jakarta/commons/proper/commons-nightly/trunk/jira-email.vm Sat Feb 17 
01:27:18 2007
@@ -39,7 +39,7 @@
 #if( $issues.size() != 0 )
   ${version} - ${resolvedIssues.size()} / ${issues.size()}
 #end
-#foreach( $issue in $issues.greater("votes", 1) )
+#foreach( $issue in $unresolvedIssues.greater("votes", 1) )
 [$issue.key] ($issue.votes votes | $issue.comments.size() comments) 
$issue.summary 
 #end
 #end



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (COMMONSSITE-15) Only show open voted on issues

2007-02-17 Thread Henri Yandell (JIRA)
Only show open voted on issues
--

 Key: COMMONSSITE-15
 URL: https://issues.apache.org/jira/browse/COMMONSSITE-15
 Project: Commons All
  Issue Type: Improvement
  Components: Nightly
Reporter: Henri Yandell
 Assigned To: Henri Yandell


When showing the list of voted on issues in a version, only show them for the 
unresolved issues.

-- 
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] Updated: (CHAIN-23) [chain] Support for new CatalogFactory

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/CHAIN-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated CHAIN-23:
---

Fix Version/s: 1.0

> [chain] Support for new CatalogFactory
> --
>
> Key: CHAIN-23
> URL: https://issues.apache.org/jira/browse/CHAIN-23
> Project: Commons Chain
>  Issue Type: Improvement
>Affects Versions: Nightly Builds
> Environment: Operating System: other
> Platform: Other
>Reporter: sean schofield
>Priority: Minor
> Fix For: 1.0
>
> Attachments: CatalogFactory.patch, CatalogFactoryBase.java, 
> CatalogFactoryBaseTestCase.java
>
>
> We need a CatalogFactoryBase (int the 'impl' pacakage) to go along with the 
> new CatalogFactory interace.  I will submit the necessary file and test case. 
>  
> Craig, please ignore the CatalogFactoryBase that was sent to the commons-dev 
> mailing list directly by me (yesterday).  I fixed a minor bug that I 
> discovered when I wrote my test case.  I know ... that will learn me to write 
> my test case first!

-- 
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] Updated: (CHAIN-22) [Chain] [PATCH] CatalogBase improvements

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/CHAIN-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated CHAIN-22:
---

Fix Version/s: 1.0

> [Chain] [PATCH] CatalogBase improvements
> 
>
> Key: CHAIN-22
> URL: https://issues.apache.org/jira/browse/CHAIN-22
> Project: Commons Chain
>  Issue Type: Improvement
>Affects Versions: Nightly Builds
> Environment: Operating System: All
> Platform: All
>Reporter: Matthew Sgarlata
>Priority: Minor
> Fix For: 1.0
>
> Attachments: CatalogBase.patch
>
>
> Added JavaDoc and a toString() method.

-- 
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] Updated: (LANG-65) [lang] Expose DateIterator or add DateUtils.iterator(startDate, endDate)

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated LANG-65:
--

Issue Type: Improvement  (was: Bug)

> [lang] Expose DateIterator or add DateUtils.iterator(startDate, endDate)
> 
>
> Key: LANG-65
> URL: https://issues.apache.org/jira/browse/LANG-65
> Project: Commons Lang
>  Issue Type: Improvement
> Environment: Operating System: other
> Platform: Other
>Reporter: Ben Munat
> Fix For: 3.0
>
>
> The DateUtils.iterator methods only work with the preset date ranges indicated
> by constants in the class. It would be very useful to be able to iterate 
> through
> each day between a user-specified start date and an end date. 
> This could be as simple as making the static DateIterator inner class of
> DateUtils public (it's package protected now). Or, if that's not appealing for
> some reason, another iterator method could be added that takes the start date
> and end date and returns a DateIterator instance as Iterator.

-- 
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: (LANG-319) CharEncodingTest fails in IBM JDK 1.4.2

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed LANG-319.
--

Resolution: Won't Fix

> CharEncodingTest fails in IBM JDK 1.4.2
> ---
>
> Key: LANG-319
> URL: https://issues.apache.org/jira/browse/LANG-319
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
> Environment: Gentoo Linux, IBM JDK 1.4.2_5
>Reporter: Joerg Schaible
> Assigned To: Joerg Schaible
>Priority: Minor
> Fix For: Known Issue
>
>
> The test CharEncodingTest.testNotSupported tests with invalid character 
> encodings. According the JDK docu of String(byte[], String) the JDK should 
> throw in this case an java.lang.UnsupportedCharacterEncoding exception, but 
> the IBM JDK 1.4.2 throws java.nio.charset.IllegalCharsetNameException. This 
> is not an issue with IBM JDK 1.5.0_3 anymore.

-- 
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: (LANG-318) HashCodeBuilderTest and ToStringBuilderTest fail with IBM JDK 1.4.2

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed LANG-318.
--

Resolution: Won't Fix

I don't see any reason to have the unit tests not run for this - makes them 
more honest and we don't need the IBM 1.4.2 JVM to develop with. Marking as 
WONTFIX as it's a JVM bug (they fixed in 1.5 so presuming it's considered so).

> HashCodeBuilderTest and ToStringBuilderTest fail with IBM JDK 1.4.2
> ---
>
> Key: LANG-318
> URL: https://issues.apache.org/jira/browse/LANG-318
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
> Environment: Gentoo Linux, IBM JDK 1.4.2_5
>Reporter: Joerg Schaible
>Priority: Minor
> Fix For: Known Issue
>
>
> The IBM JDK 1.4.2 reports the declared fields of a class in reverse 
> declaration order. The tests are affected by this:
> {noformat}
> Testsuite: org.apache.commons.lang.builder.BuilderTestSuite
> Tests run: 263, Failures: 8, Errors: 0, Time elapsed: 0,451 sec
> Testcase:
> testReflectionHierarchyHashCode(org.apache.commons.lang.builder.HashCodeBuilderTest):
> FAILED
> expected:<11785967> but was:<1276487>
> junit.framework.AssertionFailedError: expected:<11785967> but was:<1276487>
> at
> org.apache.commons.lang.builder.HashCodeBuilderTest.testReflectionHierarchyHashCode(HashCodeBuilderTest.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testReflectionHashCodeExcludeFields(org.apache.commons.lang.builder.HashCodeBuilderTest):
> FAILED
> expected:<862547> but was:<865283>
> junit.framework.AssertionFailedError: expected:<862547> but was:<865283>
> at
> org.apache.commons.lang.builder.HashCodeBuilderTest.testReflectionHashCodeExcludeFields(HashCodeBuilderTest.java:480)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testReflectionHierarchyArrayList(org.apache.commons.lang.builder.ToStringBuilderTest):
> FAILED
> expected:<...elementData={,},size=0...>
> but
> was:<...size=0,elementData={,}...>
> junit.framework.ComparisonFailure:
> expected:<...elementData={,},size=0...>
> but
> was:<...size=0,elementData={,}...>
> at
> org.apache.commons.lang.builder.ToStringBuilderTest.testReflectionHierarchyArrayList(ToStringBuilderTest.java:327)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testReflectionHierarchy(org.apache.commons.lang.builder.ToStringBuilderTest):
> FAILED
> expected:<...a=a,transientA=t...> but was:<...transientA=t,a=a...>
> junit.framework.ComparisonFailure: expected:<...a=a,transientA=t...> but
> was:<...transientA=t,a=a...>
> at
> org.apache.commons.lang.builder.ToStringBuilderTest.testReflectionHierarchy(ToStringBuilderTest.java:338)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testSelfInstanceTwoVarsReflectionObjectCycle(org.apache.commons.lang.builder.ToStringBuilderTest):
> FAILED
> expected:<[EMAIL PROTECTED],otherType=The
> Other Type...> but was:<...otherType=The Other
> Type,[EMAIL PROTECTED]>
> junit.framework.ComparisonFailure:
> expected:<[EMAIL PROTECTED],otherType=The
> Other Type...> but was:<...otherType=The Other
> Type,[EMAIL PROTECTED]>
> at
> org.apache.commons.lang.builder.ToStringBuilderTest.testSelfInstanceTwoVarsReflectionObjectCycle(ToStringBuilderTest.java:543)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invo

[jira] Updated: (LANG-319) CharEncodingTest fails in IBM JDK 1.4.2

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated LANG-319:
---

Fix Version/s: (was: 2.3)
   Known Issue

> CharEncodingTest fails in IBM JDK 1.4.2
> ---
>
> Key: LANG-319
> URL: https://issues.apache.org/jira/browse/LANG-319
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
> Environment: Gentoo Linux, IBM JDK 1.4.2_5
>Reporter: Joerg Schaible
> Assigned To: Joerg Schaible
>Priority: Minor
> Fix For: Known Issue
>
>
> The test CharEncodingTest.testNotSupported tests with invalid character 
> encodings. According the JDK docu of String(byte[], String) the JDK should 
> throw in this case an java.lang.UnsupportedCharacterEncoding exception, but 
> the IBM JDK 1.4.2 throws java.nio.charset.IllegalCharsetNameException. This 
> is not an issue with IBM JDK 1.5.0_3 anymore.

-- 
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] Updated: (LANG-318) HashCodeBuilderTest and ToStringBuilderTest fail with IBM JDK 1.4.2

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated LANG-318:
---

Fix Version/s: (was: 3.0)
   Known Issue

> HashCodeBuilderTest and ToStringBuilderTest fail with IBM JDK 1.4.2
> ---
>
> Key: LANG-318
> URL: https://issues.apache.org/jira/browse/LANG-318
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
> Environment: Gentoo Linux, IBM JDK 1.4.2_5
>Reporter: Joerg Schaible
>Priority: Minor
> Fix For: Known Issue
>
>
> The IBM JDK 1.4.2 reports the declared fields of a class in reverse 
> declaration order. The tests are affected by this:
> {noformat}
> Testsuite: org.apache.commons.lang.builder.BuilderTestSuite
> Tests run: 263, Failures: 8, Errors: 0, Time elapsed: 0,451 sec
> Testcase:
> testReflectionHierarchyHashCode(org.apache.commons.lang.builder.HashCodeBuilderTest):
> FAILED
> expected:<11785967> but was:<1276487>
> junit.framework.AssertionFailedError: expected:<11785967> but was:<1276487>
> at
> org.apache.commons.lang.builder.HashCodeBuilderTest.testReflectionHierarchyHashCode(HashCodeBuilderTest.java:166)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testReflectionHashCodeExcludeFields(org.apache.commons.lang.builder.HashCodeBuilderTest):
> FAILED
> expected:<862547> but was:<865283>
> junit.framework.AssertionFailedError: expected:<862547> but was:<865283>
> at
> org.apache.commons.lang.builder.HashCodeBuilderTest.testReflectionHashCodeExcludeFields(HashCodeBuilderTest.java:480)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testReflectionHierarchyArrayList(org.apache.commons.lang.builder.ToStringBuilderTest):
> FAILED
> expected:<...elementData={,},size=0...>
> but
> was:<...size=0,elementData={,}...>
> junit.framework.ComparisonFailure:
> expected:<...elementData={,},size=0...>
> but
> was:<...size=0,elementData={,}...>
> at
> org.apache.commons.lang.builder.ToStringBuilderTest.testReflectionHierarchyArrayList(ToStringBuilderTest.java:327)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testReflectionHierarchy(org.apache.commons.lang.builder.ToStringBuilderTest):
> FAILED
> expected:<...a=a,transientA=t...> but was:<...transientA=t,a=a...>
> junit.framework.ComparisonFailure: expected:<...a=a,transientA=t...> but
> was:<...transientA=t,a=a...>
> at
> org.apache.commons.lang.builder.ToStringBuilderTest.testReflectionHierarchy(ToStringBuilderTest.java:338)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testSelfInstanceTwoVarsReflectionObjectCycle(org.apache.commons.lang.builder.ToStringBuilderTest):
> FAILED
> expected:<[EMAIL PROTECTED],otherType=The
> Other Type...> but was:<...otherType=The Other
> Type,[EMAIL PROTECTED]>
> junit.framework.ComparisonFailure:
> expected:<[EMAIL PROTECTED],otherType=The
> Other Type...> but was:<...otherType=The Other
> Type,[EMAIL PROTECTED]>
> at
> org.apache.commons.lang.builder.ToStringBuilderTest.testSelfInstanceTwoVarsReflectionObjectCycle(ToStringBuilderTest.java:543)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
> Testcase:
> testSimpleReflectionStatics(org.apache.co

[jira] Reopened: (LANG-319) CharEncodingTest fails in IBM JDK 1.4.2

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell reopened LANG-319:



> CharEncodingTest fails in IBM JDK 1.4.2
> ---
>
> Key: LANG-319
> URL: https://issues.apache.org/jira/browse/LANG-319
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
> Environment: Gentoo Linux, IBM JDK 1.4.2_5
>Reporter: Joerg Schaible
> Assigned To: Joerg Schaible
>Priority: Minor
> Fix For: Known Issue
>
>
> The test CharEncodingTest.testNotSupported tests with invalid character 
> encodings. According the JDK docu of String(byte[], String) the JDK should 
> throw in this case an java.lang.UnsupportedCharacterEncoding exception, but 
> the IBM JDK 1.4.2 throws java.nio.charset.IllegalCharsetNameException. This 
> is not an issue with IBM JDK 1.5.0_3 anymore.

-- 
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: (LANG-320) LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed LANG-320.
--

Resolution: Won't Fix

> LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions
> 
>
> Key: LANG-320
> URL: https://issues.apache.org/jira/browse/LANG-320
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Joerg Schaible
> Fix For: Known Issue
>
>
> LocaleUtilsTest.testLanguagesByCountry makes the assumption, that within the 
> JDK there is only one language defined for GB: en. This is not true for the 
> IBM JDK 1.5.0 that also knows about cy_GB i.e. Welsh.

-- 
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: (LANG-325) DateUtilsTest error on IBM 1.5

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed LANG-325.
--

Resolution: Won't Fix

> DateUtilsTest error on IBM 1.5
> --
>
> Key: LANG-325
> URL: https://issues.apache.org/jira/browse/LANG-325
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: Nightly Builds
> Environment: Ubuntu Linux, IBM 1.5.0
>Reporter: Henri Yandell
> Fix For: Known Issue
>
>
> Testcase: testTruncateLang59(org.apache.commons.lang.time.DateUtilsTest):   
> FAILED
> Check 00:00:00.000 expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 
> GM...>
> junit.framework.ComparisonFailure: Check 00:00:00.000 
> expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 GM...>
> at 
> org.apache.commons.lang.time.DateUtilsTest.testTruncateLang59(DateUtilsTest.java:910)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

-- 
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] Updated: (LANG-320) LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated LANG-320:
---

Fix Version/s: (was: 3.0)
   Known Issue

> LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions
> 
>
> Key: LANG-320
> URL: https://issues.apache.org/jira/browse/LANG-320
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Joerg Schaible
> Fix For: Known Issue
>
>
> LocaleUtilsTest.testLanguagesByCountry makes the assumption, that within the 
> JDK there is only one language defined for GB: en. This is not true for the 
> IBM JDK 1.5.0 that also knows about cy_GB i.e. Welsh.

-- 
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] Updated: (LANG-325) DateUtilsTest error on IBM 1.5

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell updated LANG-325:
---

Fix Version/s: Known Issue

> DateUtilsTest error on IBM 1.5
> --
>
> Key: LANG-325
> URL: https://issues.apache.org/jira/browse/LANG-325
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: Nightly Builds
> Environment: Ubuntu Linux, IBM 1.5.0
>Reporter: Henri Yandell
> Fix For: Known Issue
>
>
> Testcase: testTruncateLang59(org.apache.commons.lang.time.DateUtilsTest):   
> FAILED
> Check 00:00:00.000 expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 
> GM...>
> junit.framework.ComparisonFailure: Check 00:00:00.000 
> expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 GM...>
> at 
> org.apache.commons.lang.time.DateUtilsTest.testTruncateLang59(DateUtilsTest.java:910)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

-- 
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] Reopened: (LANG-320) LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell reopened LANG-320:



> LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions
> 
>
> Key: LANG-320
> URL: https://issues.apache.org/jira/browse/LANG-320
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Joerg Schaible
> Fix For: 3.0
>
>
> LocaleUtilsTest.testLanguagesByCountry makes the assumption, that within the 
> JDK there is only one language defined for GB: en. This is not true for the 
> IBM JDK 1.5.0 that also knows about cy_GB i.e. Welsh.

-- 
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: (LANG-325) DateUtilsTest error on IBM 1.5

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed LANG-325.
--

Resolution: Won't Fix

JDK bug, so not a lot we can do about it. 

> DateUtilsTest error on IBM 1.5
> --
>
> Key: LANG-325
> URL: https://issues.apache.org/jira/browse/LANG-325
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: Nightly Builds
> Environment: Ubuntu Linux, IBM 1.5.0
>Reporter: Henri Yandell
>
> Testcase: testTruncateLang59(org.apache.commons.lang.time.DateUtilsTest):   
> FAILED
> Check 00:00:00.000 expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 
> GM...>
> junit.framework.ComparisonFailure: Check 00:00:00.000 
> expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 GM...>
> at 
> org.apache.commons.lang.time.DateUtilsTest.testTruncateLang59(DateUtilsTest.java:910)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

-- 
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] Reopened: (LANG-325) DateUtilsTest error on IBM 1.5

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell reopened LANG-325:



> DateUtilsTest error on IBM 1.5
> --
>
> Key: LANG-325
> URL: https://issues.apache.org/jira/browse/LANG-325
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: Nightly Builds
> Environment: Ubuntu Linux, IBM 1.5.0
>Reporter: Henri Yandell
>
> Testcase: testTruncateLang59(org.apache.commons.lang.time.DateUtilsTest):   
> FAILED
> Check 00:00:00.000 expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 
> GM...>
> junit.framework.ComparisonFailure: Check 00:00:00.000 
> expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 GM...>
> at 
> org.apache.commons.lang.time.DateUtilsTest.testTruncateLang59(DateUtilsTest.java:910)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

-- 
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] Commented: (LANG-325) DateUtilsTest error on IBM 1.5

2007-02-17 Thread Henri Yandell (JIRA)

[ 
https://issues.apache.org/jira/browse/LANG-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473896
 ] 

Henri Yandell commented on LANG-325:


Looks like timezones are broken on the IBM Linux 1.5.0 DateFormat class. Unable 
to test this on 1.4.2 on Linux as that errors out when trying to compile in 
either Ant or Maven.

> DateUtilsTest error on IBM 1.5
> --
>
> Key: LANG-325
> URL: https://issues.apache.org/jira/browse/LANG-325
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: Nightly Builds
> Environment: Ubuntu Linux, IBM 1.5.0
>Reporter: Henri Yandell
>
> Testcase: testTruncateLang59(org.apache.commons.lang.time.DateUtilsTest):   
> FAILED
> Check 00:00:00.000 expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 
> GM...>
> junit.framework.ComparisonFailure: Check 00:00:00.000 
> expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 GM...>
> at 
> org.apache.commons.lang.time.DateUtilsTest.testTruncateLang59(DateUtilsTest.java:910)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

-- 
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] Created: (LANG-325) DateUtilsTest error on IBM 1.5

2007-02-17 Thread Henri Yandell (JIRA)
DateUtilsTest error on IBM 1.5
--

 Key: LANG-325
 URL: https://issues.apache.org/jira/browse/LANG-325
 Project: Commons Lang
  Issue Type: Bug
Affects Versions: Nightly Builds
 Environment: Ubuntu Linux, IBM 1.5.0
Reporter: Henri Yandell


Testcase: testTruncateLang59(org.apache.commons.lang.time.DateUtilsTest):   
FAILED
Check 00:00:00.000 expected:<...0:00:00.000 MD...> but was:<...6:00:00.000 
GM...>
junit.framework.ComparisonFailure: Check 00:00:00.000 expected:<...0:00:00.000 
MD...> but was:<...6:00:00.000 GM...>
at 
org.apache.commons.lang.time.DateUtilsTest.testTruncateLang59(DateUtilsTest.java:910)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)


-- 
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: (LANG-320) LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions

2007-02-17 Thread Henri Yandell (JIRA)

 [ 
https://issues.apache.org/jira/browse/LANG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed LANG-320.
--

Resolution: Fixed

I've fixed this by changing both of the assertions to only assert that the 
results contain, rather than that the results equal. This should allow things 
to be less problematic when a JVM adds a language, and it seems a lot less 
likely that the JVM would remove a language.

Fixed in r508733.

> LocaleUtilsTest fails with IBM JDK 1.5.0 because of false assuptions
> 
>
> Key: LANG-320
> URL: https://issues.apache.org/jira/browse/LANG-320
> Project: Commons Lang
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Joerg Schaible
> Fix For: 3.0
>
>
> LocaleUtilsTest.testLanguagesByCountry makes the assumption, that within the 
> JDK there is only one language defined for GB: en. This is not true for the 
> IBM JDK 1.5.0 that also knows about cy_GB i.e. Welsh.

-- 
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]



svn commit: r508733 - /jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java

2007-02-17 Thread bayard
Author: bayard
Date: Sat Feb 17 00:41:20 2007
New Revision: 508733

URL: http://svn.apache.org/viewvc?view=rev&rev=508733
Log:
Fixing LANG-320. I modified the tests to only check that the listed languages 
and countries are contained in the result, not that they exactly equal the 
result

Modified:

jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java

Modified: 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java?view=diff&rev=508733&r1=508732&r2=508733
==
--- 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java
 (original)
+++ 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java
 Sat Feb 17 00:41:20 2007
@@ -391,7 +391,10 @@
 
 //---
 /**
- * Make sure the language by country is correct.
+ * Make sure the language by country is correct. It checks that 
+ * the LocaleUtils.languagesByCountry(country) call contains the 
+ * array of languages passed in. It may contain more due to JVM 
+ * variations.
  *
  * @param country
  * @param languages array of languages that should be returned
@@ -401,7 +404,6 @@
 List list2 = LocaleUtils.languagesByCountry(country);
 assertNotNull(list);
 assertSame(list, list2);
-assertEquals(languages.length, list.size());
 //search through langauges
 for (int i = 0; i < languages.length; i++) {
 Iterator iterator = list.iterator();
@@ -438,7 +440,11 @@
 
 //---
 /**
- * Make sure the country by language is correct.
+ * Make sure the country by language is correct. It checks that 
+ * the LocaleUtils.countryByLanguage(language) call contains the 
+ * array of countries passed in. It may contain more due to JVM 
+ * variations.
+ *
  *
  * @param language
  * @param countries array of countries that should be returned
@@ -448,7 +454,6 @@
 List list2 = LocaleUtils.countriesByLanguage(language);
 assertNotNull(list);
 assertSame(list, list2);
-assertEquals(countries.length, list.size());
 //search through langauges
 for (int i = 0; i < countries.length; i++) {
 Iterator iterator = list.iterator();



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r508731 - /jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java

2007-02-17 Thread bayard
Author: bayard
Date: Sat Feb 17 00:34:54 2007
New Revision: 508731

URL: http://svn.apache.org/viewvc?view=rev&rev=508731
Log:
Fixing javadoc

Modified:

jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java

Modified: 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java
URL: 
http://svn.apache.org/viewvc/jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java?view=diff&rev=508731&r1=508730&r2=508731
==
--- 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java
 (original)
+++ 
jakarta/commons/proper/lang/trunk/src/test/org/apache/commons/lang/LocaleUtilsTest.java
 Sat Feb 17 00:34:54 2007
@@ -438,7 +438,7 @@
 
 //---
 /**
- * Make sure the language by country is correct.
+ * Make sure the country by language is correct.
  *
  * @param language
  * @param countries array of countries that should be returned
@@ -474,7 +474,7 @@
 }
 
 /**
- * Test languagesByCountry() method.
+ * Test countriesByLanguage() method.
  */
 public void testCountriesByLanguage() {
 assertCountriesByLanguage(null, new String[0]);



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]