[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 13 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. -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: 18 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-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02082006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-02082006.jar - [junit] at org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:63) [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:58) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) [junit] at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) [junit] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:112) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) [junit] at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:160) [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 org.dom4j.rule.Mode.fireRule(Mode.java:59) [junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102) [junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91) [junit] at
[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jsl-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 13 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. -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: 18 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-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-02082006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-02082006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-02082006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/public/workspace/jaxen/target/jaxen-02082006.jar - [junit] at org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:63) [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:58) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) [junit] at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65) [junit] at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:112) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) [junit] at org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:160) [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 org.dom4j.rule.Mode.fireRule(Mode.java:59) [junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102) [junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91) [junit] at
[jira] Commented: (TRANSACTION-11) Improve relationship between ResourceManager and FileResourceManager
[ http://issues.apache.org/jira/browse/TRANSACTION-11?page=comments#action_12425218 ] Jörg Heinicke commented on TRANSACTION-11: -- I don't like the idea of adding getters and setters to interfaces, but as the corresponding getter getDefaultTransactionTimeout() does already exist, I'm ok with adding the setter as well. Adding reset() makes sense for me. BTW, in association with your changes what do you think of my suggested changes at http://marc.theaimsgroup.com/?t=11528064431r=1w=4 (please respond on the mailing list as it is quite off-topic here)? I don't know Slide's usage FileResourceManager yet. Improve relationship between ResourceManager and FileResourceManager Key: TRANSACTION-11 URL: http://issues.apache.org/jira/browse/TRANSACTION-11 Project: Commons Transaction Issue Type: Improvement Affects Versions: 1.1, 1.2 Reporter: Jeremy Fujimoto-Johnson Assigned To: Oliver Zeigermann Attachments: commons-transaction-rm-patch.txt Add the reset method to ResourceManager so that classes using a ResourceManager won't have to cast it to FileResourceManager to call this method. Add new constructors to FileResourceManager so that it can be constructed with the default timeout period for transactions already specified so that you don't have to cast to FileResourceManager to set it later. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TRANSACTION-11) Improve relationship between ResourceManager and FileResourceManager
[ http://issues.apache.org/jira/browse/TRANSACTION-11?page=comments#action_12425272 ] Jeremy Fujimoto-Johnson commented on TRANSACTION-11: Actually, in the attached patch there isn't a setDefaultTransactionTimeout() method added to the ResourceManager interface. But that solution would meet my needs as well. I can see that that there would be an advantage in not making as big of a change as adding new constructors to FileResourceManager. Improve relationship between ResourceManager and FileResourceManager Key: TRANSACTION-11 URL: http://issues.apache.org/jira/browse/TRANSACTION-11 Project: Commons Transaction Issue Type: Improvement Affects Versions: 1.1, 1.2 Reporter: Jeremy Fujimoto-Johnson Assigned To: Oliver Zeigermann Attachments: commons-transaction-rm-patch.txt Add the reset method to ResourceManager so that classes using a ResourceManager won't have to cast it to FileResourceManager to call this method. Add new constructors to FileResourceManager so that it can be constructed with the default timeout period for transactions already specified so that you don't have to cast to FileResourceManager to set it later. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (IO-90) Infinite loop in FileSystemUtils.freeSpaceWindows if share directory empty
Infinite loop in FileSystemUtils.freeSpaceWindows if share directory empty
--
Key: IO-90
URL: http://issues.apache.org/jira/browse/IO-90
Project: Commons IO
Issue Type: Bug
Components: Utilities
Affects Versions: 1.2
Environment: Windows NT or higher
Reporter: Thomas Ledoux
When using FileSystemUtils.freeSpaceWindows in an empty share directory, the
line containing the free space does not exist which causes an infinite loop
(the outerloop doesn't decrease the i index).
In fact to deal with all possible errors, I propose to test the exitCode of the
dir command.
Here is a proposed new code for this function :
/**
* Find free space on the Windows platform using the 'dir' command.
*
* @param path the path to get free space for, including the colon
* @return the amount of free drive space on the drive
* @throws IOException if an error occurs
*/
long freeSpaceWindows(String path) throws IOException {
path = FilenameUtils.normalize(path);
if (path.length() 2 path.charAt(1) == ':') {
path = path.substring(0, 2); // seems to make it work
}
// build and run the 'dir' command
String[] cmdAttrbs = new String[] {cmd.exe, /C, dir /-c + path};
// read in the output of the command to an ArrayList
BufferedReader in = null;
String line = null;
ArrayList lines = new ArrayList();
int errorLevel = 0;
try {
Process proc = Runtime.getRuntime().exec(cmdAttrbs);
in = new BufferedReader(
new InputStreamReader(proc.getInputStream()));
line = in.readLine();
while (line != null) {
line = line.toLowerCase().trim();
lines.add(line);
line = in.readLine();
}
proc.waitFor();
errorLevel = proc.exitValue();
} finally {
IOUtils.closeQuietly(in);
}
if (lines.size() == 0) {
// unknown problem, throw exception
throw new IOException(
Command line 'dir /-c' did not return any info +
for command ' + cmdAttrbs[2] + ');
}
if (errorLevel != 0) {
if (errorLevel == 2) {
// Empty directory : unable to calculate the freeSpace
return Integer.MAX_VALUE; // ???
} else {
// unknown problem, throw exception
throw new IOException(
Command line 'dir /-c' error [ + errorLevel +
] for command ' + cmdAttrbs[2] + ');
}
}
// now iterate over the lines we just read and find the LAST
// non-empty line (the free space bytes should be in the last element
// of the ArrayList anyway, but this will ensure it works even if it's
// not, still assuming it is on the last non-blank line)
long bytes = -1;
int i = lines.size() - 1;
int bytesStart = 0;
int bytesEnd = 0;
outerLoop: while (i 0) {
line = (String) lines.get(i);
if (line.length() 0) {
// found it, so now read from the end of the line to find the
// last numeric character on the line, then continue until we
// find the first non-numeric character, and everything between
// that and the last numeric character inclusive is our free
// space bytes count
int j = line.length() - 1;
innerLoop1: while (j = 0) {
char c = line.charAt(j);
if (Character.isDigit(c)) {
// found the last numeric character, this is the end of
// the free space bytes count
bytesEnd = j + 1;
break innerLoop1;
}
j--;
}
innerLoop2: while (j = 0) {
char c = line.charAt(j);
if (!Character.isDigit(c) c != ',' c != '.') {
// found the next non-numeric character, this is the
// beginning of the free space bytes count
bytesStart = j + 1;
break innerLoop2;
}
j--;
}
break outerLoop;
} else {
// If the last line is empty we are unable to parse the
freeSpace
throw new IOException(
Command line 'dir /-c' did not return valid info +
for command ' + cmdAttrbs[2] + ');
}
}
//
[jira] Created: (COLLECTIONS-219) The CollectionUtils.removeAll method calls the ListUtils.retainAll method instead of the ListUtils.removeAll method.
The CollectionUtils.removeAll method calls the ListUtils.retainAll method instead of the ListUtils.removeAll method. Key: COLLECTIONS-219 URL: http://issues.apache.org/jira/browse/COLLECTIONS-219 Project: Commons Collections Issue Type: Bug Affects Versions: 3.2 Reporter: Tom Leccese The CollectionUtils.removeAll method calls the ListUtils.retainAll method instead of the ListUtils.removeAll method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [lang] VariableFormatter - pre 2.2
Make a new one - unless you're arguing for the change to be in 2.2;
then keep it going on this thread.
Hen
On 8/2/06, Tom Schindl [EMAIL PROTECTED] wrote:
Where should I put my feature request should I:
- append it to VariableFormatter's-Jira-Entry
- create a new Jira-Entry for StrSubstitutor
Tom
Tom Schindl schrieb:
Hi,
Looks good to me. Maybe for 2.3 this patch could provide
MessageFormatting like proposed before without bloating the API. Does
this now mean that VariableFormatter is gone? I like the nameing
StrSubstitutor better.
Tom
Henri Yandell schrieb:
On 7/23/06, Stephen Colebourne [EMAIL PROTECTED] wrote:
I have reworked the VariableFormatter class along the lines that I
was thinking. I have committed it as StrSubstitutor so it doesn't
clash for the moment and so it can be easiy reviewed.
This version does not have a separate parser class, but still
supports escaping, and matchers for prefix/suffix (which can now be
set by users). The new class should perform better as a result.
I have removed the edge cases wrt resolving Objects, as they were
rather ill-defined.
Otherwise, the basic functionality it supported, and the test case
is slightly enlarged. I still want to break out the resolver as a
public abstract class before release.
Opinions
Oliver, Gary, Tom?
Looking to get Lang 2.2 moving out the door and this is the only blocker.
Hen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Index:
/home.local/tom/projects/eclipse-ws/bidi-forms/jakarta-commons-lang/src/java/org/apache/commons/lang/text/StrSubstitutor.java
===
---
/home.local/tom/projects/eclipse-ws/bidi-forms/jakarta-commons-lang/src/java/org/apache/commons/lang/text/StrSubstitutor.java
(revision 427468)
+++
/home.local/tom/projects/eclipse-ws/bidi-forms/jakarta-commons-lang/src/java/org/apache/commons/lang/text/StrSubstitutor.java
(working copy)
@@ -16,6 +16,7 @@
package org.apache.commons.lang.text;
+import java.text.MessageFormat;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
@@ -725,5 +726,84 @@
return obj.toString();
}
}
+
+/**
+ * Looks up a string value by name using a [EMAIL PROTECTED] Map} and
can use format
+ * expressions known from [EMAIL PROTECTED] MessageFormat}
+ */
+static class MapVariableResolverFormat extends MapVariableResolver {
+
+ MapVariableResolverFormat(Map map) {
+ super(map);
+ }
+
+ public String resolveVariable(String varName) {
+ int index;
+
+ if (map != null (index = varName.indexOf(,)) !=
-1) {
+ return MessageFormat.format({0 +
varName.substring(index)
+ + }, new Object[] { map.get(
+ varName.substring(0,
index)) });
+ } else {
+ return super.resolveVariable(varName);
+ }
+ }
+}
+
+/**
+ * Substitutes variables by value and allows to use the formats known
from
+ * [EMAIL PROTECTED] MessageFormat}:
+ * p
+ * The following example demonstrates this:
+ * /p
+ * pre
+ * Map map = new HashMap();
+ * map.put(num,new Double(1000.103));
+ * map.put(date, new
SimpleDateFormat(-MM-dd).parse(1970-01-01));
+ *
+ * StrSubstitutor.Format.replace(Number: ${num,number,integer}, Date:
${date,date,-MM-dd}, map)
+ * /pre
+ * yielding in Locale.US
+ * pre
+ * Number: 1,000, Date: 1970-01-01
+ * /pre
+ */
+public static class Format {
+ private Format() {}
+
+/**
+ * Replaces all the occurrences of variables in the given source
object with
+ * their matching values from the map.
+ *
+ * @param source the source text containing the variables to
substitute
+ * @param valueMap the map with the values
+ * @return the result of the replace operation
+ */
+public static String replace(Object source, Map valueMap) {
+ StrSubstitutor tmp = new StrSubstitutor();
+ tmp.setVariableResolver(new
MapVariableResolverFormat(valueMap));
+
+return tmp.replace(source);
+}
+/**
+ * Replaces all the occurrences of variables in the given source
object with
+ * their matching values from the map. This method allows to
specifiy a
+ * custom variable prefix and suffix
+ *
+ * @param source the source text containing the variables to
substitute
+
Re: [logging] Tapestry and JCL
Hello, Simon Kitching wrote: If I were writing a 1.4+ library or app, I'd just use java.util.logging directly. Which reminds me: is the JULI implementation of the java.util.logging API (used in tomcat) available as an independent library? If not, maybe it is worth extracting it as a project of the logging.apache.org group? this is exactly what x4juli ( http://www.x4juli.org ) does: Combine the advantages of Tomcat JULI (Support of per Classloader Logging / configuration and avoiding memory leaks), port the configuration, appenders and goodies of log4j, and implementing a native version of JCL and SLF4J (Different to a static/dynamic bound wrapper, the X4JULI Logger does implement the interfaces). http://svn.berlios.de/wsvn/x4juli/trunk/src/java/org/x4juli/logger/X4JuliLogger.java?op=filerev=0sc=0 Currently I am spending 12-16 hours per day at my company and have no time to develop and release a new version, but may be in September/October. The current SVN trunk does not work, I had to stop my development for mentioned reasons. The version 0.6 does work, even when there is a problem in the samples with the binaries. Regards Boris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MATH-154) MathUtils addAndCheck and subAndCheck for long values
[
http://issues.apache.org/jira/browse/MATH-154?page=comments#action_12425314 ]
Remi Arntzen commented on MATH-154:
---
a better implementation:
long addAndCheck(long a, long b) {
long max = Math.max(a, b);
long min = Math.min(a, b);
long sum = a + b;
String overflow = Overflow: add;
if (max == 0 || min == 0) (
return sum;
} else if (max 0 min 0) {
if (Long.MAX_VALUE - max min) {
throw new RuntimeException(overflow);
}
} else if (max 0 min 0) {
if (Long.MIN_VALUE - min max) {
throw new RuntimeException(overflow);
}
} else {
return sum;
}
}
long subAndCheck(long a, long b) {
long max = Math.max(a, b);
long min = Math.min(a, b);
long diff = a - b;
String overflow = Overflow: add;
if (max == 0 || min == 0) {
return diff;
} else if (max 0 min 0) {
if (max == a) {
if (max - Long.MAX_VALUE min) {
throw new RuntimeException(overflow);
}
} else if (max == b) {
if (min - Long.MIN_VALUE max) {
throw new RuntimeException(overflow);
}
}
} else {
return sum;
}
}
MathUtils addAndCheck and subAndCheck for long values
-
Key: MATH-154
URL: http://issues.apache.org/jira/browse/MATH-154
Project: Commons Math
Issue Type: Improvement
Affects Versions: Nightly Builds, 1.1 Final
Reporter: Remi Arntzen
public static long addAndCheck(long x, long y) {
BigInteger s = BigInteger.valueOf(x).add(BigInteger.valueOf(y);
if (s.bitLength() + 1 Long.SIZE) {
throw new ArithmeticException(overflow: add);
}
return s.longValue();
}
public static long subAndCheck(long x, long y) {
BigInteger s = BigInteger.valueOf(x).subtract(BigInteger.valueOf(y));
if (s.bitLength() + 1 Long.SIZE) {
throw new ArithmeticException(overflow: add);
}
return s.longValue();
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [lang] VariableFormatter - pre 2.2
Well I'd love to see this method in 2.2 because I think it does make any
API visible to the user and doesn't bloat the
interface with too many new methods.
Any other thoughts?
Tom
Henri Yandell wrote:
Make a new one - unless you're arguing for the change to be in 2.2;
then keep it going on this thread.
Hen
On 8/2/06, Tom Schindl [EMAIL PROTECTED] wrote:
Where should I put my feature request should I:
- append it to VariableFormatter's-Jira-Entry
- create a new Jira-Entry for StrSubstitutor
Tom
Tom Schindl schrieb:
Hi,
Looks good to me. Maybe for 2.3 this patch could provide
MessageFormatting like proposed before without bloating the API. Does
this now mean that VariableFormatter is gone? I like the nameing
StrSubstitutor better.
Tom
Henri Yandell schrieb:
On 7/23/06, Stephen Colebourne [EMAIL PROTECTED] wrote:
I have reworked the VariableFormatter class along the lines that I
was thinking. I have committed it as StrSubstitutor so it doesn't
clash for the moment and so it can be easiy reviewed.
This version does not have a separate parser class, but still
supports escaping, and matchers for prefix/suffix (which can now be
set by users). The new class should perform better as a result.
I have removed the edge cases wrt resolving Objects, as they were
rather ill-defined.
Otherwise, the basic functionality it supported, and the test case
is slightly enlarged. I still want to break out the resolver as a
public abstract class before release.
Opinions
Oliver, Gary, Tom?
Looking to get Lang 2.2 moving out the door and this is the only
blocker.
Hen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Index:
/home.local/tom/projects/eclipse-ws/bidi-forms/jakarta-commons-lang/src/java/org/apache/commons/lang/text/StrSubstitutor.java
===
---
/home.local/tom/projects/eclipse-ws/bidi-forms/jakarta-commons-lang/src/java/org/apache/commons/lang/text/StrSubstitutor.java
(revision 427468)
+++
/home.local/tom/projects/eclipse-ws/bidi-forms/jakarta-commons-lang/src/java/org/apache/commons/lang/text/StrSubstitutor.java
(working copy)
@@ -16,6 +16,7 @@
package org.apache.commons.lang.text;
+import java.text.MessageFormat;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
@@ -725,5 +726,84 @@
return obj.toString();
}
}
+
+/**
+ * Looks up a string value by name using a [EMAIL PROTECTED] Map} and
can
use format
+ * expressions known from [EMAIL PROTECTED] MessageFormat}
+ */
+static class MapVariableResolverFormat extends
MapVariableResolver {
+
+ MapVariableResolverFormat(Map map) {
+ super(map);
+ }
+
+ public String resolveVariable(String varName) {
+ int index;
+
+ if (map != null (index =
varName.indexOf(,)) != -1) {
+ return MessageFormat.format({0 +
varName.substring(index)
+ + }, new Object[] { map.get(
+
varName.substring(0, index)) });
+ } else {
+ return super.resolveVariable(varName);
+ }
+ }
+}
+
+/**
+ * Substitutes variables by value and allows to use the
formats known from
+ * [EMAIL PROTECTED] MessageFormat}:
+ * p
+ * The following example demonstrates this:
+ * /p
+ * pre
+ * Map map = new HashMap();
+ * map.put(num,new Double(1000.103));
+ * map.put(date, new
SimpleDateFormat(-MM-dd).parse(1970-01-01));
+ *
+ * StrSubstitutor.Format.replace(Number:
${num,number,integer}, Date: ${date,date,-MM-dd}, map)
+ * /pre
+ * yielding in Locale.US
+ * pre
+ * Number: 1,000, Date: 1970-01-01
+ * /pre
+ */
+public static class Format {
+ private Format() {}
+
+/**
+ * Replaces all the occurrences of variables in the given
source object with
+ * their matching values from the map.
+ *
+ * @param source the source text containing the variables
to substitute
+ * @param valueMap the map with the values
+ * @return the result of the replace operation
+ */
+public static String replace(Object source, Map valueMap) {
+ StrSubstitutor tmp = new StrSubstitutor();
+ tmp.setVariableResolver(new
MapVariableResolverFormat(valueMap));
+
+return tmp.replace(source);
+
RE: [lang] VariableFormatter - pre 2.2
Hello All: I think the argument for the name change I am hearing is: we are not formatting a la printf but we are replacing markers with values (and not formatting those values). Is that right? If that is the case, a Substitutor name is better. As a general rule, I do not like or use abbreviations in class or method names (acronyms are OK by me). So I would say that StringSubstitutor is better. After all, we have StringUtils, StringEscapeUtils and many others, not StrUtils, StrEscapeUtils. So I would ask that we use StringFoo for all of these classes. Gary -Original Message- From: Henri Yandell [mailto:[EMAIL PROTECTED] Sent: Monday, July 31, 2006 11:30 PM To: Jakarta Commons Developers List; Stephen Colebourne Subject: Re: [lang] VariableFormatter - pre 2.2 On 7/23/06, Stephen Colebourne [EMAIL PROTECTED] wrote: I have reworked the VariableFormatter class along the lines that I was thinking. I have committed it as StrSubstitutor so it doesn't clash for the moment and so it can be easiy reviewed. This version does not have a separate parser class, but still supports escaping, and matchers for prefix/suffix (which can now be set by users). The new class should perform better as a result. I have removed the edge cases wrt resolving Objects, as they were rather ill- defined. Otherwise, the basic functionality it supported, and the test case is slightly enlarged. I still want to break out the resolver as a public abstract class before release. Opinions Oliver, Gary, Tom? Looking to get Lang 2.2 moving out the door and this is the only blocker. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [lang] VariableFormatter - pre 2.2
Stephen Colebourne wrote:
For example There were ${number} characters, would return the
object matching the ${number} substitution, and dropping the rest of
the text!
Perhaps you can point to an exact use case?
Oliver Heger wrote:
Your analysis is correct. The idea was that you can have specialized
resolver implementations that inherently work on objects, e.g.
- a constant resolver, which interprets the variable name as a name of
a static field of a class, e.g.
${my.package.MyClass.MY_CONSTANT} would return the value of the
constant field.
- an expression resolver, which could be passed an expression in a
language like JEXL and would calculate the result.
Of course if the string passed to the substitutor contains other text
elements or variables, you have no choice than converting the result
to text. But if only a single variable is to be processed, the result
can be an arbitrary type.
Sounds a bit [configuration] specific to me.
However, we could add a singleVariableName(String) method which would
check for the special case where the whole string was a variable.
We could also have a variableNames(String) method which returns the top
level variable names in the string.
Not sure how useful either of these would really be though.
What might be more useful, would be to change the method signature of
resolveVariable() to take the StrBuilder start pos and current variable
start and end. That would effectively provide subclasses with much more
detailed events about the variables.
So, pre 2.2 - I'd suggest
a) alter resolveVariable()
b) extract VariableFormatter interface to be StrLookup abstract class
c) agree class name (is anyone not OK with StrSubstitutor?)
Stephen
a) and b) is fine with me. The discussion about the class name I will
leave to you native speakers ;-)
Oliver
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [build] nightly build support for maven2?
On 8/1/06, Simon Kitching [EMAIL PROTECTED] wrote: Hi, Currently the nightly build stuff supports either ant or maven1.x. I've just got logging building/testing successfully with maven2 (though building the dist bundles is still to do). Is there any chance someone could update the nightly build stuff to support maven2 as well? It would be a lot quicker/safer for someone already familiar with these scripts to add this than me.. Would be easy to do. Here are the steps, for anyone who wants to play with this before I get to it, which won't be until at least this weekend. I saw m2 set up already on vmbuild, so the following should be all we need to do. 1. Create and commit text files named (for consistency) nightly_proper_maven2_list.txt, nightly_sandbox_maven2_list.txt containing lists of component names to be built using maven2. Like the other files, one name per line, only the (svn) component name, e.g., beanutils. Component names should appear on at most one of the lists _proper_maven, _proper_maven2, _proper_ant, etc. 2. Add necessary config to designate the maven2 deployment location. 3. Add a process_maven2_components() function like the one for m1. Should be simpler, since m2 can do more deployment automatically. Pipe the logs out to log_location like the m1 function does. 4. Add blocks like this after the maven1 build part at the end: # Sandbox Maven2 components list_file=$nightly_list_location/nightly_sandbox_maven2_list.txt components=`$list_file` current_root=$sandbox_root echo echo == echo Building Sandbox Maven 2 Components echo == process_maven2_components 5. Test locally by changing config parameters. Make sure to check permissions on deployed files. 6. Check changes to the script in to svn. The crontab wrapper that executes the nightlies will pick up the change in the script and start executing the new version on the next run. Extra credit: satisfy the burgeoning collective appetite for CI-spam by accumulating a list of the builds that have failed (across build types) and generate *one* email to commons-dev with the failed component names in the subject line and links to the relevant build logs in the body. *Extra credit (* means double bonus points): Replace the whole mess using Continuum, contributing patches as necessary to get it all to work. Currently, logging is listed in the maven1.x list, but that only builds the site for logging, not the code so logging needs to move to either the ant list or a maven2 list... BTW, maven2 is a mile better than maven1. I'm planning on creating a maven2 buildfile for Digester soon, and maybe a few others. +1 - I think it is time to start moving things. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r428130 - in /jakarta/commons/proper/collections/trunk: ./ src/java/org/apache/commons/collections/ src/test/org/apache/commons/collections/
Author: scolebourne
Date: Wed Aug 2 13:24:02 2006
New Revision: 428130
URL: http://svn.apache.org/viewvc?rev=428130view=rev
Log:
COLLECTIONS-219 - CollectionUtils - Fix removeAll() method which was completely
broken
Modified:
jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/CollectionUtils.java
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/TestCollectionUtils.java
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/TestListUtils.java
Modified: jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html?rev=428130r1=428129r2=428130view=diff
==
--- jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html (original)
+++ jakarta/commons/proper/collections/trunk/RELEASE-NOTES.html Wed Aug 2
13:24:02 2006
@@ -56,6 +56,7 @@
ul
liFlat3Map - Fix setValue in MapIterator and EntrySetIterator to work
correctly [COLLECTIONS-217]/li
liExtendedProperties - Include property name had confused static/instance
semantics [COLLECTIONS-214]/li
+liCollectionUtils - Fix removeAll() method which was completely broken
[COLLECTIONS-219]/li
/ul
centerh3JAVADOC/h3/center
Modified:
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/CollectionUtils.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/CollectionUtils.java?rev=428130r1=428129r2=428130view=diff
==
---
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/CollectionUtils.java
(original)
+++
jakarta/commons/proper/collections/trunk/src/java/org/apache/commons/collections/CollectionUtils.java
Wed Aug 2 13:24:02 2006
@@ -1,5 +1,5 @@
/*
- * Copyright 2001-2005 The Apache Software Foundation
+ * Copyright 2001-2006 The Apache Software Foundation
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
@@ -1115,10 +1115,10 @@
* @return a codeCollection/code containing all the elements of
codecollection/code except
* any elements that also occur in coderemove/code.
* @throws NullPointerException if either parameter is null
- * @since Commons Collections 3.2
+ * @since Commons Collections 3.3 (method existed in 3.2 but was
completely broken)
*/
public static Collection removeAll(Collection collection, Collection
remove) {
-return ListUtils.retainAll(collection, remove);
+return ListUtils.removeAll(collection, remove);
}
//---
Modified:
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/TestCollectionUtils.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/TestCollectionUtils.java?rev=428130r1=428129r2=428130view=diff
==
---
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/TestCollectionUtils.java
(original)
+++
jakarta/commons/proper/collections/trunk/src/test/org/apache/commons/collections/TestCollectionUtils.java
Wed Aug 2 13:24:02 2006
@@ -1,5 +1,5 @@
/*
- * Copyright 2001-2005 The Apache Software Foundation
+ * Copyright 2001-2006 The Apache Software Foundation
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
@@ -1237,8 +1237,70 @@
assertEquals(eltb,eltc);
assertEquals(eltc,eltb);
}
-
- public void testTransformedCollection() {
+
+//---
+public void testRetainAll() {
+List base = new ArrayList();
+base.add(A);
+base.add(B);
+base.add(C);
+List sub = new ArrayList();
+sub.add(A);
+sub.add(C);
+sub.add(X);
+
+Collection result = CollectionUtils.retainAll(base, sub);
+assertEquals(2, result.size());
+assertEquals(true, result.contains(A));
+assertEquals(false, result.contains(B));
+assertEquals(true, result.contains(C));
+assertEquals(3, base.size());
+assertEquals(true, base.contains(A));
+assertEquals(true, base.contains(B));
+assertEquals(true, base.contains(C));
+assertEquals(3, sub.size());
+assertEquals(true, sub.contains(A));
+assertEquals(true, sub.contains(C));
+assertEquals(true, sub.contains(X));
+
[jira] Updated: (COLLECTIONS-219) The CollectionUtils.removeAll method calls the ListUtils.retainAll method instead of the ListUtils.removeAll method.
[ http://issues.apache.org/jira/browse/COLLECTIONS-219?page=all ] Stephen Colebourne updated COLLECTIONS-219: --- Component/s: Core Fix Version/s: 3.3 Assignee: Stephen Colebourne The CollectionUtils.removeAll method calls the ListUtils.retainAll method instead of the ListUtils.removeAll method. Key: COLLECTIONS-219 URL: http://issues.apache.org/jira/browse/COLLECTIONS-219 Project: Commons Collections Issue Type: Bug Components: Core Affects Versions: 3.2 Reporter: Tom Leccese Assigned To: Stephen Colebourne Fix For: 3.3 The CollectionUtils.removeAll method calls the ListUtils.retainAll method instead of the ListUtils.removeAll method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [lang] VariableFormatter - pre 2.2
On 8/2/06, Gary Gregory [EMAIL PROTECTED] wrote: Hello All: I think the argument for the name change I am hearing is: we are not formatting a la printf but we are replacing markers with values (and not formatting those values). Is that right? If that is the case, a Substitutor name is better. As a general rule, I do not like or use abbreviations in class or method names (acronyms are OK by me). So I would say that StringSubstitutor is better. After all, we have StringUtils, StringEscapeUtils and many others, not StrUtils, StrEscapeUtils. So I would ask that we use StringFoo for all of these classes. I think in some places it was to avoid clash with JDK 1.5. StringBuilder I presume being the one. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r428147 - /jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/io/AbstractBeanWriter.java
Author: rdonkin
Date: Wed Aug 2 14:02:21 2006
New Revision: 428147
URL: http://svn.apache.org/viewvc?rev=428147view=rev
Log:
Improved error reporting in the case of a cycle reference. Based on JIRA
BETWIXT-54 contributed by Holger Haag. This reduces the level at which the
error is reported to info but compensates by adding more useful information to
the exception.
Modified:
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/io/AbstractBeanWriter.java
Modified:
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/io/AbstractBeanWriter.java
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/io/AbstractBeanWriter.java?rev=428147r1=428146r2=428147view=diff
==
---
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/io/AbstractBeanWriter.java
(original)
+++
jakarta/commons/proper/betwixt/trunk/src/java/org/apache/commons/betwixt/io/AbstractBeanWriter.java
Wed Aug 2 14:02:21 2006
@@ -1019,15 +1019,23 @@
// use absolute equality rather than equals
// we're only really bothered if objects are actually the same
if ( bean == next ) {
-if ( log.isDebugEnabled() ) {
-log.debug(Element stack: );
-Iterator debugStack = beanStack.iterator();
-while ( debugStack.hasNext() ) {
-log.debug(debugStack.next());
-}
+final String message = Cyclic reference at bean: + bean;
+log.error(message);
+StringBuffer buffer = new StringBuffer(message);
+buffer.append( Stack: );
+Iterator errorStack = beanStack.iterator();
+while ( errorStack.hasNext() ) {
+ Object errorObj = errorStack.next();
+ if(errorObj != null) {
+ buffer.append(errorObj.getClass().getName());
+ buffer.append(: );
+ }
+ buffer.append(errorObj);
+ buffer.append(;);
}
-log.error(Cyclic reference at bean: + bean);
-throw new CyclicReferenceException();
+final String debugMessage = buffer.toString();
+log.info( debugMessage );
+throw new CyclicReferenceException( debugMessage );
}
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (BETWIXT-54) CyclicReferenceException Logging
[ http://issues.apache.org/jira/browse/BETWIXT-54?page=all ] Robert Burrell Donkin closed BETWIXT-54. Resolution: Fixed hi holgar thanks for the patch i've committed a variation upon the patch. i'm a little concerned that logging to error is a little high. so, i've logged to info but included the information in the exception which should be printed out when caught. please give this a try. if this isn't good enough then i'll consider turning up the log level again. robert CyclicReferenceException Logging Key: BETWIXT-54 URL: http://issues.apache.org/jira/browse/BETWIXT-54 Project: Commons Betwixt Issue Type: Improvement Environment: / Reporter: Holger Haag Priority: Trivial Attachments: betwixt-cyclic-reference-logging.patch I got screwed last night because of a CyclicReferenceException without additional info (debug level not switched on). So I've increased the priority of some log entries from debug to error and added some more information (class names of all objects in the stack). I think this will make debugging CyclicReferenceException much easier. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r428162 - /jakarta/commons/proper/fileupload/trunk/pom.xml
Author: jochen
Date: Wed Aug 2 14:49:12 2006
New Revision: 428162
URL: http://svn.apache.org/viewvc?rev=428162view=rev
Log:
Adding initial pom for Maven 2 builds.
Added:
jakarta/commons/proper/fileupload/trunk/pom.xml
Added: jakarta/commons/proper/fileupload/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/jakarta/commons/proper/fileupload/trunk/pom.xml?rev=428162view=auto
==
--- jakarta/commons/proper/fileupload/trunk/pom.xml (added)
+++ jakarta/commons/proper/fileupload/trunk/pom.xml Wed Aug 2 14:49:12 2006
@@ -0,0 +1,165 @@
+?xml version=1.0 encoding=UTF-8?
+project
+xmlns=http://maven.apache.org/POM/4.0.0;
+xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
+xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
+ modelVersion4.0.0/modelVersion
+ groupIdorg.apache.commons/groupId
+ artifactIdcommons-fileupload/artifactId
+ version1.2-SNAPSHOT/version
+ nameFileUpload/name
+ !-- The description must currently be a single line. See MJAR-4. --
+ descriptionThe FileUpload component provides a simple yet flexible means
of adding support for multipart file upload functionality to servlets and web
applications. /description
+ urlhttp://jakarta.apache.org/commons/fileupload//url
+ issueManagement
+systemjira/system
+urlhttp://issues.apache.org/jira/BrowseProject.jspa?pid=10465/url
+ /issueManagement
+ inceptionYear2002/inceptionYear
+
+ mailingLists
+mailingList
+ nameCommons Dev List/name
+ subscribe[EMAIL PROTECTED]/subscribe
+ unsubscribe[EMAIL PROTECTED]/unsubscribe
+ postcommons-dev@jakarta.apache.org/post
+
archivehttp://mail-archives.apache.org/mod_mbox/jakarta-commons-dev//archive
+ otherArchives
+
otherArchivehttp://marc.theaimsgroup.com/?l=jakarta-commons-dev/otherArchive
+ /otherArchives
+/mailingList
+mailingList
+ nameCommons User List/name
+ subscribe[EMAIL PROTECTED]/subscribe
+ unsubscribe[EMAIL PROTECTED]/unsubscribe
+ postcommons-user@jakarta.apache.org/post
+
archivehttp://mail-archives.apache.org/mod_mbox/jakarta-commons-user//archive
+ otherArchives
+
otherArchivehttp://marc.theaimsgroup.com/?l=jakarta-commons-user/otherArchive
+ /otherArchives
+/mailingList
+ /mailingLists
+
+ developers
+developer
+ nameMartin Cooper/name
+ idmartinc/id
+ email[EMAIL PROTECTED]/email
+ organizationInformatica/organization
+/developer
+developer
+ namedIon Gillard/name
+ iddion/id
+ email[EMAIL PROTECTED]/email
+ organizationMultitask Consulting/organization
+/developer
+developer
+ nameJohn McNally/name
+ idjmcnally/id
+ email[EMAIL PROTECTED]/email
+ organizationCollabNet/organization
+/developer
+developer
+ nameDaniel Rall/name
+ iddlr/id
+ emaildlr@finemaltcoding.com/email
+ organizationCollabNet/organization
+/developer
+developer
+ nameJason van Zyl/name
+ idjvanzyl/id
+ email[EMAIL PROTECTED]/email
+ organizationZenplex/organization
+/developer
+developer
+ nameRobert Burrell Donkin/name
+ idrdonkin/id
+ email[EMAIL PROTECTED]/email
+ organization/
+/developer
+developer
+ nameSean C. Sullivan/name
+ idsullis/id
+ emailsean |at| seansullivan |dot| com/email
+ organization/
+/developer
+developer
+ nameJochen Wiedmann/name
+ idjochen/id
+ email[EMAIL PROTECTED]/email
+ organization/
+/developer
+ /developers
+
+ licenses
+license
+ nameThe Apache Software License, Version 2.0/name
+ urlhttp://www.apache.org/licenses/LICENSE-2.0.txt/url
+ distributionrepo/distribution
+/license
+ /licenses
+
+ scm
+
connectionscm:svn:scm:svn:https://svn.apache.org/repos/asf/jakarta/commons/proper/fileupload/trunk/connection
+
developerConnectionscm:svn:scm:svn:https://svn.apache.org/repos/asf/jakarta/commons/proper/fileupload/trunk/developerConnection
+
urlscm:svn:https://svn.apache.org/repos/asf/webservices/xmlrpc/tags/XMLRPC_3_0rc1/url
+ /scm
+
+ organization
+nameApache Software Foundation/name
+urlhttp://www.apache.org//url
+ /organization
+
+ build
+sourceDirectorysrc/java/sourceDirectory
+testSourceDirectorysrc/test/testSourceDirectory
+plugins
+ plugin
+artifactIdmaven-compiler-plugin/artifactId
+configuration
+ source1.3/source
+ target1.3/target
+/configuration
+ /plugin
+ plugin
+artifactIdmaven-jar-plugin/artifactId
+configuration
+ archive
+manifestFilesrc/conf/MANIFEST.MF/manifestFile
+manifestEntries
+ Specification-Version${project.version}/Specification-Version
+ X-Compile-Source-JDK1.3/X-Compile-Source-JDK
+
Re: [lang] VariableFormatter - pre 2.2
Henri Yandell wrote: On 8/2/06, Gary Gregory [EMAIL PROTECTED] wrote: I think in some places it was to avoid clash with JDK 1.5. StringBuilder I presume being the one. (I sent a mail earlier, but its not arrived) But yes, this is the key point. StrBuilder is a pre JDK5 version of StringBuilder - except that it has many many more features :-) Hence the rest of the classes are named in sympathy. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Commons-Math] util.TransformerMap java doc's
repeted word of transformation of of mixed object in java docs for org.apache.commons.math.util.TransformerMap - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
