DO NOT REPLY [Bug 37782] - [email] API for TLS authentication and JNDI mail session integration
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=37782. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37782 [EMAIL PROTECTED] changed: What|Removed |Added Summary|API for TLS authentication |[email] API for TLS |and JNDI mail session |authentication and JNDI mail |integration |session integration -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 37783] - [email] Bug when using a mail session with authentification
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=37783. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37783 [EMAIL PROTECTED] changed: What|Removed |Added Summary|Bug when using a mail |[email] Bug when using a |session with|mail session with |authentification|authentification -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354016 - /jakarta/commons/proper/configuration/trunk/project.properties
Author: ebourg Date: Mon Dec 5 00:16:22 2005 New Revision: 354016 URL: http://svn.apache.org/viewcvs?rev=354016view=rev Log: Added the maven.compile.source to compile with the JDK 1.5 Modified: jakarta/commons/proper/configuration/trunk/project.properties Modified: jakarta/commons/proper/configuration/trunk/project.properties URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/project.properties?rev=354016r1=354015r2=354016view=diff == --- jakarta/commons/proper/configuration/trunk/project.properties (original) +++ jakarta/commons/proper/configuration/trunk/project.properties Mon Dec 5 00:16:22 2005 @@ -34,5 +34,6 @@ maven.jar.resources=conf/resources.jar maven.compile.target = 1.3 +maven.compile.source = 1.3 maven.javacc.javacc.grammar=src/java/org/apache/commons/configuration/plist/PropertyListParser.jj - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354017 - in /jakarta/commons/proper/configuration/trunk/conf: checkstyle-suppressions.xml checkstyle.xml
Author: ebourg Date: Mon Dec 5 00:21:58 2005 New Revision: 354017 URL: http://svn.apache.org/viewcvs?rev=354017view=rev Log: The classes generated by JavaCC are no longer checked by CheckStyke Removed the FileLength check, it should not take the javadoc into consideration Allowed the declaration of unchecked exceptions Added '3' as a magic number Javadoc is now mandatory for public methods only Added: jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml Modified: jakarta/commons/proper/configuration/trunk/conf/checkstyle.xml Added: jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml?rev=354017view=auto == --- jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml (added) +++ jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml Mon Dec 5 00:21:58 2005 @@ -0,0 +1,20 @@ +?xml version=1.0? + +!DOCTYPE suppressions PUBLIC +-//Puppy Crawl//DTD Suppressions 1.0//EN +http://www.puppycrawl.com/dtds/suppressions_1_0.dtd; + +!-- Exceptions for Checkstyle -- + +suppressions + +!-- Disable the warnings for the generated classes -- +suppress checks=.* files=ParseException.java/ +suppress checks=.* files=PropertyListParser.java/ +suppress checks=.* files=PropertyListParserConstants.java/ +suppress checks=.* files=PropertyListParserTokenManager.java/ +suppress checks=.* files=SimpleCharStream.java/ +suppress checks=.* files=Token.java/ +suppress checks=.* files=TokenMgrError.java/ + +/suppressions Modified: jakarta/commons/proper/configuration/trunk/conf/checkstyle.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/conf/checkstyle.xml?rev=354017r1=354016r2=354017view=diff == --- jakarta/commons/proper/configuration/trunk/conf/checkstyle.xml (original) +++ jakarta/commons/proper/configuration/trunk/conf/checkstyle.xml Mon Dec 5 00:21:58 2005 @@ -20,6 +20,10 @@ !-- See http://checkstyle.sf.net/config_misc.html#Translation -- module name=Translation/ +!-- Exceptions -- +module name=SuppressionFilter +property name=file value=conf/checkstyle-suppressions.xml/ +/module module name=TreeWalker @@ -28,6 +32,7 @@ !-- Checks for Javadoc comments. -- !-- See http://checkstyle.sf.net/config_javadoc.html -- module name=JavadocMethod +property name=scope value=public/ property name=allowUndeclaredRTE value=true/ /module module name=JavadocType @@ -70,7 +75,7 @@ !-- Checks for Size Violations.-- !-- See http://checkstyle.sf.net/config_sizes.html -- -module name=FileLength/ +!--module name=FileLength/-- module name=LineLength property name=max value=120/ /module @@ -117,9 +122,13 @@ module name=EqualsHashCode/ module name=IllegalInstantiation/ module name=InnerAssignment/ -module name=MagicNumber/ +module name=MagicNumber +property name=ignoreNumbers value=-1,0,1,2,3/ +/module module name=MissingSwitchDefault/ -module name=RedundantThrows/ +module name=RedundantThrows +property name=allowUnchecked value=true/ +/module module name=SimplifyBooleanExpression/ module name=SimplifyBooleanReturn/ module name=StringLiteralEquality/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354018 - /jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Author: ebourg
Date: Mon Dec 5 00:23:00 2005
New Revision: 354018
URL: http://svn.apache.org/viewcvs?rev=354018view=rev
Log:
Reduced the usage of 'magic numbers' for checkstyle
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java?rev=354018r1=354017r2=354018view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Mon Dec 5 00:23:00 2005
@@ -538,18 +538,20 @@
color = color.substring(1);
}
-int red = Integer.parseInt(color.substring(0, 2), 16);
-int green = Integer.parseInt(color.substring(2, 4), 16);
-int blue = Integer.parseInt(color.substring(4, 6), 16);
+int[] components = new int[3];
+for (int i = 0; i components.length; i++) {
+components[i] = Integer.parseInt(color.substring(i, i +
2), HEX_RADIX);
+}
+
int alpha = 255;
// parse the transparency
if (color.length() = 8)
{
-alpha = Integer.parseInt(color.substring(6, 8), 16);
+alpha = Integer.parseInt(color.substring(6, 8), HEX_RADIX);
}
-return new Color(red, green, blue, alpha);
+return new Color(components[0], components[1], components[2],
alpha);
}
catch (Exception e)
{
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354019 - in /jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration: ConfigurationMap.java PropertiesConfiguration.java beanutils/ConfigurationDynaClass.java
Author: ebourg
Date: Mon Dec 5 00:23:53 2005
New Revision: 354019
URL: http://svn.apache.org/viewcvs?rev=354019view=rev
Log:
Checkstyle changes (private properties, declaration order, white spaces)
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertiesConfiguration.java
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaClass.java
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java?rev=354019r1=354018r2=354019view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
Mon Dec 5 00:23:53 2005
@@ -39,18 +39,7 @@
/**
* The codeConfiguration/code wrapped by this class.
*/
-Configuration configuration;
-
-/**
- * Returns the wrapped codeConfiguration/code object.
- *
- * @return the wrapped configuration
- * @since 1.2
- */
-public Configuration getConfiguration()
-{
-return configuration;
-}
+private Configuration configuration;
/**
* Creates a new instance of a codeConfigurationMap/code
@@ -62,6 +51,17 @@
public ConfigurationMap(Configuration configuration)
{
this.configuration = configuration;
+}
+
+/**
+ * Returns the wrapped codeConfiguration/code object.
+ *
+ * @return the wrapped configuration
+ * @since 1.2
+ */
+public Configuration getConfiguration()
+{
+return configuration;
}
/**
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertiesConfiguration.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertiesConfiguration.java?rev=354019r1=354018r2=354019view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertiesConfiguration.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertiesConfiguration.java
Mon Dec 5 00:23:53 2005
@@ -155,10 +155,10 @@
public class PropertiesConfiguration extends AbstractFileConfiguration
{
/** The list of possible key/value separators */
-private static final char[] SEPARATORS = new char[] { '=', ':' };
+private static final char[] SEPARATORS = new char[] {'=', ':'};
/** The white space characters used as key/value separators. */
-private static final char[] WHITE_SPACE = new char[] { ' ', '\t', '\f' };
+private static final char[] WHITE_SPACE = new char[]{' ', '\t', '\f'};
/**
* The default encoding (ISO-8859-1 as specified by
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaClass.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaClass.java?rev=354019r1=354018r2=354019view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaClass.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/beanutils/ConfigurationDynaClass.java
Mon Dec 5 00:23:53 2005
@@ -42,7 +42,7 @@
private static Log log = LogFactory.getLog(ConfigurationDynaClass.class);
/** Stores the associated configuration.*/
-Configuration configuration;
+private Configuration configuration;
/**
* Construct an instance of a codeConfigurationDynaClass/code
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 37574] - [lang] [PATCH] new ExceptionUtils.setCause() method
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=37574. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37574 --- Additional Comments From [EMAIL PROTECTED] 2005-12-05 09:39 --- Hello, does any commons-lang committer have the time to take a short look to the patches I provided? Thank you in advance. Andrea. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[logging] J2EE resource adapter
Hi, Has anybody in the logging community thought of transactional logging yet? That means using a JTA transaction to collect logging statements and write them out on commit or discard them on rollback. Such a thing is generally useful when you write business logs. They are not used for debugging but to record for instance user actions in a system. You don't want to see uncommitted actions there generally. So I thought, why not provide a J2EE resource adapter (RAR) implementation for commons-logging. What do you think about the idea? Ortwin Glück - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-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-test has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 11 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-test : Commons Jelly
Full details are available at:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-test/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for
property maven.jar.servletapi.
-DEBUG- Dependency on jakarta-taglibs-standard exists, no need to add for
property maven.jar.jstl.
-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/build.properties]
-DEBUG- (Gump generated) Maven Properties in:
/usr/local/gump/public/workspace/commons-jelly/build.properties
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/usr/local/gump/public/workspace/commons-jelly/project.xml
-DEBUG- Maven project properties in:
/usr/local/gump/public/workspace/commons-jelly/project.properties
-INFO- Project Reports in:
/usr/local/gump/public/workspace/commons-jelly/target/test-reports
The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-test/gump_work/build_commons-jelly_commons-jelly-test.html
Work Name: build_commons-jelly_commons-jelly-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 54 secs
Command Line: maven --offline jar
[Working Directory: /usr/local/gump/public/workspace/commons-jelly]
CLASSPATH:
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/forehead/forehead-1.0-beta-5.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
At tag test:assertEquals: line: 359 column: 75
[junit] org.apache.commons.jelly.JellyTagException:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly:359:75:
test:assertEquals expected:[22] but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
At tag test:assertEquals: line: 359 column: 75
[junit] at
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:712)
[junit] at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
[junit] at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] Caused by:
org.apache.commons.jelly.tags.junit.JellyAssertionFailedError: expected:[22]
but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
At tag test:assertEquals: line: 359 column: 75
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:39)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.failNotEquals(AssertTagSupport.java:62)
[junit] at
org.apache.commons.jelly.tags.junit.AssertEqualsTag.doTag(AssertEqualsTag.java:55)
[junit]
[EMAIL PROTECTED]: Project commons-jelly-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-test has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 11 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-test : Commons Jelly
Full details are available at:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-test/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for
property maven.jar.servletapi.
-DEBUG- Dependency on jakarta-taglibs-standard exists, no need to add for
property maven.jar.jstl.
-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/build.properties]
-DEBUG- (Gump generated) Maven Properties in:
/usr/local/gump/public/workspace/commons-jelly/build.properties
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/usr/local/gump/public/workspace/commons-jelly/project.xml
-DEBUG- Maven project properties in:
/usr/local/gump/public/workspace/commons-jelly/project.properties
-INFO- Project Reports in:
/usr/local/gump/public/workspace/commons-jelly/target/test-reports
The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-test/gump_work/build_commons-jelly_commons-jelly-test.html
Work Name: build_commons-jelly_commons-jelly-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 54 secs
Command Line: maven --offline jar
[Working Directory: /usr/local/gump/public/workspace/commons-jelly]
CLASSPATH:
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/forehead/forehead-1.0-beta-5.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
At tag test:assertEquals: line: 359 column: 75
[junit] org.apache.commons.jelly.JellyTagException:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly:359:75:
test:assertEquals expected:[22] but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
At tag test:assertEquals: line: 359 column: 75
[junit] at
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:712)
[junit] at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
[junit] at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] Caused by:
org.apache.commons.jelly.tags.junit.JellyAssertionFailedError: expected:[22]
but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File:
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
At tag test:assertEquals: line: 359 column: 75
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:39)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.failNotEquals(AssertTagSupport.java:62)
[junit] at
org.apache.commons.jelly.tags.junit.AssertEqualsTag.doTag(AssertEqualsTag.java:55)
[junit]
[EMAIL PROTECTED]: Project commons-vfs (in module jakarta-commons) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-vfs has an issue affecting its community integration. This issue affects 72 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-chaperon : Java XML Framework - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-faces : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A jcr: protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-sample : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-vfs : Jakarta commons - excalibur-fortress-bean : Repository of reusable components. - excalibur-fortress-container-impl : Repository of reusable components. - excalibur-fortress-container-test : Repository of reusable components. - excalibur-fortress-examples : Repository of reusable components. - excalibur-fortress-migration : Repository of reusable components. - excalibur-fortress-platform : Repository of reusable components. - excalibur-fortress-testcase : Repository of reusable components. - excalibur-monitor : Repository of reusable components. - excalibur-sourceresolve : Repository of reusable components. - excalibur-xmlutil : Repository of reusable components. - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... - lenya : Content Management System - logging-log4j-chainsaw : Chainsaw log viewer Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-vfs-05122005.jar] identifier set to project name -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/gump_work/build_jakarta-commons_commons-vfs.html Work Name: build_jakarta-commons_commons-vfs
[EMAIL PROTECTED]: Project commons-vfs (in module jakarta-commons) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-vfs has an issue affecting its community integration. This issue affects 72 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-chaperon : Java XML Framework - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-faces : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A jcr: protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-sample : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-vfs : Jakarta commons - excalibur-fortress-bean : Repository of reusable components. - excalibur-fortress-container-impl : Repository of reusable components. - excalibur-fortress-container-test : Repository of reusable components. - excalibur-fortress-examples : Repository of reusable components. - excalibur-fortress-migration : Repository of reusable components. - excalibur-fortress-platform : Repository of reusable components. - excalibur-fortress-testcase : Repository of reusable components. - excalibur-monitor : Repository of reusable components. - excalibur-sourceresolve : Repository of reusable components. - excalibur-xmlutil : Repository of reusable components. - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... - lenya : Content Management System - logging-log4j-chainsaw : Chainsaw log viewer Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-vfs-05122005.jar] identifier set to project name -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/gump_work/build_jakarta-commons_commons-vfs.html Work Name: build_jakarta-commons_commons-vfs
[EMAIL PROTECTED]: Project commons-jelly-tags-xml-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-xml-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-xml-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-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/xml/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/gump_work/build_commons-jelly_commons-jelly-tags-xml-test.html Work Name: build_commons-jelly_commons-jelly-tags-xml-test (Type: Build) Work ended in a state of : Failed Elapsed: 41 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testSetSingleNodeAndAsString(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81: x:set You must define an attribute called 'select' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81: x:set You must define an attribute called 'select' for this tag. [junit] at org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86) [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.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testSetStringLists(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82: x:set You must define an attribute called 'select' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82: x:set You must define an attribute called 'select' for this tag. [junit] at org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86) [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.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testEntities(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit]
[EMAIL PROTECTED]: Project commons-jelly-tags-xml-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-xml-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-xml-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-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/xml/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/gump_work/build_commons-jelly_commons-jelly-tags-xml-test.html Work Name: build_commons-jelly_commons-jelly-tags-xml-test (Type: Build) Work ended in a state of : Failed Elapsed: 41 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testSetSingleNodeAndAsString(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81: x:set You must define an attribute called 'select' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81: x:set You must define an attribute called 'select' for this tag. [junit] at org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86) [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.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testSetStringLists(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82: x:set You must define an attribute called 'select' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82: x:set You must define an attribute called 'select' for this tag. [junit] at org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86) [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.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testEntities(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit]
Re: [all] Maven, help or hinderance?
Torsten Curdt wrote: On 04.12.2005, at 02:17, Stephen Colebourne wrote: Hate to be an old fart here but was ant really all that bad? Oh ...please don't! All I have to say: dependency management plus the reports are just enough for me to never want to switch back to ant again. Even from m1! Worst case I was always able to come up with some non-standard goals-magic to do what I wanted. My 2 cents -- Torsten That wasn't Stephen Colebourne's comment, it was originally mine :-) I just did a release, my first in over a year, and man, was it annoying. But I wasn't completely serious. Maven allows us to produce a much nicer site with more functionality - no doubt about it. However, there are more steps now, more things to keep track of, more things to go wrong. And my comment sparked quite a lot of thread. My real thoughts are that it is now time to tighten up the jakarta-commons standard and documentation for maven use so that there are fewer of these manual extra steps that need to be done for every release. This is how this starts: Someone comes up with a neat idea and adds a manual step to the process to do that. Often, but not always, this gets documented. Better yet would be if it could get automated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-swing (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-swing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-swing : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/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-swing-05122005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/gump_work/build_commons-jelly_commons-jelly-tags-swing.html Work Name: build_commons-jelly_commons-jelly-tags-swing (Type: Build) Work ended in a state of : Failed Elapsed: 3 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/interaction/target/commons-jelly-tags-interaction-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at java.lang.Class.newInstance0(Class.java:308) at java.lang.Class.newInstance(Class.java:261) at org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:432) at org.apache.maven.jelly.MavenJellyContext.getTagLibrary(MavenJellyContext.java:171) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1033) at org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:647) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown
[EMAIL PROTECTED]: Project commons-jelly-tags-swing (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-swing has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-swing : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/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-swing-05122005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports -WARNING- No directory [/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/gump_work/build_commons-jelly_commons-jelly-tags-swing.html Work Name: build_commons-jelly_commons-jelly-tags-swing (Type: Build) Work ended in a state of : Failed Elapsed: 3 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/interaction/target/commons-jelly-tags-interaction-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at java.lang.Class.newInstance0(Class.java:308) at java.lang.Class.newInstance(Class.java:261) at org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:432) at org.apache.maven.jelly.MavenJellyContext.getTagLibrary(MavenJellyContext.java:171) at org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1033) at org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:647) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown
[EMAIL PROTECTED]: Project commons-jelly-tags-define-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-define-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-define-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-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/define/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/gump_work/build_commons-jelly_commons-jelly-tags-define-test.html Work Name: build_commons-jelly_commons-jelly-tags-define-test (Type: Build) Work ended in a state of : Failed Elapsed: 14 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - [junit] at org.jaxen.saxpath.base.XPathReader.unionExpr(XPathReader.java:1129) [junit] at org.jaxen.saxpath.base.XPathReader.unaryExpr(XPathReader.java:1117) [junit] at org.jaxen.saxpath.base.XPathReader.multiplicativeExpr(XPathReader.java:1039) [junit] at org.jaxen.saxpath.base.XPathReader.additiveExpr(XPathReader.java:982) [junit] at org.jaxen.saxpath.base.XPathReader.relationalExpr(XPathReader.java:902) [junit] at org.jaxen.saxpath.base.XPathReader.equalityExpr(XPathReader.java:850) [junit] at org.jaxen.saxpath.base.XPathReader.andExpr(XPathReader.java:826) [junit] at org.jaxen.saxpath.base.XPathReader.orExpr(XPathReader.java:804) [junit] at org.jaxen.saxpath.base.XPathReader.expr(XPathReader.java:797) [junit] at org.jaxen.saxpath.base.XPathReader.parse(XPathReader.java:105) [junit] at org.jaxen.BaseXPath.init(BaseXPath.java:126) [junit] at org.jaxen.BaseXPath.init(BaseXPath.java:152) [junit] at org.jaxen.dom4j.Dom4jXPath.init(Dom4jXPath.java:101) [junit] at org.apache.commons.jelly.expression.xpath.XPathExpression.evaluate(XPathExpression.java:78) [junit] at org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:256) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] at junit.framework.TestCase.runBare(TestCase.java:127) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [junit] at
[EMAIL PROTECTED]: Project commons-jelly-tags-define-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-define-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-define-test : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-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/define/build.properties] -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/test-reports The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/gump_work/build_commons-jelly_commons-jelly-tags-define-test.html Work Name: build_commons-jelly_commons-jelly-tags-define-test (Type: Build) Work ended in a state of : Failed Elapsed: 14 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/define] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - [junit] at org.jaxen.saxpath.base.XPathReader.unionExpr(XPathReader.java:1129) [junit] at org.jaxen.saxpath.base.XPathReader.unaryExpr(XPathReader.java:1117) [junit] at org.jaxen.saxpath.base.XPathReader.multiplicativeExpr(XPathReader.java:1039) [junit] at org.jaxen.saxpath.base.XPathReader.additiveExpr(XPathReader.java:982) [junit] at org.jaxen.saxpath.base.XPathReader.relationalExpr(XPathReader.java:902) [junit] at org.jaxen.saxpath.base.XPathReader.equalityExpr(XPathReader.java:850) [junit] at org.jaxen.saxpath.base.XPathReader.andExpr(XPathReader.java:826) [junit] at org.jaxen.saxpath.base.XPathReader.orExpr(XPathReader.java:804) [junit] at org.jaxen.saxpath.base.XPathReader.expr(XPathReader.java:797) [junit] at org.jaxen.saxpath.base.XPathReader.parse(XPathReader.java:105) [junit] at org.jaxen.BaseXPath.init(BaseXPath.java:126) [junit] at org.jaxen.BaseXPath.init(BaseXPath.java:152) [junit] at org.jaxen.dom4j.Dom4jXPath.init(Dom4jXPath.java:101) [junit] at org.apache.commons.jelly.expression.xpath.XPathExpression.evaluate(XPathExpression.java:78) [junit] at org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:256) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] at junit.framework.TestCase.runBare(TestCase.java:127) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [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 11 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: 17 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.4/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/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - [junit] at org.apache.commons.jelly.tags.xml.ExprTag.doTag(ExprTag.java:46) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) [junit] at org.apache.commons.jelly.TagSupport.getBodyText(TagSupport.java:234) [junit] at org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:90) [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.tags.jsl.TemplateTag$1.run(TemplateTag.java:160) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58) [junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:79) [junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58) [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 11 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: 17 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl] CLASSPATH: /opt/jdk1.4/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/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar - [junit] at org.apache.commons.jelly.tags.xml.ExprTag.doTag(ExprTag.java:46) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262) [junit] at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186) [junit] at org.apache.commons.jelly.TagSupport.getBodyText(TagSupport.java:234) [junit] at org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:90) [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.tags.jsl.TemplateTag$1.run(TemplateTag.java:160) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58) [junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:79) [junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171) [junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58) [junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102) [junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91) [junit] at
Re: [jelly] Gump failures
Brett Porter wrote: It was intentionally breaking, I think. I was told that it tightening up conformance. Others are welcome to pursue it further, this isn't really my realm of expertise. Brett, would you have a copy of the mails ? Such a strengthening would be related to a reported non-conformance issue, or? I agree. It should be fixed at either the Jelly or Jaxen end, but if nobody is stepping up to do so (and I certainly can't), then turn off the nags and put it in jira would be my vote. Maybe I find time to hit this... paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354056 - in /jakarta/commons/proper/commons-build/trunk: project.properties xdocs/releases/prepare.xml xdocs/releases/release.xml
Author: scohen Date: Mon Dec 5 04:21:55 2005 New Revision: 354056 URL: http://svn.apache.org/viewcvs?rev=354056view=rev Log: remove stale info about STATUS.html from release.xml. Move stuff from there to prepare.xml where it belongs. Update project.properties with correct maven.xdoc.jsl value Modified: jakarta/commons/proper/commons-build/trunk/project.properties jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml Modified: jakarta/commons/proper/commons-build/trunk/project.properties URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/project.properties?rev=354056r1=354055r2=354056view=diff == --- jakarta/commons/proper/commons-build/trunk/project.properties (original) +++ jakarta/commons/proper/commons-build/trunk/project.properties Mon Dec 5 04:21:55 2005 @@ -45,7 +45,7 @@ ## # commons site LF ## -maven.xdoc.jsl=../commons-build/commons-site.jsl +maven.xdoc.jsl=commons-site.jsl maven.xdoc.date=left maven.xdoc.poweredby.image=maven-feather.png maven.xdoc.developmentProcessUrl=http://jakarta.apache.org/commons/charter.html Modified: jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml?rev=354056r1=354055r2=354056view=diff == --- jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml (original) +++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml Mon Dec 5 04:21:55 2005 @@ -596,6 +596,18 @@ /ul /subsection +subsection name=project.xml (aka POM) +p + project.xml, used by Maven to generate that site, has some data which may have become stale. + Make sure it isn't before releasing. Look at the dependencies report, todo report, + and other reports. +/p +ul +liEnsure dependencies are correct/li +liEnsure completed tasks are removed from todo list/li +/ul +/subsection + subsection name=Code Style p Many projects enforce coding styles using the CheckStyle or PMD tools. If your Modified: jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml?rev=354056r1=354055r2=354056view=diff == --- jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml (original) +++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/release.xml Mon Dec 5 04:21:55 2005 @@ -557,15 +557,6 @@ /p ul li -strongUpdate STATUS.html/strong -Check and update STATUS.html: -ul -liUpdate release info section/li -liEnsure dependencies are correct/li -liEnsure completed tasks are removed from todo list/li -/ul -/li -li strongUpdate Build Version Number/strong Update build number found in codebuild.xml/code in the trunk. This should be updated to a codedev/code release, eg change 1.2 to 1.3-dev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Maven, help or hinderance?
That wasn't Stephen Colebourne's comment, it was originally mine :-) Sorry, Stephen ...snipped the wrong header :) snip/ My real thoughts are that it is now time to tighten up the jakarta- commons standard and documentation for maven use so that there are fewer of these manual extra steps that need to be done for every release. Ok This is how this starts: Someone comes up with a neat idea and adds a manual step to the process to do that. Often, but not always, this gets documented. Better yet would be if it could get automated. Sure cheers -- Torsten PGP.sig Description: This is a digitally signed message part
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
Phil Steitz wrote: On 12/4/05, Steve Cohen [EMAIL PROTECTED] wrote: Phil Steitz wrote: On 12/4/05, Steve Cohen [EMAIL PROTECTED] wrote: Martin Cooper wrote: On 12/4/05, Steve Cohen [EMAIL PROTECTED] wrote: Phil Steitz wrote: On 12/4/05, Steve Cohen [EMAIL PROTECTED] wrote: This is another inaccuracy in the instructions. Step 14 says the dependencies are listed in STATUS.html. Net, at least doesn't have a STATUS.html. These seem to be generated from project.xml. Good point. Patch / update welcome. It would be great if you could bundle up any other issues that you ran into into a patch or direct update for the building/releasing docs. Phil I will, Phil. But is the non-existence of STATUS.html common to all of commons? If so, I will make the revisions myself. Incidentally, these items are all handled now prior to cutting the release, not as post release items. The STATUS files are a hold-over from the pre-Maven days. They were required because there was no POM / project.xml file in which the committer list could be maintained. Now that all of the components are using Maven, the STATUS files are pretty much obsolete. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Martin. I'll be happy to update the files myself, but where are they? I see some files that look like old versions of the site in commons-build's xdocs but they don't match what's on the site now. I've glanced all over the repository and haven't found the right place yet. The relevant files are in http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk/xdocs/releases/ maven site from /commons-build should generate the site locally for you, then maven site:sshdeploy to publish (assuming you have key set up) Make sure to check changes in before updating the site. Thanks! Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Alas and alack. More maven problems. Couldn't run maven site on commons-build Downloaded maven 1.0.2 Reinstalled the maven xdoc plugin 1.9.2 get this: xdoc:jelly-transform: [echo] en [echo] The current Locale is the default one [echo] Scanning '/home/scohen/commons-build/target/generated-xdocs'... [echo] Generating /home/scohen/commons-build/target/docs/license.html from /home/scohen/commons-build/target/generated-xdocs/license.xml BUILD FAILED File.. /home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin.jelly Element... j:include Line.. 479 Column 58 file:/home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin-resources/site.jsl:33:17: jsl:stylesheet file:/home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin-resources/site.jsl:156:57: jsl:applyTemplates file:/home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin-resources/site.jsl:240:105: maven:property You must define an attribute called 'defaultValue' for this tag. Total time: 10 seconds Finished at: Sun Dec 04 22:09:51 CST 2005 :-( Are you sure you are executing maven from the the right directory - i.e., not above trunk? Also, you need the top-level directory to be named commons-build The second requirement can probably be removed by changing maven.xdoc.jsl=../commons-build/commons-site.jsl to maven.xdoc.jsl=commons-site.jsl In project.properties. Phil Thanks for all your help. These last suggestions worked. I built the site, tested my changes, then pushed the site. I DON'T have my key set up. where do I do this, it's a pain to keep typing in my password, but doable. Also, fyi, in my pushing of the site, I saw gobs of [exec] chmod: some/file: Operation not permitted Is this something not set up properly in my account or an expected glitch? In any case somebody might want to check the chmod settings of the site now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
snip Thanks for all your help. These last suggestions worked. I built the site, tested my changes, then pushed the site. I DON'T have my key set up. where do I do this, it's a pain to keep typing in my password, but doable. As indicated on the building page, you should follow the instructions on the bottom of this page: http://www.apache.org/dev/cvs-on-unix.html Also, fyi, in my pushing of the site, I saw gobs of [exec] chmod: some/file: Operation not permitted Is this something not set up properly in my account or an expected glitch? In any case somebody might want to check the chmod settings of the site now. Can't check this now, perhaps someone else can and also recall what causes this error message. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-jelly-tags-html (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-html has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-html : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/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-html-05122005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-reports -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/gump_work/build_commons-jelly_commons-jelly-tags-html.html Work Name: build_commons-jelly_commons-jelly-tags-html (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar:/usr/local/gump/packages/nekohtml-0.9.5/nekohtml.jar - [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testLowerCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48: test:assert You must define an attribute called 'test' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48: test:assert You must define an attribute called 'test' for this tag. [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54) [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.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testMixedCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48: test:assert You must define an attribute called 'test' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48: test:assert You must define an attribute called 'test' for this tag. [junit] at
[EMAIL PROTECTED]: Project commons-jelly-tags-html (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-html has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 11 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-html : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/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-html-05122005.jar] identifier set to project name -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.properties -INFO- Project Reports in: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-reports -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/gump_work/build_commons-jelly_commons-jelly-tags-html.html Work Name: build_commons-jelly_commons-jelly-tags-html (Type: Build) Work ended in a state of : Failed Elapsed: 15 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/commons-jelly/jelly-tags/html] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-05122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-05122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-05122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar:/usr/local/gump/packages/nekohtml-0.9.5/nekohtml.jar - [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testLowerCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48: test:assert You must define an attribute called 'test' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48: test:assert You must define an attribute called 'test' for this tag. [junit] at org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54) [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.tags.junit.CaseTag$1.runTest(CaseTag.java:59) [junit] [junit] [junit] Testcase: testMixedCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48: test:assert You must define an attribute called 'test' for this tag. [junit] org.apache.commons.jelly.MissingAttributeException: file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48: test:assert You must define an attribute called 'test' for this tag. [junit] at
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
On 12/5/05, Phil Steitz [EMAIL PROTECTED] wrote: snip Thanks for all your help. These last suggestions worked. I built the site, tested my changes, then pushed the site. I DON'T have my key set up. where do I do this, it's a pain to keep typing in my password, but doable. As indicated on the building page, you should follow the instructions on the bottom of this page: http://www.apache.org/dev/cvs-on-unix.html I see now that the link in section 8 of the releasing page to instructions for this is broken.I think there used to be a how-to which has moved or been deleted. We should fix that link - just change to above - in any case. Another thing that we should think about, given the comments about automation, is moving the content in 16 up higher and making Windows batch files to do the same thing as the shell scripts referenced there. These scripts automate much of the drudgery in sections 2-4 and 7. I guess we could also try to get the dist plugin to do the 2-4 stuff, but IIRC there are problems integrating with the native OS stuff required to handle keys and create sigs. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [logging] J2EE resource adapter
Hello, IMHO you're better off implementing such a functionality for a specific logger implementation and enable it in that configuration. Thoughts? - Jörg Jörg, thanks for your feedback. I know that it is just a wrapper. That's an advantage in my opinion. Because the resource adapter could then be used with any logging framework. The timestamp problem has also occurred to me. It can not be solved by using Log4J directly either. I don't mean the rar should go into the standard JCL distribution. It could be an add-on package. Ortwin I think this is a bad idea. Not in sense of the technical design/implementation, but looking at the use-case: To document business transactions you have to collect informations about them. I am working at a IT center for banks. A simple transaction could modifiy an account and the customer who owns the account. I would have to document three things: the usecase (changing name becaus of marriage), the id of the account, the id of the customer and old/new value of his/her name. Doing this with a logging framework would mean to pass everthing to a String, we could discuss csv or a readable form (4711,2323,changename,maier,schmidt or CustomerID[4711] AccountId[2323] UseCase[changename] OldValue[Maier] NewValue[Schmidt]). Having these things in a file is a bad idea in my opinion. This is a classic case for a structured persistence, a database. One part is a very good idea: To establish a RAR Handler/Appender for logging (meant as classic logging for debug/info/error program information). This has a technical reason: File access is limited by the J2EE specification (most vendors allow more, but the spec describes restricted access), see [1] section 6.2ff, especially 6.2.3. To conform to J2EE one has to use a Resource Adaptor for logging. I know that this is different to actual practice and technical restrictions of J2EE Application server implementations, but may change in future. I.E. when the security permissions are enforced by the AppServers by Code, not by properties. Regards Boris [1] http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons proper karma for Rahul Akolkar
On 12/5/05, Simon Kitching [EMAIL PROTECTED] wrote: On Sun, 2005-12-04 at 09:33 -0800, Martin Cooper wrote: On 12/4/05, Phil Steitz [EMAIL PROTECTED] wrote: Rahul is an apache committer who already has commons-sandbox karma and is interested in contributing to commons proper as well. Let's give him karma to commons proper. Sorry, got busy last night with house stuff. Karma added for Rahul. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Website changes (was Re: short critique of site)
Hi Mario, Sorry for not being there on sunday to finish of the commit :) - The current list of contributors are only committers. - The committers are collected from the project.xml (the developers section in maven), so a lot more inactive people out there are probably listed. - Just the list of committers is generated. The current contributor page is split up in 2 parts : top and bottom. The emuritus committers are at the bottom. - I let maven glue the top, list of committers and bottom together. - You end up with a generated contributors.xml in the xdocs directory. - The generation is currently hooked into the commons-site-generate goal. - The generation itself happens in the commons-contributors-page-generate goal. A choices need to be made before commit : Do we want to generate the committers from the commons-site-generate goal ? or Do we want to generate this on demand by calling a specific goal (I'll rename the goal to something more friendly). or Make both possible ? (I am currently reusing the list of loaded poms that the reactor stores in a variable) Mvgr, Martin Mario Ivankovits wrote: Martin van den Bemt wrote: Also have a look at http://people.apache.org/~mvdb/contributors.html which was automatically generated by maven, based on the all the developers sections in commons-proper. Should this be a list of contributers and/or committers? I ask as the headline talks about contributors but on the list are only committers. At least the VFS contributors are missing. If we are able to autogenerate this list, maybe we might list the contributors too. How did you create the Emeritus section? Is this list based on the (non) commits in the last year? I ask as e.g. adammurdoch is still on the list but I cant find a commit. I have no problem with him, but if we would like to have a correct status than this is a failure, isnt it? BTW I just checked the commons-dev commit messages, so maybe I missed something. --- Mario - 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: [email] MBoxMimeMessage
Looks usefull..
+1 :)
Don't forget the software grant ;)
Mvgr,
Martin
Henri Yandell wrote:
I'd like to add the work in www.osjava.org's gj-mail to [email] if I may.
It's a small package with two classes that do the following things:
1) Mailer class for easy emailing.
2) Template style emailing; ${foo} etc.
3) MBoxMimeMessage
Now, 1) should be unnecessary, I assume [email] already does this. 2)
is unwanted, user's should use velocity or some other template engine.
3) is the bit I'd like to add.
It allows messages that look liks SMTP, or mbox emails, rather than
just containing the message. So the From:, To:, Subject: etc etc are
all in there. This makes for a much nicer time if someone is using a
template style system for emailing as the person modifying the
template can handle these issues instead of asking the coder.
Attachments are buggy, so I'd commit time to fixing these if the
MBoxMimeMessage looks attractive to the community. I'd
javadoc/unit-test obviously and would be able to kill gj-mail in
favour of [email].
Any interest?
Source can be seen at:
http://www.osjava.org/genjava/multiproject/gj-mail/xref/index.html
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: [VOTE] Release commons math 1.1
+1 Although I am not the best judge of the Math component, everything looks pretty much complete (eg lot of tests, all tests pass) and I am very impressed with the message zarro bugs in bugzilla :) And another note : don't forget to vote yourself Phil :) Mvgr, Martin Phil Steitz wrote: There have been no problems reported with math 1.1 RC4, other than some small javadoc fixes, which have been applied to the release branch. Assuming a positive vote, I will cut a new signed release, including these fixes. Release notes are here: http://people.apache.org/~psteitz/commons-math/1-1-rc4/RELEASE-NOTES.txt And apidocs: http://people.apache.org/~psteitz/commons-math/1-1-rc4/apidocs/ The RC4 jar (commons-math-1.1-RC4.jar) has also been deployed to the apache internal maven repository at cvs.apache.org/repository Votes, please. The vote will close in 72 hours. Thanks in advance! Phil --- [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Maven, help or hinderance?
This is how this starts: Someone comes up with a neat idea and adds a manual step to the process to do that. Often, but not always, this gets documented. Better yet would be if it could get automated. Automation is definitely worthwhile with so many components... Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354089 - in /jakarta/commons/proper/commons-build/trunk/src/xdocs: ./ contributorsend.xml contributorsstart.xml
Author: mvdb Date: Mon Dec 5 08:18:56 2005 New Revision: 354089 URL: http://svn.apache.org/viewcvs?rev=354089view=rev Log: Split up contributors.xml Added: jakarta/commons/proper/commons-build/trunk/src/xdocs/ jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsend.xml (with props) jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsstart.xml (with props) Added: jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsend.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsend.xml?rev=354089view=auto == --- jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsend.xml (added) +++ jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsend.xml Mon Dec 5 08:18:56 2005 @@ -0,0 +1,27 @@ + /ul + pJoin us!/p +/section +section name=Emeritus Committers + p + The following committers have made a number of contributions to Jakarta Commons, but have + been inactive for some time. Following the Jakarta project's a href=http://jakarta.apache.org/site/roles.html;guidelines/a, + they have been named emeritus committers. These individuals may be restored to active committer status + simply by requesting it on the commons-dev mailing list. + /p + ul +liArron Bates (arron)/li +liConor MacNeill (conor)/li +liDoug Sale (dsale)/li +liDavid Winterfeldt (dwinterfeldt)/li +liPaul Hammant (hammant)/li +li(jariw)/li +liJeff Turner (jefft)/li +liMarc Saegesser (marcsaeg)/li +liMichael Smith (mas)/li +liIgnacio J. Ortega (nacho)/li +liPaulo Gaspar (paulo)/li +liVincent Massol (vmassol)/li + /ul +/section + /body +/document Propchange: jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsend.xml -- svn:executable = * Added: jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsstart.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsstart.xml?rev=354089view=auto == --- jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsstart.xml (added) +++ jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsstart.xml Mon Dec 5 08:18:56 2005 @@ -0,0 +1,26 @@ +?xml version=1.0? +!-- + Copyright 2001-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- + +document + properties +titleContributors/title +author email=commons-dev@jakarta.apache.orgCommons Documentation Team/author + /properties + body +section name=Contributors + pWe are the participants in Commons:/p + ul Propchange: jakarta/commons/proper/commons-build/trunk/src/xdocs/contributorsstart.xml -- svn:executable = * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354091 - /jakarta/commons/proper/commons-build/trunk/maven.xml
Author: mvdb
Date: Mon Dec 5 08:23:41 2005
New Revision: 354091
URL: http://svn.apache.org/viewcvs?rev=354091view=rev
Log:
Automatically generate the contributors.xml with the new goal
generate-contributors. By default it is not enabled in the build and has to be
run manually when you want the contributors page updated.
Please remember that it overwrites the xdocs/contriburors.xml file.
Modified:
jakarta/commons/proper/commons-build/trunk/maven.xml
Modified: jakarta/commons/proper/commons-build/trunk/maven.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/maven.xml?rev=354091r1=354090r2=354091view=diff
==
--- jakarta/commons/proper/commons-build/trunk/maven.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/maven.xml Mon Dec 5 08:23:41
2005
@@ -169,7 +169,11 @@
goals=site:generate
banner=Generating site for
ignoreFailures=true
+ postProcessing=true
/
+ !-- used to generate the contributors page --
+ !-- Commented out, feel free to uncomment it --
+!-- attainGoal name=generate-contributors/ --
attainGoal name=xdoc/
/goal
@@ -217,6 +221,44 @@
delete file=${maven.final.name}-site.tar.gz/
+ /goal
+
+ goal name=generate-contributors
+!--
+ don't rerun the reactor if that has already been done..
+ Use pom:verify-version, since it runs quickly..
+ --
+j:if test=${reactorProjects == null}
+ maven:reactor
+basedir=${basedir}/..
+includes=*/project.xml
+excludes=commons-build/project.xml
+goals=pom:verify-version
+banner=Generating site for
+ignoreFailures=true
+postProcessing=true
+ /
+/j:if
+
+!-- Gather all committer names and id's from the project poms and stuff
them in a treemap --
+ant:echoStart generating constributors.xml file/ant:echo
+j:new className=java.util.TreeMap var=committers/
+j:forEach var=reactorProject items=${reactorProjects}
+ j:forEach var=developer items=${reactorProject.developers}
+ ${committers.put(developer.id, developer.name)}
+ /j:forEach
+/j:forEach
+!-- output the xml parts and the committers to the contributors.xml file
--
+
+j:set var=contributorFile value=xdocs/contributors.xml/
+util:loadText file=src/xdocs/contributorsstart.xml var=cstart/
+util:loadText file=src/xdocs/contributorsend.xml var=cend/
+j:forEach var=committer items=${committers}
+ j:set var=ctext value=${ctext}lt;ligt;${committer.value}
(${committer.key})lt;/ligt;/
+/j:forEach
+j:file escapeText=false name=${contributorFile}
omitXmlDeclaration=true
+ ${cstart}${ctext}${cend}
+/j:file
/goal
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[all] [doc] Automatic generation of contributors.xml
Hi everyone, Just committed some changes so that we can automatically generate the contributors page. In src/xdocs/ are 2 files : contributorsstart.xml contributorsend.xml The start page is the previous top part of the contributors.xml file and the end is the previous bottom part (previous = the xdocs/contributors.xml current SVN version). Just type maven generate-contributors and it will be generated (will overwrite the current contrbutors.xml!). For now I commented out generation of the contributors.xml from the commons-site-generate goal. So if you you are happy with the solution, just remove the comment. It's not a work of art, but it does the job ;) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [email] MBoxMimeMessage
Henri,
There's one problem with the code. You can't use a SimpleDateFormat in
multiple threads. They're not thread-safe (Date formats are not
synchronized. It is recommended to create separate format instances for each
thread. If multiple threads access a format concurrently, it must be
synchronized externally.). I actually fixed a bug in Tomcat where they
were doing the same thing. Just create a SimpleDateFormat every time you
need it.
James
-Original Message-
From: Martin van den Bemt [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 10:20 AM
To: Jakarta Commons Developers List
Subject: Re: [email] MBoxMimeMessage
Looks usefull..
+1 :)
Don't forget the software grant ;)
Mvgr,
Martin
Henri Yandell wrote:
I'd like to add the work in www.osjava.org's gj-mail to [email] if I may.
It's a small package with two classes that do the following things:
1) Mailer class for easy emailing.
2) Template style emailing; ${foo} etc.
3) MBoxMimeMessage
Now, 1) should be unnecessary, I assume [email] already does this. 2)
is unwanted, user's should use velocity or some other template engine.
3) is the bit I'd like to add.
It allows messages that look liks SMTP, or mbox emails, rather than
just containing the message. So the From:, To:, Subject: etc etc are
all in there. This makes for a much nicer time if someone is using a
template style system for emailing as the person modifying the
template can handle these issues instead of asking the coder.
Attachments are buggy, so I'd commit time to fixing these if the
MBoxMimeMessage looks attractive to the community. I'd
javadoc/unit-test obviously and would be able to kill gj-mail in
favour of [email].
Any interest?
Source can be seen at:
http://www.osjava.org/genjava/multiproject/gj-mail/xref/index.html
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
Phil Steitz wrote: On 12/4/05, Brett Porter [EMAIL PROTECTED] wrote: Dennis Lundberg wrote: Brett said that this *should* work, so I decided to try it myself. I received the same results as you did Phil, regarding maven --info, but I think I understand what is going on now. I have posted a question about this on the maven-users list to see if I can get some confirmation. Sorry this went over my head earlier, but Dennis' analysis on the usres list is correct. Maven --info doesn't reflect the difference as it reports what's installed. Plugin dependencies are only used for the life of the project's build, not installed. So the dependency should work regardless of what maven --info says. Is that the case? Then the solution to add the necessary dependencies to commons-build won't work and what we need to do is something like pluginUpdate (bunch of explicit plugin installs from the command line). Correct? No, as I will elaborate on further down, it will work nicely. I'll leave aside for a moment the discussion whether or not it's a good idea to extend project.xml from commons-build in other components. Setting up dependencies for a specific version of a Maven plugin, i.e. the xdoc and site plugins, works the way we want them to. I have tried this and it's easy to set it up. Here's what needs to be added in commons-build/project.xml for site generation: dependencies dependency groupIdmaven/groupId artifactIdmaven-site-plugin/artifactId version1.6.1/version typeplugin/type /dependency dependency groupIdmaven/groupId artifactIdmaven-xdoc-plugin/artifactId version1.9.2/version typeplugin/type /dependency /dependencies This will ensure that building the web site for commons-build will always use these versions of the plugins, regardless of what the user has installed on his or her system. So far all is good. Now on to the to extend or not extend discussion... If commons component A extends the project.xml file from commons-build these dependencies are transfered to that component, meaning that component A doesn't have to worry about dependencies for site generation. However, if commons component B does *not* extend the project.xml file from commons-build these dependencies will have to be repeated in the project.xml file for component B. Hopefully these dependencies would not change all that often, meaning that little work would have to be done in order to keep this working, once it has been set up properly. Either way I think there is a big win including these dependencies in commons-build and all commons components. What do you think? -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Website changes (was Re: short critique of site)
On 12/5/05, Martin van den Bemt [EMAIL PROTECTED] wrote: Hi Mario, Sorry for not being there on sunday to finish of the commit :) - The current list of contributors are only committers. - The committers are collected from the project.xml (the developers section in maven), so a lot more inactive people out there are probably listed. - Just the list of committers is generated. The current contributor page is split up in 2 parts : top and bottom. The emuritus committers are at the bottom. - I let maven glue the top, list of committers and bottom together. - You end up with a generated contributors.xml in the xdocs directory. - The generation is currently hooked into the commons-site-generate goal. - The generation itself happens in the commons-contributors-page-generate goal. A choices need to be made before commit : Do we want to generate the committers from the commons-site-generate goal ? Sure. I see no reason not to do this. or Do we want to generate this on demand by calling a specific goal (I'll rename the goal to something more friendly). That just ensures that it will be out of date a lot of the time. ;-) -- Martin Cooper or Make both possible ? (I am currently reusing the list of loaded poms that the reactor stores in a variable) Mvgr, Martin Mario Ivankovits wrote: Martin van den Bemt wrote: Also have a look at http://people.apache.org/~mvdb/contributors.html which was automatically generated by maven, based on the all the developers sections in commons-proper. Should this be a list of contributers and/or committers? I ask as the headline talks about contributors but on the list are only committers. At least the VFS contributors are missing. If we are able to autogenerate this list, maybe we might list the contributors too. How did you create the Emeritus section? Is this list based on the (non) commits in the last year? I ask as e.g. adammurdoch is still on the list but I cant find a commit. I have no problem with him, but if we would like to have a correct status than this is a failure, isnt it? BTW I just checked the commons-dev commit messages, so maybe I missed something. --- Mario - 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: [VOTE] Release commons math 1.1
Thanks Martin! And thanks for the reminder. Here is my +1 Phil On 12/5/05, Martin van den Bemt [EMAIL PROTECTED] wrote: +1 Although I am not the best judge of the Math component, everything looks pretty much complete (eg lot of tests, all tests pass) and I am very impressed with the message zarro bugs in bugzilla :) And another note : don't forget to vote yourself Phil :) Mvgr, Martin Phil Steitz wrote: There have been no problems reported with math 1.1 RC4, other than some small javadoc fixes, which have been applied to the release branch. Assuming a positive vote, I will cut a new signed release, including these fixes. Release notes are here: http://people.apache.org/~psteitz/commons-math/1-1-rc4/RELEASE-NOTES.txt And apidocs: http://people.apache.org/~psteitz/commons-math/1-1-rc4/apidocs/ The RC4 jar (commons-math-1.1-RC4.jar) has also been deployed to the apache internal maven repository at cvs.apache.org/repository Votes, please. The vote will close in 72 hours. Thanks in advance! Phil --- [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons --- - 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]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
Dennis Lundberg wrote: If commons component A extends the project.xml file from commons-build these dependencies are transfered to that component, meaning that component A doesn't have to worry about dependencies for site generation. However, if commons component B does *not* extend the project.xml file from commons-build these dependencies will have to be repeated in the project.xml file for component B. Hopefully these dependencies would not change all that often, meaning that little work would have to be done in order to keep this working, once it has been set up properly. Either way I think there is a big win including these dependencies in commons-build and all commons components. What do you think? This sounds great. Would have made my tasks this weekend much easier. However, I'm a bit behind the maven curve here. Could you please explain what the extends mechanism is for POMs? How would I tell if the project I'm working on extends commons-build or not? Thanks, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
Thanks for your help figuring out what the options are, Dennis. See comments interspersed. On 12/5/05, Dennis Lundberg [EMAIL PROTECTED] wrote: Phil Steitz wrote: On 12/4/05, Brett Porter [EMAIL PROTECTED] wrote: Dennis Lundberg wrote: Brett said that this *should* work, so I decided to try it myself. I received the same results as you did Phil, regarding maven --info, but I think I understand what is going on now. I have posted a question about this on the maven-users list to see if I can get some confirmation. Sorry this went over my head earlier, but Dennis' analysis on the usres list is correct. Maven --info doesn't reflect the difference as it reports what's installed. Plugin dependencies are only used for the life of the project's build, not installed. So the dependency should work regardless of what maven --info says. Is that the case? Then the solution to add the necessary dependencies to commons-build won't work and what we need to do is something like pluginUpdate (bunch of explicit plugin installs from the command line). Correct? No, as I will elaborate on further down, it will work nicely. I'll leave aside for a moment the discussion whether or not it's a good idea to extend project.xml from commons-build in other components. Setting up dependencies for a specific version of a Maven plugin, i.e. the xdoc and site plugins, works the way we want them to. I have tried this and it's easy to set it up. Here's what needs to be added in commons-build/project.xml for site generation: dependencies dependency groupIdmaven/groupId artifactIdmaven-site-plugin/artifactId version1.6.1/version typeplugin/type /dependency dependency groupIdmaven/groupId artifactIdmaven-xdoc-plugin/artifactId version1.9.2/version typeplugin/type /dependency /dependencies This will ensure that building the web site for commons-build will always use these versions of the plugins, regardless of what the user has installed on his or her system. So far all is good. Now on to the to extend or not extend discussion... So will only work for the main commons site, IIUC, which is not good enough. We need the individual sites to build without pain for RMs / maintainers. If just running a clean target in commons-build does not effectively update them, then above strategy will not work, unless you are talking about adding the dependencies to each individual POM, or reverting to extending commons-build, or I am not understanding something. If commons component A extends the project.xml file from commons-build these dependencies are transfered to that component, meaning that component A doesn't have to worry about dependencies for site generation. However, if commons component B does *not* extend the project.xml file from commons-build these dependencies will have to be repeated in the project.xml file for component B. Hopefully these dependencies would not change all that often, meaning that little work would have to be done in order to keep this working, once it has been set up properly. Either way I think there is a big win including these dependencies in commons-build and all commons components. What do you think? I don't much like the idea of adding dependencies to each of the individual POMs, but understand that this makes the dependency explicit, which is a good thing. So I guess I am +0 for this approach. Actually +1 as in will help if others agree we should go this route instead of the updatePlugins approach. I remain -1 on reverting to extending the commons-build POM because this makes individual releases depend on something not shipped (or even release managed) with them and forces users to have commons-build checked out to compile/jar under maven. I know we are still partially broken in this way now, as most projects require commons-build to be checked out for site generation. I view this as less of an issue, though, because we ship the docs with the releases. We should find a way to copy and adjust references to all of the required stuff as (automated, of course ;-) part of the dist build so the releases are 100% self-contained and can be reproduced fully from svn tags. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
On 12/5/05, Phil Steitz [EMAIL PROTECTED] wrote: Thanks for your help figuring out what the options are, Dennis. See comments interspersed. On 12/5/05, Dennis Lundberg [EMAIL PROTECTED] wrote: Phil Steitz wrote: On 12/4/05, Brett Porter [EMAIL PROTECTED] wrote: Dennis Lundberg wrote: Brett said that this *should* work, so I decided to try it myself. I received the same results as you did Phil, regarding maven --info, but I think I understand what is going on now. I have posted a question about this on the maven-users list to see if I can get some confirmation. Sorry this went over my head earlier, but Dennis' analysis on the usres list is correct. Maven --info doesn't reflect the difference as it reports what's installed. Plugin dependencies are only used for the life of the project's build, not installed. So the dependency should work regardless of what maven --info says. Is that the case? Then the solution to add the necessary dependencies to commons-build won't work and what we need to do is something like pluginUpdate (bunch of explicit plugin installs from the command line). Correct? No, as I will elaborate on further down, it will work nicely. I'll leave aside for a moment the discussion whether or not it's a good idea to extend project.xml from commons-build in other components. Setting up dependencies for a specific version of a Maven plugin, i.e. the xdoc and site plugins, works the way we want them to. I have tried this and it's easy to set it up. Here's what needs to be added in commons-build/project.xml for site generation: dependencies dependency groupIdmaven/groupId artifactIdmaven-site-plugin/artifactId version1.6.1/version typeplugin/type /dependency dependency groupIdmaven/groupId artifactIdmaven-xdoc-plugin/artifactId version1.9.2/version typeplugin/type /dependency /dependencies This will ensure that building the web site for commons-build will always use these versions of the plugins, regardless of what the user has installed on his or her system. So far all is good. Now on to the to extend or not extend discussion... So will only work for the main commons site, IIUC, which is not good enough. We need the individual sites to build without pain for RMs / maintainers. If just running a clean target in commons-build does not effectively update them, then above strategy will not work, unless you are talking about adding the dependencies to each individual POM, or reverting to extending commons-build, or I am not understanding something. If commons component A extends the project.xml file from commons-build these dependencies are transfered to that component, meaning that component A doesn't have to worry about dependencies for site generation. However, if commons component B does *not* extend the project.xml file from commons-build these dependencies will have to be repeated in the project.xml file for component B. Hopefully these dependencies would not change all that often, meaning that little work would have to be done in order to keep this working, once it has been set up properly. Either way I think there is a big win including these dependencies in commons-build and all commons components. What do you think? I don't much like the idea of adding dependencies to each of the individual POMs, but understand that this makes the dependency explicit, which is a good thing. So I guess I am +0 for this approach. Actually +1 as in will help if others agree we should go this route instead of the updatePlugins approach. I'm more than happy with the updatePlugins approach. It's KISS at its best. ;-) I remain -1 on reverting to extending the commons-build POM Ditto. -- Martin Cooper because this makes individual releases depend on something not shipped (or even release managed) with them and forces users to have commons-build checked out to compile/jar under maven. I know we are still partially broken in this way now, as most projects require commons-build to be checked out for site generation. I view this as less of an issue, though, because we ship the docs with the releases. We should find a way to copy and adjust references to all of the required stuff as (automated, of course ;-) part of the dist build so the releases are 100% self-contained and can be reproduced fully from svn tags. Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354131 - in /jakarta/commons/proper/vfs/trunk: build.xml project.properties project.xml
Author: imario
Date: Mon Dec 5 11:15:53 2005
New Revision: 354131
URL: http://svn.apache.org/viewcvs?rev=354131view=rev
Log:
RC7
Modified:
jakarta/commons/proper/vfs/trunk/build.xml
jakarta/commons/proper/vfs/trunk/project.properties
jakarta/commons/proper/vfs/trunk/project.xml
Modified: jakarta/commons/proper/vfs/trunk/build.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/build.xml?rev=354131r1=354130r2=354131view=diff
==
--- jakarta/commons/proper/vfs/trunk/build.xml (original)
+++ jakarta/commons/proper/vfs/trunk/build.xml Mon Dec 5 11:15:53 2005
@@ -1,6 +1,6 @@
?xml version=1.0 encoding=UTF-8?
-!--build.xml generated by maven from project.xml version 1.0-RC6
+!--build.xml generated by maven from project.xml version 1.0-RC7
on date August 13 2005, time 0731--
project default=jar name=commons-vfs basedir=.
@@ -20,7 +20,7 @@
/property
property name=javadocdir value=dist/docs/api
/property
-property name=final.name value=commons-vfs-1.0-RC6
+property name=final.name value=commons-vfs-1.0-RC7
/property
path id=build.classpath
fileset dir=${libdir}
@@ -150,7 +150,7 @@
/tstamp
property name=copyright value=Copyright amp;copy; The Apache
Software Foundation. All Rights Reserved.
/property
-property name=title value=Commons VFS 1.0-RC6 API
+property name=title value=Commons VFS 1.0-RC7 API
/property
javadoc use=true private=true destdir=${javadocdir}
author=true version=true sourcepath=src/java
packagenames=org.apache.commons.vfs.*
Modified: jakarta/commons/proper/vfs/trunk/project.properties
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/project.properties?rev=354131r1=354130r2=354131view=diff
==
--- jakarta/commons/proper/vfs/trunk/project.properties (original)
+++ jakarta/commons/proper/vfs/trunk/project.properties Mon Dec 5 11:15:53 2005
@@ -29,6 +29,7 @@
maven.repo.apache.snapshots.directory=/www/cvs.apache.org/repository
maven.junit.fork = true
maven.junit.sysproperties = test.basedir test.ftp.uri test.smb.uri
test.webdav.uri test.sftp.uri test.http.uri
+maven.junit.jvmargs = -Xss4096k
maven.test.failure.ignore=true
maven.ant.excludeTests=**/*.java
@@ -49,4 +50,4 @@
maven.checkstyle.properties = ${basedir}/checkstyle.properties
-maven.dist.src.assembly.dir=${maven.dist.assembly.dir}/src/${maven.final.name}-src
\ No newline at end of file
+maven.dist.src.assembly.dir=${maven.dist.assembly.dir}/src/${maven.final.name}-src
Modified: jakarta/commons/proper/vfs/trunk/project.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/project.xml?rev=354131r1=354130r2=354131view=diff
==
--- jakarta/commons/proper/vfs/trunk/project.xml (original)
+++ jakarta/commons/proper/vfs/trunk/project.xml Mon Dec 5 11:15:53 2005
@@ -6,7 +6,7 @@
idcommons-vfs/id
logo/images/vfs-logo-white.png/logo
urlhttp://jakarta.apache.org/commons/vfs//url
-currentVersion1.0-RC6/currentVersion
+currentVersion1.0-RC7/currentVersion
inceptionYear2002/inceptionYear
packageorg.apache.commons.vfs/package
shortDescriptionCommons VFS/shortDescription
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [email] MBoxMimeMessage
Will do, thanks James.
I need to rewrite the code to sit on top of [email] anyway.
Hen
On 12/5/05, James Carman [EMAIL PROTECTED] wrote:
Henri,
There's one problem with the code. You can't use a SimpleDateFormat in
multiple threads. They're not thread-safe (Date formats are not
synchronized. It is recommended to create separate format instances for each
thread. If multiple threads access a format concurrently, it must be
synchronized externally.). I actually fixed a bug in Tomcat where they
were doing the same thing. Just create a SimpleDateFormat every time you
need it.
James
-Original Message-
From: Martin van den Bemt [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 10:20 AM
To: Jakarta Commons Developers List
Subject: Re: [email] MBoxMimeMessage
Looks usefull..
+1 :)
Don't forget the software grant ;)
Mvgr,
Martin
Henri Yandell wrote:
I'd like to add the work in www.osjava.org's gj-mail to [email] if I may.
It's a small package with two classes that do the following things:
1) Mailer class for easy emailing.
2) Template style emailing; ${foo} etc.
3) MBoxMimeMessage
Now, 1) should be unnecessary, I assume [email] already does this. 2)
is unwanted, user's should use velocity or some other template engine.
3) is the bit I'd like to add.
It allows messages that look liks SMTP, or mbox emails, rather than
just containing the message. So the From:, To:, Subject: etc etc are
all in there. This makes for a much nicer time if someone is using a
template style system for emailing as the person modifying the
template can handle these issues instead of asking the coder.
Attachments are buggy, so I'd commit time to fixing these if the
MBoxMimeMessage looks attractive to the community. I'd
javadoc/unit-test obviously and would be able to kill gj-mail in
favour of [email].
Any interest?
Source can be seen at:
http://www.osjava.org/genjava/multiproject/gj-mail/xref/index.html
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]
-
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: r354134 - in /jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs: ./ impl/ provider/ provider/ftp/ provider/sftp/ provider/webdav/
Author: imario Date: Mon Dec 5 11:25:09 2005 New Revision: 354134 URL: http://svn.apache.org/viewcvs?rev=354134view=rev Log: javadoc fixes Modified: jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/RandomAccessContent.java jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/impl/DefaultFileSystemManager.java jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/FileNameParser.java jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/ftp/FtpFileSystemConfigBuilder.java jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/sftp/SftpFileSystemConfigBuilder.java jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/webdav/WebdavConnectionManager.java Modified: jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/RandomAccessContent.java URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/RandomAccessContent.java?rev=354134r1=354133r2=354134view=diff == --- jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/RandomAccessContent.java (original) +++ jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/RandomAccessContent.java Mon Dec 5 11:25:09 2005 @@ -80,7 +80,6 @@ * get the inputstream interface * br/ * bNotice: If you use [EMAIL PROTECTED] #seek(long)} you have to reget the InputStream/b - * @return */ public InputStream getInputStream() throws IOException; } Modified: jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/impl/DefaultFileSystemManager.java URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/impl/DefaultFileSystemManager.java?rev=354134r1=354133r2=354134view=diff == --- jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/impl/DefaultFileSystemManager.java (original) +++ jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/impl/DefaultFileSystemManager.java Mon Dec 5 11:25:09 2005 @@ -569,7 +569,6 @@ * @param base the base filename * @param name the name * @param scope the [EMAIL PROTECTED] NameScope} - * @return * @throws FileSystemException */ public FileName resolveName(final FileName base, Modified: jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/FileNameParser.java URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/FileNameParser.java?rev=354134r1=354133r2=354134view=diff == --- jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/FileNameParser.java (original) +++ jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/FileNameParser.java Mon Dec 5 11:25:09 2005 @@ -34,7 +34,6 @@ * parses a String into a filename * @param base * @param filename - * @return * @throws org.apache.commons.vfs.FileSystemException */ public FileName parseUri(final VfsComponentContext context, final FileName base, final String filename) throws FileSystemException; Modified: jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/ftp/FtpFileSystemConfigBuilder.java URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/ftp/FtpFileSystemConfigBuilder.java?rev=354134r1=354133r2=354134view=diff == --- jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/ftp/FtpFileSystemConfigBuilder.java (original) +++ jakarta/commons/proper/vfs/trunk/src/java/org/apache/commons/vfs/provider/ftp/FtpFileSystemConfigBuilder.java Mon Dec 5 11:25:09 2005 @@ -56,7 +56,6 @@ /** * @param opts - * @return * @see #setEntryParserFactory */ public FTPFileEntryParserFactory getEntryParserFactory(FileSystemOptions opts) @@ -80,7 +79,6 @@ /** * @param opts - * @return * @see #setEntryParser */ public String getEntryParser(FileSystemOptions opts) @@ -106,7 +104,6 @@ /** * @param opts - * @return * @see #setPassiveMode */ public Boolean getPassiveMode(FileSystemOptions opts) @@ -127,7 +124,6 @@ /** * @param opts - * @return * @see #setUserDirIsRoot */ public Boolean getUserDirIsRoot(FileSystemOptions opts) @@ -137,7 +133,6 @@ /** * @param opts - * @return * @see #setDataTimeout */ public Integer getDataTimeout(FileSystemOptions opts) Modified:
svn commit: r354148 - /jakarta/commons/proper/vfs/trunk/project.properties
Author: imario Date: Mon Dec 5 11:40:26 2005 New Revision: 354148 URL: http://svn.apache.org/viewcvs?rev=354148view=rev Log: increase ss - jdk 1.3 constantly (but not reproducable) dies during the tests - its a pain Modified: jakarta/commons/proper/vfs/trunk/project.properties Modified: jakarta/commons/proper/vfs/trunk/project.properties URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/project.properties?rev=354148r1=354147r2=354148view=diff == --- jakarta/commons/proper/vfs/trunk/project.properties (original) +++ jakarta/commons/proper/vfs/trunk/project.properties Mon Dec 5 11:40:26 2005 @@ -29,7 +29,7 @@ maven.repo.apache.snapshots.directory=/www/cvs.apache.org/repository maven.junit.fork = true maven.junit.sysproperties = test.basedir test.ftp.uri test.smb.uri test.webdav.uri test.sftp.uri test.http.uri -maven.junit.jvmargs = -Xss4096k +maven.junit.jvmargs = -Xss8192k maven.test.failure.ignore=true maven.ant.excludeTests=**/*.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-vfs (in module jakarta-commons) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-vfs has an issue affecting its community integration. This issue affects 72 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-chaperon : Java XML Framework - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-faces : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A jcr: protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-sample : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-vfs : Jakarta commons - excalibur-fortress-bean : Repository of reusable components. - excalibur-fortress-container-impl : Repository of reusable components. - excalibur-fortress-container-test : Repository of reusable components. - excalibur-fortress-examples : Repository of reusable components. - excalibur-fortress-migration : Repository of reusable components. - excalibur-fortress-platform : Repository of reusable components. - excalibur-fortress-testcase : Repository of reusable components. - excalibur-monitor : Repository of reusable components. - excalibur-sourceresolve : Repository of reusable components. - excalibur-xmlutil : Repository of reusable components. - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... - lenya : Content Management System - logging-log4j-chainsaw : Chainsaw log viewer Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-vfs-05122005.jar] identifier set to project name -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/gump_work/build_jakarta-commons_commons-vfs.html Work Name: build_jakarta-commons_commons-vfs (Type: Build) Work ended in a state of :
[EMAIL PROTECTED]: Project commons-vfs (in module jakarta-commons) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-vfs has an issue affecting its community integration. This issue affects 72 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-chaperon : Java XML Framework - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-faces : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A jcr: protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-mail : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-portal : Java XML Framework - cocoon-block-portal-sample : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-scratchpad : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-vfs : Jakarta commons - excalibur-fortress-bean : Repository of reusable components. - excalibur-fortress-container-impl : Repository of reusable components. - excalibur-fortress-container-test : Repository of reusable components. - excalibur-fortress-examples : Repository of reusable components. - excalibur-fortress-migration : Repository of reusable components. - excalibur-fortress-platform : Repository of reusable components. - excalibur-fortress-testcase : Repository of reusable components. - excalibur-monitor : Repository of reusable components. - excalibur-sourceresolve : Repository of reusable components. - excalibur-xmlutil : Repository of reusable components. - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... - lenya : Content Management System - logging-log4j-chainsaw : Chainsaw log viewer Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-vfs-05122005.jar] identifier set to project name -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons/commons-vfs/gump_work/build_jakarta-commons_commons-vfs.html Work Name: build_jakarta-commons_commons-vfs (Type: Build) Work ended in a state of :
Re: [all] Website changes (was Re: short critique of site)
On 12/5/05, Martin van den Bemt [EMAIL PROTECTED] wrote: Hi Mario, Sorry for not being there on sunday to finish of the commit :) - The current list of contributors are only committers. - The committers are collected from the project.xml (the developers section in maven), so a lot more inactive people out there are probably listed. - Just the list of committers is generated. The current contributor page is split up in 2 parts : top and bottom. The emuritus committers are at the bottom. - I let maven glue the top, list of committers and bottom together. - You end up with a generated contributors.xml in the xdocs directory. - The generation is currently hooked into the commons-site-generate goal. - The generation itself happens in the commons-contributors-page-generate goal. A choices need to be made before commit : Do we want to generate the committers from the commons-site-generate goal ? or Do we want to generate this on demand by calling a specific goal (I'll rename the goal to something more friendly). or Make both possible ? I agree with Martin C that it will be more likely kept up to date if it is automatic. (I am currently reusing the list of loaded poms that the reactor stores in a variable) Will this require that to gen the commons site you will need to have trunks-proper checked out with the standard directory layout? I am OK with this personally, just wondering if it could ever cause problems. Also, one would need to have all svn upped to be correct. Or are you doing something clever with the scm plugin to just grab the POMS at gen time? Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354152 - in /jakarta/commons/proper/vfs/trunk: build.xml maven.xml
Author: imario
Date: Mon Dec 5 12:06:01 2005
New Revision: 354152
URL: http://svn.apache.org/viewcvs?rev=354152view=rev
Log:
add: xdocs in src distribution
fix: removed empty setproxy from build.xml
Modified:
jakarta/commons/proper/vfs/trunk/build.xml
jakarta/commons/proper/vfs/trunk/maven.xml
Modified: jakarta/commons/proper/vfs/trunk/build.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/build.xml?rev=354152r1=354151r2=354152view=diff
==
--- jakarta/commons/proper/vfs/trunk/build.xml (original)
+++ jakarta/commons/proper/vfs/trunk/build.xml Mon Dec 5 12:06:01 2005
@@ -163,8 +163,6 @@
target name=get-deps unless=noget depends=init
!--Proxy settings works only with a JDK 1.2 and higher.--
-setproxy
-/setproxy
get dest=${libdir}/ant-1.6.2.jar usetimestamp=true
ignoreerrors=true
src=http://www.ibiblio.org/maven/ant/jars/ant-1.6.2.jar;
/get
Modified: jakarta/commons/proper/vfs/trunk/maven.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/maven.xml?rev=354152r1=354151r2=354152view=diff
==
--- jakarta/commons/proper/vfs/trunk/maven.xml (original)
+++ jakarta/commons/proper/vfs/trunk/maven.xml Mon Dec 5 12:06:01 2005
@@ -69,6 +69,12 @@
fileset file='${basedir}/RELEASE_NOTES.txt'/
fileset file='${basedir}/NOTICE.txt'/
/copy
+
+!-- Copy XDocs --
+copy todir=${maven.dist.src.assembly.dir}/xdocs
+ fileset dir='${basedir}/xdocs' /
+/copy
+
/preGoal
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354153 - /jakarta/commons/proper/vfs/tags/vfs-1.0-RC7/
Author: imario Date: Mon Dec 5 12:06:36 2005 New Revision: 354153 URL: http://svn.apache.org/viewcvs?rev=354153view=rev Log: RC7 Added: jakarta/commons/proper/vfs/tags/vfs-1.0-RC7/ - copied from r354152, jakarta/commons/proper/vfs/trunk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[scxml] removing superstep, etc.
I've developed a version of SCXML that matches the spec's semantics more closely (no superstep, single event queue, internal and external events treated identically, etc.) I am not going to check it in right away, however, for two reasons: 1. I couldn't keep the changes local to the semantics component. In particular I had to change SCXMLExecutor significantly (including making it support the Runnable interface.) 2. This is my first time programming in Java so I'm sure I messed things up. Maybe we could set up a phone call to discuss how to merge the changes without breaking existing applications. We also need to discuss how to make other changes needed to get in synch with the upcoming release of the spec. And in any case, I would like someone to review my code before it gets checked in. - Jim
svn commit: r354155 - in /jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient: ./ auth/ methods/multipart/ params/ util/
Author: olegk
Date: Mon Dec 5 12:18:10 2005
New Revision: 354155
URL: http://svn.apache.org/viewcvs?rev=354155view=rev
Log:
PR #37616 (Findbugs reports and fixes)
Fixes for problems discovered by running findbugs 0.94.rc1 on HttpClient 3.0rc4
Submitted by Sebb sebb at apache.org
Reviewed by Oleg Kalnichevski Michael Becke
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HostConfiguration.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HttpClient.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/ProxyClient.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/StatusLine.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/auth/AuthScope.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/auth/DigestScheme.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/methods/multipart/FilePart.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/params/DefaultHttpParamsFactory.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/params/HttpClientParams.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/params/HttpConnectionManagerParams.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/params/HttpMethodParams.java
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/util/LangUtils.java
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HostConfiguration.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HostConfiguration.java?rev=354155r1=354154r2=354155view=diff
==
---
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HostConfiguration.java
(original)
+++
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HostConfiguration.java
Mon Dec 5 12:18:10 2005
@@ -503,7 +503,7 @@
/**
* @see java.lang.Object#hashCode()
*/
-public int hashCode() {
+public synchronized int hashCode() {
int hash = LangUtils.HASH_SEED;
hash = LangUtils.hashCode(hash, this.host);
hash = LangUtils.hashCode(hash, this.proxyHost);
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HttpClient.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HttpClient.java?rev=354155r1=354154r2=354155view=diff
==
---
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HttpClient.java
(original)
+++
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/HttpClient.java
Mon Dec 5 12:18:10 2005
@@ -389,7 +389,7 @@
}
HttpMethodDirector methodDirector = new HttpMethodDirector(
-this.httpConnectionManager,
+getHttpConnectionManager(),
hostconfig,
this.params,
(state == null ? getState() : state));
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/ProxyClient.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/ProxyClient.java?rev=354155r1=354154r2=354155view=diff
==
---
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/ProxyClient.java
(original)
+++
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/ProxyClient.java
Mon Dec 5 12:18:10 2005
@@ -261,7 +261,7 @@
/**
* A connection manager that creates a single connection. Meant to be
used only once.
*/
-class DummyConnectionManager implements HttpConnectionManager {
+static class DummyConnectionManager implements HttpConnectionManager {
private HttpConnection httpConnection;
Modified:
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/StatusLine.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/StatusLine.java?rev=354155r1=354154r2=354155view=diff
==
---
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/StatusLine.java
(original)
+++
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/StatusLine.java
Mon Dec 5
[ANNOUNCE][VFS] commons-vfs 1.0 RC7 available
Hi! The commons vfs community is happy to announce the availability of commons-vfs 1.0 RC7. Please find the RC at http://people.apache.org/~imario/vfs The site can be reviewed at http://people.apache.org/~imario/vfs-1.0-RC7/site *) upgrade to commons-net 1.4.1 *) use of jdk1.3 compiler to build this release *) some fixes to be release conform --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vfs][REVOTE] release version 1.0
Hi! Even if the last vode passed I decided to restart the voting based on RC7. RC7 is now using commons-net 1.4.1 and built using the jdk1.3 compiler also some rearrangements have taken place to accommodate to our guidlines (e.g. include xdocs into src distribution) As previously posted please find the RC7 at http://people.apache.org/~imario/vfs Please vote: [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons Sorry if this revote bothers you, but after all what happens in the last days on our mailinglist I thought if would be better to do so. Thanks! Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 37690] - RandomStringUtils.random() family of methods create invalid unicode sequences
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37690.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37690
--- Additional Comments From [EMAIL PROTECTED] 2005-12-05 21:35 ---
Sorry, have never added a unit test patch.
Here is a junit test case showing the problem.
/**
* Creates a human readable representation of any unicode character.
* @param c - a unicode character
* @return human readable representation for c
*/
static public String makeStringFromChar(char c)
{
// dirty for getting the char code from a character
return Integer.toHexString((new Character(c)).hashCode());
}
/**
* Checks if the string got by [EMAIL PROTECTED]
RandomStringUtils#random(int)}
* can be converted to UTF-8 and back without loss.
*
* @author [EMAIL PROTECTED]
* @throws Exception
*/
public void testRandom() throws Exception
{
final int size = 5000;
final String encoding = UTF-8;
final String orig = RandomStringUtils.random(size);
final byte[] bytes = orig.getBytes(encoding);
final String copy = new String(bytes, encoding);
// for a verbose compare:
for (int i=0; iorig.length() icopy.length(); ++i)
{
char o = orig.charAt(i);
char c = copy.charAt(i);
assertEquals(differs at + i + ( +
makeStringFromChar(o) + , +
makeStringFromChar(c) + ), o, c);
}
// compare length also
assertEquals(orig.length(), copy.length());
// just to be complete
assertEquals(orig, copy);
}
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Maven, help or hinderance?
Torsten Curdt wrote: On 04.12.2005, at 02:17, Stephen Colebourne wrote: Hate to be an old fart here but was ant really all that bad? Oh ...please don't! ;-) All I have to say: dependency management plus the reports are just enough for me to never want to switch back to ant again. Even from m1! Worst case I was always able to come up with some non-standard goals-magic to do what I wanted. Its clear that many here like maven enough to want to keep it. Personally, it drives me up the wall. For example, ATM, I am trying to use clirr with maven. I've had it working before, but now it deosn't. It tries to download the jar even though its in the local repository, and thus fails. There is no rhyme nor reason about why it fails now when I've had it work previously. I've already wasted an hour on it, so now I shall just do what I always do - run ant instead. At least there seems to be some discussion about trying to simplify life here at commons. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs][REVOTE] release version 1.0
What is the cause of the current GUMP test failure?? Stephen Mario Ivankovits wrote: Hi! Even if the last vode passed I decided to restart the voting based on RC7. RC7 is now using commons-net 1.4.1 and built using the jdk1.3 compiler also some rearrangements have taken place to accommodate to our guidlines (e.g. include xdocs into src distribution) As previously posted please find the RC7 at http://people.apache.org/~imario/vfs Please vote: [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons Sorry if this revote bothers you, but after all what happens in the last days on our mailinglist I thought if would be better to do so. Thanks! Mario - 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: svn commit: r354018 - /jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Is it possible that this change broke a unit test? I get now the
following failures in TestDataConfiguration:
Testsuite: org.apache.commons.configuration.TestDataConfiguration
Tests run: 34, Failures: 3, Errors: 0, Time elapsed: 1,832 sec
Testcase:
testGetColor(org.apache.commons.configuration.TestDataConfiguration):
FAILED
color expected:java.awt.Color[r=255,g=0,b=0] but
was:java.awt.Color[r=255,g=240,b=0]
junit.framework.AssertionFailedError: color
expected:java.awt.Color[r=255,g=0,b=0] but
was:java.awt.Color[r=255,g=240,b=0]
at
org.apache.commons.configuration.TestDataConfiguration.testGetColor(TestDataConfiguration.java:1169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Testcase:
testGetColorArray(org.apache.commons.configuration.TestDataConfiguration):
FAILED
[position 0] expected:java.awt.Color[r=255,g=0,b=0] but
was:java.awt.Color[r=255,g=240,b=0]
junit.framework.AssertionFailedError: [position 0]
expected:java.awt.Color[r=255,g=0,b=0] but
was:java.awt.Color[r=255,g=240,b=0]
at junitx.framework.ArrayAssert.assertEquals(ArrayAssert.java:103)
at junitx.framework.ArrayAssert.assertEquals(ArrayAssert.java:113)
at
org.apache.commons.configuration.TestDataConfiguration.testGetColorArray(TestDataConfiguration.java:1197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Testcase:
testGetColorList(org.apache.commons.configuration.TestDataConfiguration):
FAILED
expecting java.awt.Color[r=255,g=0,b=0] in
java.awt.Color[r=255,g=240,b=0], java.awt.Color[r=0,g=0,b=0]
junit.framework.AssertionFailedError: expecting
java.awt.Color[r=255,g=0,b=0] in java.awt.Color[r=255,g=240,b=0],
java.awt.Color[r=0,g=0,b=0]
at junitx.framework.ListAssert.failNotContains(ListAssert.java:133)
at junitx.framework.ListAssert.assertContains(ListAssert.java:118)
at junitx.framework.ListAssert.assertEquals(ListAssert.java:91)
at junitx.framework.ListAssert.assertEquals(ListAssert.java:78)
at
org.apache.commons.configuration.TestDataConfiguration.testGetColorList(TestDataConfiguration.java:1232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Can you please check again?
Thanks
Oliver
[EMAIL PROTECTED] wrote:
Author: ebourg
Date: Mon Dec 5 00:23:00 2005
New Revision: 354018
URL: http://svn.apache.org/viewcvs?rev=354018view=rev
Log:
Reduced the usage of 'magic numbers' for checkstyle
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java?rev=354018r1=354017r2=354018view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Mon Dec 5 00:23:00 2005
@@ -538,18 +538,20 @@
color = color.substring(1);
}
-int red = Integer.parseInt(color.substring(0, 2), 16);
-int green = Integer.parseInt(color.substring(2, 4), 16);
-int blue = Integer.parseInt(color.substring(4, 6), 16);
+int[] components = new int[3];
+for (int i = 0; i components.length; i++) {
+components[i] = Integer.parseInt(color.substring(i, i +
2), HEX_RADIX);
+}
+
int alpha = 255;
// parse the transparency
if (color.length() = 8)
{
-alpha = Integer.parseInt(color.substring(6, 8), 16);
+alpha = Integer.parseInt(color.substring(6, 8),
HEX_RADIX);
}
-return new Color(red, green, blue, alpha);
+return new Color(components[0], components[1], components[2],
alpha);
}
catch (Exception e)
{
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[all] Sharing maven setup [was Re: HELP!]
I don't much like the idea of adding dependencies to each of the individual POMs, but understand that this makes the dependency explicit, which is a good thing. So I guess I am +0 for this approach. Actually +1 as in will help if others agree we should go this route instead of the updatePlugins approach. I'm more than happy with the updatePlugins approach. It's KISS at its best. ;-) I remain -1 on reverting to extending the commons-build POM I agree that we should not extend the commons-build POM. However we could do with a way to share stuff. I have in my mind that what we need is a commons maven plugin. It would: - create target/commons - download commons-build within target/commons - update the local maven installation - merge the latest mandatory POM settings - merge the latest mandatory POM properties - merge the latest mandatory xdocs Thus, to push a site or release out you do: maven commons then any other command: maven ... This is probably a pipedream though, as I doubt anyone has the time to write this (ie. I don't!) Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs][REVOTE] release version 1.0
Stephen Colebourne wrote: What is the cause of the current GUMP test failure?? ClassNotFoundException of one of our test classes. internal-test: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/vfs/target/test-reports [junit] Running org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] Testsuite: org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Caused an ERROR [junit] org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] java.lang.ClassNotFoundException: org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:199) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:187) Using maven locally works like a charme. --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Sharing maven setup [was Re: HELP!]
On 12/5/05, Stephen Colebourne [EMAIL PROTECTED] wrote: I don't much like the idea of adding dependencies to each of the individual POMs, but understand that this makes the dependency explicit, which is a good thing. So I guess I am +0 for this approach. Actually +1 as in will help if others agree we should go this route instead of the updatePlugins approach. I'm more than happy with the updatePlugins approach. It's KISS at its best. ;-) I remain -1 on reverting to extending the commons-build POM I agree that we should not extend the commons-build POM. However we could do with a way to share stuff. I have in my mind that what we need is a commons maven plugin. It would: +1 I was thinking the exact same thing. Maybe we can find some time to hack on it at the ApacheCon. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release commons math 1.1
Looks good (now that I made some experience with checking RCs on my own ;-) The only thing I find a bit strange is that the manifest says the jar was built with JDK 1.4.2_08 while the minimum required JDK seems to be 1.3 (stated in section 0.5 of the user guide). Is this okay? Then I am +1. Oliver Phil Steitz wrote: There have been no problems reported with math 1.1 RC4, other than some small javadoc fixes, which have been applied to the release branch. Assuming a positive vote, I will cut a new signed release, including these fixes. Release notes are here: http://people.apache.org/~psteitz/commons-math/1-1-rc4/RELEASE-NOTES.txt And apidocs: http://people.apache.org/~psteitz/commons-math/1-1-rc4/apidocs/ The RC4 jar (commons-math-1.1-RC4.jar) has also been deployed to the apache internal maven repository at cvs.apache.org/repository Votes, please. The vote will close in 72 hours. Thanks in advance! Phil --- [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Maven, help or hinderance?
On 12/5/05, Stephen Colebourne [EMAIL PROTECTED] wrote: All I have to say: dependency management plus the reports are just enough for me to never want to switch back to ant again. Even from m1! Worst case I was always able to come up with some non-standard goals-magic to do what I wanted. Its clear that many here like maven enough to want to keep it. Personally, it drives me up the wall. For example, ATM, I am trying to use clirr with maven. I've had it working before, but now it deosn't. It tries to download the jar even though its in the local repository, and thus fails. There is no rhyme nor reason about why it fails now when I've had it work previously. I've already wasted an hour on it, so now I shall just do what I always do - run ant instead. At least there seems to be some discussion about trying to simplify life here at commons. Mhm, that makes me wonder whether Ant + Ivy (for dependencies) wouldn't be a better (simpler) choice, or perhaps Maven 2 (havn't used it yet). Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Sharing maven setup [was Re: HELP!]
I have in my mind that what we need is a commons maven plugin. It would: +1 I was thinking the exact same thing. Same here :-) cheers -- Torsten PGP.sig Description: This is a digitally signed message part
svn commit: r354192 - /jakarta/commons/trunks-sandbox/
Author: brett Date: Mon Dec 5 13:20:41 2005 New Revision: 354192 URL: http://svn.apache.org/viewcvs?rev=354192view=rev Log: add openpgp to externals Modified: jakarta/commons/trunks-sandbox/ (props changed) Propchange: jakarta/commons/trunks-sandbox/ -- --- svn:externals (original) +++ svn:externals Mon Dec 5 13:20:41 2005 @@ -7,6 +7,7 @@ id https://svn.apache.org/repos/asf/jakarta/commons/sandbox/id/trunk javaflow https://svn.apache.org/repos/asf/jakarta/commons/sandbox/javaflow/trunk jci https://svn.apache.org/repos/asf/jakarta/commons/sandbox/jci/trunk +openpgp https://svn.apache.org/repos/asf/jakarta/commons/sandbox/openpgp/trunk pipeline https://svn.apache.org/repos/asf/jakarta/commons/sandbox/pipeline/trunk proxy https://svn.apache.org/repos/asf/jakarta/commons/sandbox/proxy/trunk scxml https://svn.apache.org/repos/asf/jakarta/commons/sandbox/scxml/trunk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
[EMAIL PROTECTED] wrote: Dennis Lundberg wrote: If commons component A extends the project.xml file from commons-build these dependencies are transfered to that component, meaning that component A doesn't have to worry about dependencies for site generation. However, if commons component B does *not* extend the project.xml file from commons-build these dependencies will have to be repeated in the project.xml file for component B. Hopefully these dependencies would not change all that often, meaning that little work would have to be done in order to keep this working, once it has been set up properly. Either way I think there is a big win including these dependencies in commons-build and all commons components. What do you think? This sounds great. Would have made my tasks this weekend much easier. However, I'm a bit behind the maven curve here. Could you please explain what the extends mechanism is for POMs? How would I tell if the project I'm working on extends commons-build or not? Maven's POM extends works pretty much like extends in Java. Define stuff you want to reuse in the parent and then use in the child. If you don't like what's in the parent just override it in the child. You can tell if your component is extending commons-build by looking at the top of your component's POM. If you find this line there: extend../commons-build/project.xml/extend then it's extending commons-build. A quick look in my, just updated, SVN checkout of commons-proper shows that only commons-attributes and commons-chain are extending commons-build. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commons-concoct - new project proposal
Thank you very much Henri. I'm starting a new thread for greater visibility (took some marketing lessons this summer :) Henri Yandell wrote: Giorgio's propsal/code in zip form are uploaded to: http://people.apache.org/~bayard/commons-concoct.zip On 12/1/05, Henri Yandell [EMAIL PROTECTED] wrote: On 12/1/05, Giorgio Gallo [EMAIL PROTECTED] wrote: I've read trough the charter and will post a formal proposal as soon as I get the time to write it down ;) In the meantime, is there anyway I could upload the code (its around 60k, zipped), in a quest for initial committers to include on the proposal? Either attach it to a bugzilla entry, or mail it to me and I'll put it in my ~ space As regards incubation: - The code have never been released, whether on its own or inside a larger application/library - I'm the sole copyright owner of the code - I am (of course) willing to donate it to ASF Does this imply it needs to be incubated? Depends on the people interested. If there are no/few existing committers interested, then yes you'd need to be incubated. If however the majority of interested committers are existing committers, then we'll go with a code grant and goto the sandbox. 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: [all] Sharing maven setup [was Re: HELP!]
Stephen Colebourne wrote: I don't much like the idea of adding dependencies to each of the individual POMs, but understand that this makes the dependency explicit, which is a good thing. So I guess I am +0 for this approach. Actually +1 as in will help if others agree we should go this route instead of the updatePlugins approach. I'm more than happy with the updatePlugins approach. It's KISS at its best. ;-) I remain -1 on reverting to extending the commons-build POM I agree that we should not extend the commons-build POM. However we could do with a way to share stuff. I have in my mind that what we need is a commons maven plugin. It would: - create target/commons - download commons-build within target/commons - update the local maven installation - merge the latest mandatory POM settings - merge the latest mandatory POM properties - merge the latest mandatory xdocs Thus, to push a site or release out you do: maven commons then any other command: maven ... This is probably a pipedream though, as I doubt anyone has the time to write this (ie. I don't!) Yes, of course! A plugin is the way to go. Most people seems to agree that extending commons-build is a bad thing, so we need to figure out a way to make each commons component self-supporting. Imagine this directory structure in the commons component of your choice: / +- commons-component/ +- site/ | +- menus/ | | +- ... | +- parts/ | | +- ... | +- commons-site.jsl | +- cvsusage.xml | +- ... +- project.properties +- project.xml +- project-parent.xml First we make sure that every commons-component extends the *local* project-parent.xml, see directory-structure above. This would be a one-time job. If we then create a plugin that does the following, it might just work: - Download commons-build/project-parent.xml via anonymous SVN to commons-component/project-parent.xml - We would probably need to do something similar for project.properties, I'm not sure how that would work though - Download commons-build/site/menus/ , commons-build/site/parts/ et al via anonymous SVN to commons-component/site/ This way we don't have to think about merging xml documents and other fancy stuff - just download some files from SVN. Does this sound at all possible? Should I have go at it? I have not made a plugin before, but there's a first time for everything... -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
commons-concoct: proposal draft and search for supporters
Hi all! As you might know, Henri has been so gentle as to upload the (wannabe) commons-concoct into his ~ space: http://people.apache.org/~bayard/commons-concoct.zip Inside the .zip file you'll find the current project (maven2-enabled and, well, it's more of a prototype than a full-fledged component right now:) as well as a draft of the proposal I wish to post in a few days. Please take a look at the proposal draft and comment on it: I'm not very sure my english is good enough to convey the vision of a new project. -- Giorgio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commons-concoct - new project proposal
I have tried the http DL, as well as trying to check the file out locally via ssh to people@ and I continue to get errors indicating bad file format, etc... Thanks, Matt --- Henri Yandell [EMAIL PROTECTED] wrote: Giorgio's propsal/code in zip form are uploaded to: http://people.apache.org/~bayard/commons-concoct.zip On 12/1/05, Henri Yandell [EMAIL PROTECTED] wrote: On 12/1/05, Giorgio Gallo [EMAIL PROTECTED] wrote: I've read trough the charter and will post a formal proposal as soon as I get the time to write it down ;) In the meantime, is there anyway I could upload the code (its around 60k, zipped), in a quest for initial committers to include on the proposal? Either attach it to a bugzilla entry, or mail it to me and I'll put it in my ~ space As regards incubation: - The code have never been released, whether on its own or inside a larger application/library - I'm the sole copyright owner of the code - I am (of course) willing to donate it to ASF Does this imply it needs to be incubated? Depends on the people interested. If there are no/few existing committers interested, then yes you'd need to be incubated. If however the majority of interested committers are existing committers, then we'll go with a code grant and goto the sandbox. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs][REVOTE] release version 1.0
Does this mean we need to re-gen the ant build file? On 12/6/05, Mario Ivankovits [EMAIL PROTECTED] wrote: Stephen Colebourne wrote: What is the cause of the current GUMP test failure?? ClassNotFoundException of one of our test classes. internal-test: [mkdir] Created dir: /x1/gump/public/workspace/jakarta-commons/vfs/target/test-reports [junit] Running org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] Testsuite: org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec [junit] Caused an ERROR [junit] org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] java.lang.ClassNotFoundException: org.apache.commons.vfs.provider.ftp.test.FtpProviderTestCase [junit] at java.net.URLClassLoader$1.run(URLClassLoader.java:199) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at java.net.URLClassLoader.findClass(URLClassLoader.java:187) Using maven locally works like a charme. --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live. - George Bernard Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commons-concoct - new project proposal
That's most strange: I downloaded it successfully with Firefox... Please ask me and I'll send it to you by email. Matt Benson wrote: I have tried the http DL, as well as trying to check the file out locally via ssh to people@ and I continue to get errors indicating bad file format, etc... Thanks, Matt --- Henri Yandell [EMAIL PROTECTED] wrote: Giorgio's propsal/code in zip form are uploaded to: http://people.apache.org/~bayard/commons-concoct.zip snip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE][VFS] commons-vfs 1.0 RC7 available
The site link below 404's. On 12/6/05, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! The commons vfs community is happy to announce the availability of commons-vfs 1.0 RC7. Please find the RC at http://people.apache.org/~imario/vfs The site can be reviewed at http://people.apache.org/~imario/vfs-1.0-RC7/site *) upgrade to commons-net 1.4.1 *) use of jdk1.3 compiler to build this release *) some fixes to be release conform --- Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live. - George Bernard Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commons-concoct - new project proposal
ah, never mind. Must've been some WinZip-specific stuff. I tried to open w/ XP and jar, but 7-zip did the trick. ;) -Matt --- Giorgio Gallo [EMAIL PROTECTED] wrote: That's most strange: I downloaded it successfully with Firefox... Please ask me and I'll send it to you by email. Matt Benson wrote: I have tried the http DL, as well as trying to check the file out locally via ssh to people@ and I continue to get errors indicating bad file format, etc... Thanks, Matt --- Henri Yandell [EMAIL PROTECTED] wrote: Giorgio's propsal/code in zip form are uploaded to: http://people.apache.org/~bayard/commons-concoct.zip snip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release commons math 1.1
+0 Phil Steitz wrote: There have been no problems reported with math 1.1 RC4, other than some small javadoc fixes, which have been applied to the release branch. Assuming a positive vote, I will cut a new signed release, including these fixes. Release notes are here: http://people.apache.org/~psteitz/commons-math/1-1-rc4/RELEASE-NOTES.txt And apidocs: http://people.apache.org/~psteitz/commons-math/1-1-rc4/apidocs/ The RC4 jar (commons-math-1.1-RC4.jar) has also been deployed to the apache internal maven repository at cvs.apache.org/repository Votes, please. The vote will close in 72 hours. Thanks in advance! Phil --- [ ] +1 I support this release and am willing to help [ ] +0 I support this release but am unable to help [ ] -0 I do not support this release [ ] -1 I do not support this release, and here are my reasons --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.kimvdlinde.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 37574] - [lang] [PATCH] new ExceptionUtils.setCause() method
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=37574. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37574 --- Additional Comments From [EMAIL PROTECTED] 2005-12-06 01:19 --- I'll try to take a look this week. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354251 - /jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Author: ebourg
Date: Mon Dec 5 17:13:13 2005
New Revision: 354251
URL: http://svn.apache.org/viewcvs?rev=354251view=rev
Log:
Fixed the error introduced with the new loop parsing the color components
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java?rev=354251r1=354250r2=354251view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Mon Dec 5 17:13:13 2005
@@ -540,7 +540,7 @@
int[] components = new int[3];
for (int i = 0; i components.length; i++) {
-components[i] = Integer.parseInt(color.substring(i, i +
2), HEX_RADIX);
+components[i] = Integer.parseInt(color.substring(2 * i, 2
* i + 2), HEX_RADIX);
}
int alpha = 255;
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r354018 - /jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
Oliver Heger wrote: Is it possible that this change broke a unit test? I get now the following failures in TestDataConfiguration: Testsuite: org.apache.commons.configuration.TestDataConfiguration Tests run: 34, Failures: 3, Errors: 0, Time elapsed: 1,832 sec My bad sorry, I fixed it. Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
LGPL compatibility
Quick question... if one were to write a library that eventually became a Commons project, or part of an existing Commons project, which depended on another non-Apache library release under an LGPL license, would that be compatible in terms of including the LGPL'd library in the Commons component? I'm thinking there is three options, and only the last one do I know would be compatible... (1) The LGPL'd library, or some subset of it more likely, becoming part of the Commons codebase, leaving all applicable copyright notices and such in place and otherwise adhearing to the requirements of the LGPL (2) The LGPL'd library simply being included in the Commons download in its complete, unaltered form (3) Simply referencing the LGPL'd library as a dependency that people would have to go get themselves, and linking to a download page of course Like I said, I know #3 is safe, but what about the others? Thanks! -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LGPL compatibility
On 12/5/05, Frank W. Zammetti [EMAIL PROTECTED] wrote: Quick question... if one were to write a library that eventually became a Commons project, or part of an existing Commons project, which depended on another non-Apache library release under an LGPL license, would that be compatible in terms of including the LGPL'd library in the Commons component? I'm thinking there is three options, and only the last one do I know would be compatible... (1) The LGPL'd library, or some subset of it more likely, becoming part of the Commons codebase, leaving all applicable copyright notices and such in place and otherwise adhearing to the requirements of the LGPL (2) The LGPL'd library simply being included in the Commons download in its complete, unaltered form (3) Simply referencing the LGPL'd library as a dependency that people would have to go get themselves, and linking to a download page of course Like I said, I know #3 is safe, but what about the others? Thanks! Only #3 is viable. However, if the LGPL dependency was *required* by the Commons component (as opposed to being an optional add-on), then I personally would vote against such a thing, as it means the Commons component is not usable without bringing the LGPL code into the picture, rendering the Apache License on that component somewhat meaningless. -- Martin Cooper -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vfs][REVOTE] release version 1.0
On 12/5/05, Dion Gillard [EMAIL PROTECTED] wrote: Does this mean we need to re-gen the ant build file? On 12/6/05, Mario Ivankovits [EMAIL PROTECTED] wrote: Stephen Colebourne wrote: What is the cause of the current GUMP test failure?? It looks to me like the vfs tests were not being run until this change in the build,xml: http://tinyurl.com/da6tr From what I can see the exclude name=**/*.java would have prevented any tests being included and removing that is when the tests started failing. So in summary my guess is the tests never worked in gump. Looking at the gump config for vfs, I think the test classes dir is missing from the classpath, so I have added it. Hopefully that should sort out the ClassNotFound exception. I'll check it tommorrow, but if it doesn't, apologies in advance for interfering. Niall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354257 - /jakarta/commons/sandbox/scxml/trunk/project.xml
Author: rahul
Date: Mon Dec 5 17:46:52 2005
New Revision: 354257
URL: http://svn.apache.org/viewcvs?rev=354257view=rev
Log:
Add issueTrackingUrl to POM to fully eliminate commons-build POM inheritance
requirement
Modified:
jakarta/commons/sandbox/scxml/trunk/project.xml
Modified: jakarta/commons/sandbox/scxml/trunk/project.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/project.xml?rev=354257r1=354256r2=354257view=diff
==
--- jakarta/commons/sandbox/scxml/trunk/project.xml (original)
+++ jakarta/commons/sandbox/scxml/trunk/project.xml Mon Dec 5 17:46:52 2005
@@ -45,6 +45,7 @@
siteAddressjakarta.apache.org/siteAddress
siteDirectory/www/jakarta.apache.org/commons/sandbox/${pom.artifactId.substring(8)}//siteDirectory
+ issueTrackingUrlhttp://issues.apache.org/bugzilla//issueTrackingUrl
distributionDirectory/www/jakarta.apache.org/builds/jakarta-commons/${pom.artifactId.substring(8)}//distributionDirectory
repository
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [scxml] removing superstep, etc.
On 12/5/05, Barnett, James [EMAIL PROTECTED] wrote: I've developed a version of SCXML that matches the spec's semantics more closely (no superstep, single event queue, internal and external events treated identically, etc.) snip/ This is great, thanks. I am not going to check it in right away, however, for two reasons: 1. I couldn't keep the changes local to the semantics component. In particular I had to change SCXMLExecutor significantly (including making it support the Runnable interface.) 2. This is my first time programming in Java so I'm sure I messed things up. Maybe we could set up a phone call to discuss how to merge the changes without breaking existing applications. We also need to discuss how to make other changes needed to get in synch with the upcoming release of the spec. And in any case, I would like someone to review my code before it gets checked in. snap/ When you get a chance, please attach a patch to a bugzilla ticket, and we'll be glad to take a look at it. Bugzilla is here [1]. Some information related to filing tickets in bugzilla, specific to SCXML, is here [2]. -Rahul [1] http://issues.apache.org/bugzilla/ [2] http://jakarta.apache.org/commons/sandbox/scxml/issue-tracking.html - Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LGPL compatibility
Martin Cooper wrote: Only #3 is viable. However, if the LGPL dependency was *required* by the Commons component (as opposed to being an optional add-on), then I personally would vote against such a thing, as it means the Commons component is not usable without bringing the LGPL code into the picture, rendering the Apache License on that component somewhat meaningless. Fair enough. Thanks Martin, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
Phil Steitz wrote: snip Thanks for all your help. These last suggestions worked. I built the site, tested my changes, then pushed the site. I DON'T have my key set up. where do I do this, it's a pain to keep typing in my password, but doable. As indicated on the building page, you should follow the instructions on the bottom of this page: http://www.apache.org/dev/cvs-on-unix.html Right, I'd had this set up before. What I'd forgotten was I'd joined another site that required protocol 2, and my config was set up that way. But I'd only stored my protocol 1 key on apache. Logging on via ssh -1 works. Does apache accept protocol 2 ssh keys? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
On 12/5/05, Steve Cohen [EMAIL PROTECTED] wrote: snip/ Logging on via ssh -1 works. Does apache accept protocol 2 ssh keys? snap/ Atleast the RSA one, AFAICT. -Rahul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354264 - in /jakarta/commons/proper/configuration/trunk: ./ conf/ src/java/org/apache/commons/configuration/ src/java/org/apache/commons/configuration/plist/
Author: ebourg
Date: Mon Dec 5 19:10:27 2005
New Revision: 354264
URL: http://svn.apache.org/viewcvs?rev=354264view=rev
Log:
Fixed the remaining legitimate checkstyle and PMD issues
Modified:
jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml
jakarta/commons/proper/configuration/trunk/project.properties
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/AbstractConfiguration.java
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertiesConfiguration.java
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/PropertyConverter.java
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/plist/PropertyListConfiguration.java
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/plist/XMLPropertyListConfiguration.java
Modified:
jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml?rev=354264r1=354263r2=354264view=diff
==
--- jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml
(original)
+++ jakarta/commons/proper/configuration/trunk/conf/checkstyle-suppressions.xml
Mon Dec 5 19:10:27 2005
@@ -16,5 +16,7 @@
suppress checks=.* files=SimpleCharStream.java/
suppress checks=.* files=Token.java/
suppress checks=.* files=TokenMgrError.java/
+
+suppress checks=MissingSwitchDefault
files=PropertiesConfiguration.java/
/suppressions
Modified: jakarta/commons/proper/configuration/trunk/project.properties
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/project.properties?rev=354264r1=354263r2=354264view=diff
==
--- jakarta/commons/proper/configuration/trunk/project.properties (original)
+++ jakarta/commons/proper/configuration/trunk/project.properties Mon Dec 5
19:10:27 2005
@@ -19,6 +19,7 @@
compile.deprecation = off
maven.checkstyle.properties=conf/checkstyle.xml
+maven.pmd.excludes=**/*PropertyListParser*
maven.junit.fork=true
maven.test.failure.ignore=false
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/AbstractConfiguration.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/AbstractConfiguration.java?rev=354264r1=354263r2=354264view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/AbstractConfiguration.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/AbstractConfiguration.java
Mon Dec 5 19:10:27 2005
@@ -48,7 +48,7 @@
protected static final String END_TOKEN = };
/** The property delimiter used while parsing (a comma). */
-private static char DELIMITER = ',';
+private static char delimiter = ',';
/**
* Whether the configuration should throw NoSuchElementExceptions or simply
@@ -64,7 +64,7 @@
*/
public static void setDelimiter(char delimiter)
{
-AbstractConfiguration.DELIMITER = delimiter;
+AbstractConfiguration.delimiter = delimiter;
}
/**
@@ -74,7 +74,7 @@
*/
public static char getDelimiter()
{
-return AbstractConfiguration.DELIMITER;
+return AbstractConfiguration.delimiter;
}
/**
@@ -108,7 +108,7 @@
*/
public void addProperty(String key, Object value)
{
-Iterator it = PropertyConverter.toIterator(value, DELIMITER);
+Iterator it = PropertyConverter.toIterator(value, getDelimiter());
while (it.hasNext())
{
addPropertyDirect(key, it.next());
Modified:
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java?rev=354264r1=354263r2=354264view=diff
==
---
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
(original)
+++
jakarta/commons/proper/configuration/trunk/src/java/org/apache/commons/configuration/ConfigurationMap.java
Mon Dec 5 19:10:27 2005
@@ -91,12 +91,20 @@
return configuration.getProperty(String.valueOf(key));
}
+/**
+ * Set of entries in the map.
+ */
static
Re: [VOTE] Release Configuration 1.2
Phil Steitz wrote: Sorry to be so late checking / trying to help. I am +1 for the release assuming Stephen's points (other than the ones listed as optional) and the following issues are addressed: - You should either modify configs, fix issues or eliminate PMD and checkstyle reports I fixed the remaining issues with PMD and Checkstyle. There are just some false positives left (an unused variable for PMD that is actually used, and missing method comments for Checkstyle that actually exist in a super class). I could disable line by line the checkstyle warnings left, but this would be a pain to maintain. I'd rather bet on a fix of Checkstyle in a future release. Emmanuel Bourg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354274 - in /jakarta/commons/proper/commons-build/trunk: menus/ parts/ xdocs/ xdocs/dormant/ xdocs/sandbox/
Author: rahul Date: Mon Dec 5 19:38:04 2005 New Revision: 354274 URL: http://svn.apache.org/viewcvs?rev=354274view=rev Log: Changes to the Commons website: ** Match the state of the repository * Remove dormant components from sandbox listing * Create a dormant components web page * Create three sections on Commons home page ** List procedure for reviving dormant components (see dormant components page) * Hen's sandbox pruning proposal states a VOTE is required ** Other menu changes * Remove broken link for Korean translation * Remove link for Japanese translation (stale content) * Moved Wiki link to General information Added: jakarta/commons/proper/commons-build/trunk/menus/dormant-items.ent (with props) jakarta/commons/proper/commons-build/trunk/menus/dormant.ent (with props) jakarta/commons/proper/commons-build/trunk/parts/dormant-table.ent (with props) jakarta/commons/proper/commons-build/trunk/xdocs/dormant/ jakarta/commons/proper/commons-build/trunk/xdocs/dormant/index.xml (with props) Removed: jakarta/commons/proper/commons-build/trunk/menus/resources.ent Modified: jakarta/commons/proper/commons-build/trunk/menus/about-main-menu.ent jakarta/commons/proper/commons-build/trunk/menus/about.ent jakarta/commons/proper/commons-build/trunk/menus/information.ent jakarta/commons/proper/commons-build/trunk/menus/menus.dtd jakarta/commons/proper/commons-build/trunk/menus/sandbox-items.ent jakarta/commons/proper/commons-build/trunk/menus/view.ent jakarta/commons/proper/commons-build/trunk/parts/parts.dtd jakarta/commons/proper/commons-build/trunk/parts/sandbox-table.ent jakarta/commons/proper/commons-build/trunk/xdocs/index.xml jakarta/commons/proper/commons-build/trunk/xdocs/navigation.xml jakarta/commons/proper/commons-build/trunk/xdocs/sandbox/index.xml Modified: jakarta/commons/proper/commons-build/trunk/menus/about-main-menu.ent URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/menus/about-main-menu.ent?rev=354274r1=354273r2=354274view=diff == --- jakarta/commons/proper/commons-build/trunk/menus/about-main-menu.ent (original) +++ jakarta/commons/proper/commons-build/trunk/menus/about-main-menu.ent Mon Dec 5 19:38:04 2005 @@ -9,5 +9,8 @@ item name=Sandbox href=/sandbox/index.html collapse=true sandbox-items; /item +item name=Dormant href=/dormant/index.html collapse=true +dormant-items; +/item /menu Modified: jakarta/commons/proper/commons-build/trunk/menus/about.ent URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/menus/about.ent?rev=354274r1=354273r2=354274view=diff == --- jakarta/commons/proper/commons-build/trunk/menus/about.ent (original) +++ jakarta/commons/proper/commons-build/trunk/menus/about.ent Mon Dec 5 19:38:04 2005 @@ -9,5 +9,8 @@ item name=Sandbox href=http://jakarta.apache.org/commons/sandbox/index.html; collapse=true item name=Full list... href=http://jakarta.apache.org/commons/sandbox/index.html/ /item +item name=Dormant href=http://jakarta.apache.org/commons/dormant/index.html; collapse=true +item name=Full list... href=http://jakarta.apache.org/commons/dormant/index.html/ +/item /menu Added: jakarta/commons/proper/commons-build/trunk/menus/dormant-items.ent URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/menus/dormant-items.ent?rev=354274view=auto == --- jakarta/commons/proper/commons-build/trunk/menus/dormant-items.ent (added) +++ jakarta/commons/proper/commons-build/trunk/menus/dormant-items.ent Mon Dec 5 19:38:04 2005 @@ -0,0 +1,13 @@ +item name=Cache href=http://jakarta.apache.org/commons/sandbox/cache// +item name=Clazz href=http://jakarta.apache.org/commons/sandbox/clazz// +item name=Convert href=http://jakarta.apache.org/commons/sandbox/convert// +item name=Events href=http://jakarta.apache.org/commons/sandbox/events// +item name=Functor href=http://jakarta.apache.org/commons/sandbox/functor// +item name=Javaflow href=http://jakarta.apache.org/commons/sandbox/javaflow// +item name=JJar href=http://jakarta.apache.org/commons/sandbox/jjar// +item name=Mapper href=http://jakarta.apache.org/commons/sandbox/mapper// +item name=Messenger href=http://jakarta.apache.org/commons/sandbox/messenger// +item name=Scaffold href=http://jakarta.apache.org/commons/sandbox/scaffold// +item name=ThreadPool
[all] Website TODOs
I've refreshed the Commons website according to recent discussions. TODOs: 1) Dormant components revival (website says [1] we need a VOTE according to the sandbox pruning proposal [2]). Any objections? 2) There are 6 links under View Source Code Repository, a bit of a clutter. Hen was to check with infra to see if we can slash that down to 3. Hen? 3) I've refreshed site for [scxml]. Rest of the components will pick up changes as their sites are refreshed. 4) I think Steve mentioned the chmod failures on site:sshdeploy for Commons. Since I witnessed that today, that has to do with the recursive chmod under siteDirectory, which hits every component in commons (given the directory structure), many of which have hostile permissions for a chmod, given other owners. I don't think we need to worry about this (unless someone wants to convince maven to recurse selectively). -Rahul [1] http://jakarta.apache.org/commons/dormant/index.html (see bottom of) [2] http://wiki.apache.org/jakarta-commons/ProposalSandboxPruning - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Website TODOs
On 12/5/05, Rahul Akolkar [EMAIL PROTECTED] wrote: I've refreshed the Commons website according to recent discussions. snip/ Oh, and therefore, yell at me if you notice any regressions ;-) -Rahul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354318 - /jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseMethodTestCase.java
Author: niallp
Date: Mon Dec 5 21:14:51 2005
New Revision: 354318
URL: http://svn.apache.org/viewcvs?rev=354318view=rev
Log:
Add new ResourcesBase JUnit test (forgotten when committing changes for Bug
37642)
Added:
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseMethodTestCase.java
(with props)
Added:
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseMethodTestCase.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseMethodTestCase.java?rev=354318view=auto
==
---
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseMethodTestCase.java
(added)
+++
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseMethodTestCase.java
Mon Dec 5 21:14:51 2005
@@ -0,0 +1,393 @@
+/*
+ * $Id$
+ * $Revision$
+ * $Date$
+ *
+ *
+ *
+ * Copyright 2005 The Apache Software Foundation
+ *
+ * Licensed under the Apache License, Version 2.0 (the License);
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.commons.resources.impl;
+
+import java.util.ArrayList;
+import java.util.Iterator;
+import java.util.List;
+import java.util.Locale;
+import java.util.TimeZone;
+import java.util.Map;
+import java.util.HashMap;
+import java.io.Reader;
+import java.io.InputStream;
+
+import junit.framework.Test;
+import junit.framework.TestSuite;
+import junit.framework.TestCase;
+
+import org.apache.commons.resources.Resources;
+import org.apache.commons.resources.ResourcesException;
+import org.apache.commons.resources.ResourcesKeyException;
+
+/**
+ * pUnit tests for ResourceBase which checks that the standard
+ *content retrieval methods all work inter-changeably.
+ * /p
+ * pFor example if the getObject() method retrieves an InputStream
+ *the getReader() method converts the InputStream to a Reader.
+ * /p
+ */
+public class ResourcesBaseMethodTestCase extends TestCase {
+
+
+// - Instance Variables
+
+
+// The Resources instance to be tested
+protected Resources resources = null;
+
+private static Map testMap;
+private String[] keys = null;
+private static int BUFFER_SIZE = 20;
+
+
+// --- Constructors
+
+
+public ResourcesBaseMethodTestCase(String name) {
+super(name);
+}
+
+
+// --- Overall Test Methods
+
+
+// Set up instance variables required by this test case
+public void setUp() throws Exception {
+super.setUp();
+testMap = new HashMap();
+testMap.put(buffer-0, );
+testMap.put(buffer-1, makeString(1));
+testMap.put(buffer-2, makeString(2));
+testMap.put(buffer-less1, makeString(BUFFER_SIZE - 1));
+testMap.put(buffer-size, makeString(BUFFER_SIZE));
+testMap.put(buffer-plus1, makeString(BUFFER_SIZE + 1));
+testMap.put(buffer-large, makeString((BUFFER_SIZE * 3) + 1));
+
+Iterator iterator = testMap.keySet().iterator();
+List list = new ArrayList();
+while (iterator.hasNext()) {
+Object key = iterator.next();
+list.add(key);
+//System.out.println(TEST MAP Key=[ + key + ] value=[ +
testMap.get(key) + ]);
+}
+keys = new String[list.size()];
+keys = (String[])list.toArray(keys);
+
+}
+
+/**
+ * Create a String value of a specified length
+ * containing repeated digits of 0 - 9.
+ */
+private String makeString(int size) {
+StringBuffer buffer = new StringBuffer();
+int count = 0;
+for (int i = 0; i size; i++) {
+ if (count 9) {
+ count = 0;
+ }
+ buffer.append(count);
+ count++;
+}
+return buffer.toString();
+}
+
+// Return the tests included in this test suite
+public static Test suite() {
+return (new TestSuite(ResourcesBaseMethodTestCase.class));
+}
+
+// Tear down the instance variables required by this test case
+public void tearDown() {
+resources = null;
+}
+
+
+//
svn commit: r354328 - in /jakarta/commons/proper/fileupload/trunk: fileupload_basic.xml fileupload_checks.xml project.properties
Author: martinc
Date: Mon Dec 5 22:04:33 2005
New Revision: 354328
URL: http://svn.apache.org/viewcvs?rev=354328view=rev
Log:
* Target JRE 1.3 VMs.
* Tweak Checkstyle rules to be more stringent.
* Add custom PMD rule configuration.
Added:
jakarta/commons/proper/fileupload/trunk/fileupload_basic.xml (with props)
Modified:
jakarta/commons/proper/fileupload/trunk/fileupload_checks.xml
jakarta/commons/proper/fileupload/trunk/project.properties
Added: jakarta/commons/proper/fileupload/trunk/fileupload_basic.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/fileupload/trunk/fileupload_basic.xml?rev=354328view=auto
==
--- jakarta/commons/proper/fileupload/trunk/fileupload_basic.xml (added)
+++ jakarta/commons/proper/fileupload/trunk/fileupload_basic.xml Mon Dec 5
22:04:33 2005
@@ -0,0 +1,9 @@
+?xml version=1.0?
+
+ruleset name=FileUpload Basic Rules
+ descriptionPMD Basic Ruleset minus the EmptyCatchBlock rule./description
+
+ rule ref=rulesets/basic.xml
+exclude name=EmptyCatchBlock/
+ /rule
+/ruleset
Propchange: jakarta/commons/proper/fileupload/trunk/fileupload_basic.xml
--
svn:keywords = Date Author Id Revision HeadURL
Modified: jakarta/commons/proper/fileupload/trunk/fileupload_checks.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/fileupload/trunk/fileupload_checks.xml?rev=354328r1=354327r2=354328view=diff
==
--- jakarta/commons/proper/fileupload/trunk/fileupload_checks.xml (original)
+++ jakarta/commons/proper/fileupload/trunk/fileupload_checks.xml Mon Dec 5
22:04:33 2005
@@ -138,7 +138,11 @@
!-- Checks for Size Violations.--
!-- See http://checkstyle.sf.net/config_sizes.html --
module name=FileLength/
-module name=LineLength/
+!-- Begin Custom for FileUpload --
+module name=LineLength
+ property name=ignorePattern value=^ \* @version .*$/
+/module
+!-- End Custom for FileUpload --
module name=MethodLength/
module name=ParameterNumber/
@@ -165,7 +169,11 @@
!-- Checks for blocks. You know, those {}'s --
!-- See http://checkstyle.sf.net/config_blocks.html --
module name=AvoidNestedBlocks/
-!-- Disabled for FileUpload: module name=EmptyBlock/ --
+!-- Begin Custom for FileUpload --
+module name=EmptyBlock
+ property name=option value=text/
+/module
+!-- End Custom for FileUpload --
module name=LeftCurly/
module name=NeedBraces/
module name=RightCurly/
Modified: jakarta/commons/proper/fileupload/trunk/project.properties
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/fileupload/trunk/project.properties?rev=354328r1=354327r2=354328view=diff
==
--- jakarta/commons/proper/fileupload/trunk/project.properties (original)
+++ jakarta/commons/proper/fileupload/trunk/project.properties Mon Dec 5
22:04:33 2005
@@ -22,14 +22,23 @@
compile.optimize = off
compile.deprecation = off
-maven.compile.source=1.4
-maven.compile.target=1.4
+maven.compile.source=1.3
+maven.compile.target=1.3
maven.checkstyle.properties = ${basedir}/fileupload_checks.xml
checkstyle.regexp.header=${basedir}/license-header.txt
+maven.pmd.rulesetfiles=fileupload_basic.xml,rulesets/unusedcode.xml,rulesets/imports.xml
+
maven.javadoc.additionalparam=-tag todo:a:To Do:
-maven.linkcheck.enable=true
+maven.linkcheck.enable=true
+
+# Ostensibly, changes since the FileUpload 1.0 release at SVN revision 133359.
+# Unfortunately, it doesn't work, which is why it's commented out.
+# I guess I'll have to compile the release notes without Maven's help.
+# (The plugin needs to support SVN revision numbers, which it doesn't today.)
+#maven.changelog.type = date
+#maven.changelog.date = 2003-06-24
# documentation properties
maven.xdoc.jsl=../commons-build/commons-site.jsl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354330 - in /jakarta/commons/proper/resources/trunk: src/java/org/apache/commons/resources/ src/java/org/apache/commons/resources/impl/ src/test/org/apache/commons/resources/impl/ xdocs/
Author: niallp
Date: Mon Dec 5 22:05:19 2005
New Revision: 354330
URL: http://svn.apache.org/viewcvs?rev=354330view=rev
Log:
Remove TimeZone from Resources API (see Bug 37709)
Modified:
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Messages.java
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Resources.java
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/impl/CollectionResourcesBase.java
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/impl/ResourceBundleResources.java
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/impl/ResourcesBase.java
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/CollectionResourcesBaseTestCase.java
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourceBundleResourcesTestCase.java
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseMethodTestCase.java
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/ResourcesBaseTestCase.java
jakarta/commons/proper/resources/trunk/src/test/org/apache/commons/resources/impl/TestResources.java
jakarta/commons/proper/resources/trunk/xdocs/changes.xml
jakarta/commons/proper/resources/trunk/xdocs/index.xml
Modified:
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Messages.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Messages.java?rev=354330r1=354329r2=354330view=diff
==
---
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Messages.java
(original)
+++
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Messages.java
Mon Dec 5 22:05:19 2005
@@ -233,7 +233,7 @@
String message = null;
try {
-message = resources.getString(key, locale, null);
+message = resources.getString(key, locale);
} catch (ResourcesException e) {
Log log = LogFactory.getLog(Messages.class);
if (log.isDebugEnabled()) {
Modified:
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Resources.java
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Resources.java?rev=354330r1=354329r2=354330view=diff
==
---
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Resources.java
(original)
+++
jakarta/commons/proper/resources/trunk/src/java/org/apache/commons/resources/Resources.java
Mon Dec 5 22:05:19 2005
@@ -28,13 +28,12 @@
import java.io.Serializable;
import java.util.Iterator;
import java.util.Locale;
-import java.util.TimeZone;
/**
* pAn abstract representation of a set of internationalized resources,
* which are arbitrary objects identified by a unique String codekey/code.
- * Localized versions of the resources (based on Locale and optional
- * TimeZone parameters) can be retrieved in a variety of formats./p
+ * Localized versions of the resources (based on Locale parameter)
+ * can be retrieved in a variety of formats./p
*
* pWhen presented with an invalid codekey/code value, resource
* getter methods will behave differently based on the current value of
@@ -50,8 +49,8 @@
* application resources, and other specialized approaches as desired./p
*
* pDifferent implementations of the [EMAIL PROTECTED] Resources} interface
may apply
- * different semantics to the use of the codelocale/code and/or
- * codetimeZone/code attributes used to perform localization. Consult
+ * different semantics to the use of the codelocale/code
+ * attribute used to perform localization. Consult
* the documentation for the specific [EMAIL PROTECTED] Resources}
implementation you
* are using for the specific details of your implementation./p
*
@@ -140,14 +139,12 @@
/**
* pReturn the content for the specified codekey/code as a
- * byte array, localized based on the specified codelocale/code
- * and/or codetimeZone/code./p
+ * byte array, localized based on the specified codelocale/code.
+ * /p
*
* @param key Identifier for the requested content
* @param locale Locale with which to localize retrieval,
* or codenull/code for the default Locale
- * @param timeZone TimeZone with which to localize retrieval,
- * or codenull/code for the default TimeZone
* @return content for a specified key.
*
* @exception ResourcesException if an error occurs retrieving or
@@ -156,19 +153,17 @@
* key was found, and codeisReturnNull()/code returns
* codefalse/code
DO NOT REPLY [Bug 37709] - [resources] Remove TimeZone from Resources API
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=37709. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37709 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-12-06 07:08 --- Closing as FIXED: http://svn.apache.org/viewcvs?rev=354330view=rev -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r354340 - /jakarta/commons/proper/vfs/trunk/project.xml
Author: imario Date: Mon Dec 5 22:46:24 2005 New Revision: 354340 URL: http://svn.apache.org/viewcvs?rev=354340view=rev Log: wrong site directory Modified: jakarta/commons/proper/vfs/trunk/project.xml Modified: jakarta/commons/proper/vfs/trunk/project.xml URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/vfs/trunk/project.xml?rev=354340r1=354339r2=354340view=diff == --- jakarta/commons/proper/vfs/trunk/project.xml (original) +++ jakarta/commons/proper/vfs/trunk/project.xml Mon Dec 5 22:46:24 2005 @@ -33,7 +33,7 @@ !-- siteDirectory/www/jakarta.apache.org/commons/vfs//siteDirectory -- -siteDirectorypublic_html/vfs-1.0-RC6/site/siteDirectory +siteDirectorypublic_html/vfs-1.0-RC7/site/siteDirectory distributionDirectory/www/jakarta.apache.org/builds/jakarta-commons/vfs//distributionDirectory repository connectionscm:svn:http://svn.apache.org/repos/asf/jakarta/commons/proper/vfs/trunk/connection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
