[GUMP@vmgump]: Project commons-scxml-test (in module apache-commons) failed

2011-02-19 Thread Gump 
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 gene...@gump.apache.org.

Project commons-scxml-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 93 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-scxml-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/scxml/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/gump_work/build_apache-commons_commons-scxml-test.html
Work Name: build_apache-commons_commons-scxml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 19 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/scxml]
M2_HOME: /opt/maven2
-

---
 T E S T S
---
Running org.apache.commons.scxml.invoke.InvokeTestSuite
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.54 sec
Running org.apache.commons.scxml.test.TestingTestSuite
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
Running org.apache.commons.scxml.env.EnvTestSuite
Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.185 sec
Running org.apache.commons.scxml.SCXMLTestSuite
Tests run: 71, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.973 sec <<< 
FAILURE!
Running org.apache.commons.scxml.issues.IssuesTestSuite
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.381 sec
Running org.apache.commons.scxml.model.ModelTestSuite
Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.377 sec <<< 
FAILURE!
Running org.apache.commons.scxml.env.faces.EnvFacesTestSuite
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec
Running org.apache.commons.scxml.semantics.SemanticsTestSuite
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.scxml.env.jsp.EnvJspTestSuite
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec
Running org.apache.commons.scxml.env.jexl.EnvJexlTestSuite
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
Running org.apache.commons.scxml.env.servlet.EnvServletTestSuite
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.scxml.io.IOTestSuite
Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.377 sec

Results :

Failed tests: 
  
testNamespacePrefixedXPathsEL(org.apache.commons.scxml.NamespacePrefixedXPathsTest)
  testDatamodelSimultaneousJsp(org.apache.commons.scxml.model.DatamodelTest)

Tests run: 228, Failures: 2, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 17 seconds
[INFO] Finished at: Sat Feb 19 10:10:14 UTC 2011
[INFO] Final Memory: 25M/61M
[INFO] 
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/atom.xml

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 05000619022011, vmgump.apache.org:vmgump:05000619022011
Gump E-mail Identifier (unique with

[GUMP@vmgump]: Project commons-jelly-tags-quartz (in module commons-jelly) failed

2011-02-19 Thread Gump 
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 gene...@gump.apache.org.

Project commons-jelly-tags-quartz has an issue affecting its community 
integration.
This issue affects 1 projects.
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-quartz :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-quartz/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [commons-jelly-tags-quartz-19022011.jar] identifier 
set to project name
 -DEBUG- Dependency on logging-log4j-12 exists, no need to add for property 
maven.jar.log4j.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- Dependency on commons-jexl-1.x exists, no need to add for property 
maven.jar.commons-jexl.
 -DEBUG- (Apache Gump generated) Apache Maven Properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/project.properties
 -INFO- Project Reports in: 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/target/test-reports
 -WARNING- No directory 
[/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/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-quartz/gump_work/build_commons-jelly_commons-jelly-tags-quartz.html
Work Name: build_commons-jelly_commons-jelly-tags-quartz (Type: Build)
Work ended in a state of : Failed
Elapsed: 5 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/quartz]
-
java:compile:
[echo] Compiling to 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/target/classes
[javac] Compiling 7 source files to 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/target/classes
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/src/java/org/apache/commons/jelly/tags/quartz/CronTriggerTag.java:198:
 org.quartz.CronTrigger is abstract; cannot be instantiated
[javac] CronTrigger trigger = new CronTrigger( getName(),
[javac]   ^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/src/java/org/apache/commons/jelly/tags/quartz/CronTriggerTag.java:201:
 cannot find symbol
[javac] symbol  : method setCronExpression(java.lang.String)
[javac] location: interface org.quartz.CronTrigger
[javac] trigger.setCronExpression( getSpec() );
[javac]^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/src/java/org/apache/commons/jelly/tags/quartz/CronTriggerTag.java:206:
 cannot find symbol
[javac] symbol  : method setJobName(java.lang.String)
[javac] location: interface org.quartz.CronTrigger
[javac] trigger.setJobName( getJobName() );
[javac]^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/src/java/org/apache/commons/jelly/tags/quartz/CronTriggerTag.java:207:
 cannot find symbol
[javac] symbol  : method setJobGroup(java.lang.String)
[javac] location: interface org.quartz.CronTrigger
[javac] trigger.setJobGroup( getJobGroup() );
[javac]^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/src/java/org/apache/commons/jelly/tags/quartz/CronTriggerTag.java:208:
 cannot find symbol
[javac] symbol  : method setStartTime(java.util.Date)
[javac] location: interface org.quartz.CronTrigger
[javac] trigger.setStartTime( new Date() );
[javac]^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/src/java/org/apache/commons/jelly/tags/quartz/JobTag.java:118:
 org.quartz.JobDetail is abstract; cannot be instantiated
[javac] JobDetail detail = new JobDetail( getName(),
[javac]^
[javac] 
/srv/gump/public/workspace/commons-jelly/jelly-tags/quartz/src/java/org/apache/commons/jelly/tags/quartz/JobTag.java:122:
 cannot find symbol
[javac] symbol  : method setDurability(boolean)
[javac] location: interface org.quartz.JobDetail
[javac] detail.setDurability( true );
[javac]   ^
[javac] 
/srv/gump/public/workspace/commons-j

[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed

2011-02-19 Thread Gump 
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 gene...@gump.apache.org.

Project commons-proxy-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 93 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-proxy-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -WARNING- Overriding Maven settings: 
[/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/proxy/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html
Work Name: build_apache-commons_commons-proxy-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 11 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/proxy]
M2_HOME: /opt/maven2
-
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.factory.util.TestMethodSignature
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.apache.commons.proxy.provider.TestConstantProvider
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
Running org.apache.commons.proxy.interceptor.TestInterceptorChain
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running org.apache.commons.proxy.invoker.TestNullInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
Running org.apache.commons.proxy.exception.TestDelegateProviderException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.apache.commons.proxy.invoker.TestChainInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.16 sec
Running org.apache.commons.proxy.exception.TestProxyFactoryException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec
Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.proxy.provider.TestBeanProvider
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec

Results :

Tests in error: 
  testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker)

Tests run: 179, Failures: 0, Errors: 1, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 10 seconds
[INFO] Finished at: Sat Feb 19 10:47:06 UTC 2011
[INFO] Final Memory: 24M/58M
[INFO] 
-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml
- Atom: 
http://vmgump.apache.or

Re: [GUMP@vmgump]: Project commons-math (in module apache-commons) failed

2011-02-19 Thread Phil Steitz 
Relevant test output:

[junit] Running org.apache.commons.math.optimization.direct.CMAESOptimizerTest
[junit] Testsuite: 
org.apache.commons.math.optimization.direct.CMAESOptimizerTest
[junit] Tests run: 21, Failures: 1, Errors: 0, Time elapsed: 10.666 sec
[junit] Tests run: 21, Failures: 1, Errors: 0, Time elapsed: 10.666 sec
[junit] 
[junit] Testcase: testInitOutofbounds took 0.151 sec
[junit] Testcase: testBoundariesDimensionMismatch took 0.002 sec
[junit] Testcase: testBoundariesNoData took 0.001 sec
[junit] Testcase: testInputSigmaNegative took 0.001 sec
[junit] Testcase: testInputSigmaOutOfRange took 0.001 sec
[junit] Testcase: testInputSigmaDimensionMismatch took 0.001 sec
[junit] Testcase: testRosen took 1.922 sec
[junit] Testcase: testMaximize took 1.382 sec
[junit] FAILED
[junit] expected:<1.0> but was:<0.9099897>
[junit] junit.framework.AssertionFailedError: expected:<1.0> but 
was:<0.9099897>
[junit] at 
org.apache.commons.math.optimization.direct.CMAESOptimizerTest.doTest(CMAESOptimizerTest.java:380)
[junit] at 
org.apache.commons.math.optimization.direct.CMAESOptimizerTest.testMaximize(CMAESOptimizerTest.java:147)





-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-math (in module apache-commons) failed

2011-02-19 Thread Gump 
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 gene...@gump.apache.org.

Project commons-math has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-math :  The Jakarta Mathematics Library


Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-math/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole jar output [commons-math-19022011.jar] identifier set to project 
name
 -DEBUG- Dependency on junit exists, no need to add for property junit.jar.
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-math/gump_work/build_apache-commons_commons-math.html
Work Name: build_apache-commons_commons-math (Type: Build)
Work ended in a state of : Failed
Elapsed: 5 mins 7 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
 org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Djunit.jar=/srv/gump/public/workspace/junit/dist/junit-19022011.jar 
-Dfinal.name=commons-math-19022011 jar 
[Working Directory: /srv/gump/public/workspace/apache-commons/math]
CLASSPATH: 
/usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/apache-commons/math/target/classes:/srv/gump/public/workspace/apache-commons/math/target/test-classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/junit/dist/junit-19022011.jar:/srv/gump/public/workspace/junit/dist/junit-dep-19022011.jar
-
[junit] Testcase: testCopy took 0 sec
[junit] Testcase: testContainsKey took 0.004 sec
[junit] Testcase: testIterator took 0.017 sec
[junit] Testcase: testConcurrentModification took 0.001 sec
[junit] Testcase: testPutKeysWithCollisions took 0 sec
[junit] Testcase: testPutKeysWithCollision2 took 0.001 sec
[junit] Running org.apache.commons.math.util.PairTest
[junit] Testsuite: org.apache.commons.math.util.PairTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.019 sec
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.019 sec
[junit] 
[junit] Testcase: testAccessor took 0.004 sec
[junit] Testcase: testEquals took 0 sec
[junit] Running org.apache.commons.math.util.ResizableDoubleArrayTest
[junit] Testsuite: org.apache.commons.math.util.ResizableDoubleArrayTest
[junit] Tests run: 14, Failures: 0, Errors: 0, Time elapsed: 0.212 sec
[junit] Tests run: 14, Failures: 0, Errors: 0, Time elapsed: 0.212 sec
[junit] 
[junit] Testcase: testConstructors took 0.021 sec
[junit] Testcase: testSetElementArbitraryExpansion took 0.121 sec
[junit] Testcase: testAdd1000 took 0 sec
[junit] Testcase: testAddElements took 0.013 sec
[junit] Testcase: testAddElementRolling took 0.036 sec
[junit] Testcase: testSetNumberOfElements took 0 sec
[junit] Testcase: testWithInitialCapacity took 0.005 sec
[junit] Testcase: testWithInitialCapacityAndExpansionFactor took 0.001 sec
[junit] Testcase: testDiscard took 0 sec
[junit] Testcase: testSubstitute took 0 sec
[junit] Testcase: testMutators took 0 sec
[junit] Testcase: testEqualsAndHashCode took 0.001 sec
[junit] Testcase: testGetValues took 0 sec
[junit] Testcase: testMinMax took 0 sec
[junit] Running org.apache.commons.math.util.TransformerMapTest
[junit] Testsuite: org.apache.commons.math.util.TransformerMapTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.031 sec
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.031 sec
[junit] 
[junit] Testcase: testPutTransformer took 0.005 sec
[junit] Testcase: testContainsClass took 0 sec
[junit] Testcase: testContainsTransformer took 0 sec
[junit] Testc

Re: [jexl] Short description in commit messages (was: svn commit: r1072000)

2011-02-19 Thread sebb 
On 18 February 2011 22:54, Phil Steitz  wrote:
> On 2/18/11 2:14 PM, sebb wrote:
>> I agree it's helpful to have at least the subject of the JIRA in the
>> log message, but IMO there should be nothing in the log message that
>> is not in the JIRA and/or code comments.
>>
>> The SVN log message should enable reviewers to understand the content
>> of the commit but should otherwise be disposable. SVN log messages are
>> not versioned, so can be permanently overwritten. Also we release
>> source code, and if SVN log messages are necessary to understand the
>> code, then the comments are insufficient.
>>
> I agree that svn log messages should not be necessary to understand
> the code; but they are a very important tool in understanding how
> the revision history works - i.e., what was changed when.  The fact
> that they can be modified is a plus - it means we can go back and
> fix errors in the log messages or improve them.

Or they can be obliterated with no trace ...

> I am frequently
> thankful of developers who have written good and complete commit
> messages not for understanding how code works, but why it works the
> way it does.

Such information should not be confined to log messages, partly
because log messages are hard to scan and not guaranteed to be
available, but mainly because the source code should be understandable
on its own.

External users will generally only see the source code. If there is
important information about how the source code works buried in SVN
log messages, then I think we have failed to produce the best source
code that we can.

> I personally have no problem at all with duplication
> between the content of these messages and comments and/or
> descriptions in JIRA.

Agree, duplication is not a problem.

> Phil
>> S.
>> On 18 February 2011 17:22, henrib  wrote:
>>> Sorry about that; will do. Got it reversed between what I write in Jira and
>>> in the svn log.
>>> Regards,
>>> Henrib
>>> --
>>> View this message in context: 
>>> http://apache-commons.680414.n4.nabble.com/Re-jexl-Short-description-in-commit-messages-was-svn-commit-r1072000-tp3312834p3313182.html
>>> Sent from the Commons - Dev mailing list archive at Nabble.com.
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[math] velocity problem while doing a dry run on RC

2011-02-19 Thread Luc Maisonobe 
Hello,

It seems 2.2 has been stabilized thanks to the efforts of everybody.
I fixed the latest CLIRR problems, the latest report is available here:
.

I tried a dry run on creating a release candidate, and encountered a
velocity problem while generating the release notes.

I used Phil's scripts math-pre-RC.sh which calls
  mvn changes:announcement-generate

This triggered the following error message a few times:

[ERROR] Parser Exception: templates/math-release-notes.vm :
org.apache.velocity.runtime.parser.ParseException: Encountered
"\"\n\")\n\n" at line 22, column 39.
Was expecting one of:
"[" ...
 ...
"true" ...
"false" ...
 ...
 ...
"{" ...

at
org.apache.velocity.runtime.parser.Parser.generateParseException(Parser.java:3271)
at
org.apache.velocity.runtime.parser.Parser.jj_consume_token(Parser.java:3155)
at org.apache.velocity.runtime.parser.Parser.Parameter(Parser.java:1022)


Lines 22-23 and following of math-release-notes.vm read:

$release.description.replaceAll("  ", "
")

This line seem to have been last modified as of r927472 just before 2.1
release to fix a parenthesis problem.

The net result is the the release notes file is empty.

What did I do wrong ?
Luc

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [jexl] Short description in commit messages (was: svn commit: r1072000)

2011-02-19 Thread Rahul Akolkar 
On Sat, Feb 19, 2011 at 2:22 PM, sebb  wrote:
> On 18 February 2011 22:54, Phil Steitz  wrote:
>> On 2/18/11 2:14 PM, sebb wrote:
>>> I agree it's helpful to have at least the subject of the JIRA in the
>>> log message, but IMO there should be nothing in the log message that
>>> is not in the JIRA and/or code comments.
>>>
>>> The SVN log message should enable reviewers to understand the content
>>> of the commit but should otherwise be disposable. SVN log messages are
>>> not versioned, so can be permanently overwritten. Also we release
>>> source code, and if SVN log messages are necessary to understand the
>>> code, then the comments are insufficient.
>>>
>> I agree that svn log messages should not be necessary to understand
>> the code; but they are a very important tool in understanding how
>> the revision history works - i.e., what was changed when.  The fact
>> that they can be modified is a plus - it means we can go back and
>> fix errors in the log messages or improve them.
>
> Or they can be obliterated with no trace ...
>


I doubt this happens often, and if and when it does, we have oversight
via notification of svn:log changes (and permanent archival).


>> I am frequently
>> thankful of developers who have written good and complete commit
>> messages not for understanding how code works, but why it works the
>> way it does.
>
> Such information should not be confined to log messages, partly
> because log messages are hard to scan and not guaranteed to be
> available, but mainly because the source code should be understandable
> on its own.
>
> External users will generally only see the source code. If there is
> important information about how the source code works buried in SVN
> log messages, then I think we have failed to produce the best source
> code that we can.
>


We may be talking about different things by now. The original point
was (since I made it) -- when I read diffs in email or 'svn log'
output, it is easier if I see "FOO-123 Fixed bar to alleviate baz" as
against "FOO-123".

-Rahul

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [math] velocity problem while doing a dry run on RC

2011-02-19 Thread Phil Steitz 
On 2/19/11 2:45 PM, Luc Maisonobe wrote:
> Hello,
>
> It seems 2.2 has been stabilized thanks to the efforts of everybody.
> I fixed the latest CLIRR problems, the latest report is available here:
> .
>
> I tried a dry run on creating a release candidate, and encountered a
> velocity problem while generating the release notes.
>
> I used Phil's scripts math-pre-RC.sh which calls
>   mvn changes:announcement-generate
>
> This triggered the following error message a few times:
>
> [ERROR] Parser Exception: templates/math-release-notes.vm :
> org.apache.velocity.runtime.parser.ParseException: Encountered
> "\"\n\")\n\n" at line 22, column 39.
> Was expecting one of:
> "[" ...
>  ...
> "true" ...
> "false" ...
>  ...
>  ...
> "{" ...
>
>   at
> org.apache.velocity.runtime.parser.Parser.generateParseException(Parser.java:3271)
>   at
> org.apache.velocity.runtime.parser.Parser.jj_consume_token(Parser.java:3155)
>   at org.apache.velocity.runtime.parser.Parser.Parameter(Parser.java:1022)
>
>
> Lines 22-23 and following of math-release-notes.vm read:
>
> $release.description.replaceAll("  ", "
> ")
>
> This line seem to have been last modified as of r927472 just before 2.1
> release to fix a parenthesis problem.
>
> The net result is the the release notes file is empty.
>
> What did I do wrong ?

Works4me using

Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_22
...
OS name: "mac os x" version: "10.6.6" arch: "x86_64" Family: "mac"

What versions of maven and what jdk are you using?

Phil

> Luc
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[collections] retire or release?

2011-02-19 Thread Henri Yandell 
Seeing this bug reported for the Nth time:

https://issues.apache.org/jira/browse/COLLECTIONS-371

I wonder if collections should be declared dead. It's a dumb bug,
(removeAll calling retainAll), and users have had to put up with it
for years now.

Hen

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GUMP@vmgump]: Project commons-attributes (in module apache-commons) failed

2011-02-19 Thread Gump 
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 gene...@gump.apache.org.

Project commons-attributes has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 21 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-attributes :  Commons Attributes


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-attributes/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-attributes/gump_work/build_apache-commons_commons-attributes.html
Work Name: build_apache-commons_commons-attributes (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true 
-Dbuild.sysclasspath=only org.apache.tools.ant.Main 
-Dgump.merge=/srv/gump/public/gump/work/merge.xml 
-Dfinal.name.api=commons-attributes-api-20022011 
-Dfinal.name.compiler=commons-attributes-compiler-20022011 dist 
[Working Directory: /srv/gump/public/workspace/apache-commons/attributes]
CLASSPATH: 
/usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/apache-commons/attributes/target/classes:/srv/gump/public/workspace/apache-commons/attributes/target/test-classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/qdox/qdox-1.12.jar:/srv/gump/public/workspace/junit/dist/junit-20022011.jar:/srv/gump/public/workspace/junit/dist/junit-dep-20022011.jar
-
Buildfile: /srv/gump/public/workspace/apache-commons/attributes/build.xml

init:
[mkdir] Created dir: 
/srv/gump/public/workspace/apache-commons/attributes/target/lib

get-deps:

compile:
[mkdir] Created dir: 
/srv/gump/public/workspace/apache-commons/attributes/target/classes
[javac] Compiling 28 source files to 
/srv/gump/public/workspace/apache-commons/attributes/target/classes
[javac] 
/srv/gump/public/workspace/apache-commons/attributes/compiler/src/java/org/apache/commons/attributes/compiler/AttributeCompiler.java:90:
 warning: [deprecation] project in org.apache.tools.ant.ProjectComponent has 
been deprecated
[javac] String sourcePaths = project.getReference 
(pathref).toString ();
[javac]  ^
[javac] 
/srv/gump/public/workspace/apache-commons/attributes/compiler/src/java/org/apache/commons/attributes/compiler/AttributeCompiler.java:96:
 warning: [deprecation] project in org.apache.tools.ant.ProjectComponent has 
been deprecated
[javac] fs.setProject (project);
[javac]^
[javac] 
/srv/gump/public/workspace/apache-commons/attributes/compiler/src/java/org/apache/commons/attributes/compiler/AttributeCompiler.java:245:
 incompatible types
[javac] found   : com.thoughtworks.qdox.model.JavaPackage
[javac] required: java.lang.String
[javac] packageName = javaClass.getPackage ();
[javac]^
[javac] 
/srv/gump/public/workspace/apache-commons/attributes/compiler/src/java/org/apache/commons/attributes/compiler/AttributeCompiler.java:454:
 warning: [deprecation] getFile() in com.thoughtworks.qdox.model.JavaSource has 
been deprecated
[javac] return javaClass.getSource ().getFile ();
[javac]  ^
[javac] 
/srv/gump/public/workspace/apache-commons/attributes/compiler/src/java/org/apache/commons/attributes/compiler/AttributeCompiler.java:481:
 warning: [deprecation] project in org.apache.tools.ant.ProjectComponent has 
been deprecated
[javac] DirectoryScanner ds = 
fs.getDirectoryScanner(project);
[javac]  ^
[javac] 
/srv/gump/public/workspace/apache-commons/attributes/compiler/src/java/org/apache/commons/attributes/compiler/AttributeCompiler.java:482:
 warning: [deprecation] project in org.apache.tools.ant.ProjectComponent has 
been deprecated
[javac] File from