[GUMP@vmgump]: Project commons-scxml-test (in module apache-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 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 26 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: 18 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.344 sec Running org.apache.commons.scxml.test.TestingTestSuite Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.scxml.env.EnvTestSuite Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.168 sec Running org.apache.commons.scxml.SCXMLTestSuite Tests run: 71, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.834 sec <<< FAILURE! Running org.apache.commons.scxml.issues.IssuesTestSuite Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.349 sec Running org.apache.commons.scxml.model.ModelTestSuite Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.294 sec <<< FAILURE! Running org.apache.commons.scxml.env.faces.EnvFacesTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.scxml.semantics.SemanticsTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running org.apache.commons.scxml.env.jsp.EnvJspTestSuite Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec Running org.apache.commons.scxml.env.jexl.EnvJexlTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 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.403 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 Jan 15 09:51:12 UTC 2011 [INFO] Final Memory: 41M/99M [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 06000615012011, vmgump.apache.org:vmgump:06000615012011 Gump E-mail Identifier (unique wit
[GUMP@vmgump]: Project commons-jelly-tags-quartz (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 gene...@gump.apache.org. Project commons-jelly-tags-quartz has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 14 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-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-15012011.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] -DEBUG- Extracted 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: 4 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@vmgump]: Project commons-proxy-test (in module apache-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 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 26 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: 10 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.006 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 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.03 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.017 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.032 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.154 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.provider.TestBeanProvider Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 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: 9 seconds [INFO] Finished at: Sat Jan 15 10:26:54 UTC 2011 [INFO] Final Memory: 39M/94M [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.org
Re: [lang] What's left for 3.0?
See JIRA :) https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310481&fixfor=12311714&resolution=-1&sorter/field=priority&sorter/order=DESC On Fri, Jan 14, 2011 at 12:42 PM, Matt Benson wrote: > See title. > > -Matt > > - > 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
creating internal errors
Hi all, With the exception refactoring, MathRuntimeException has been deprecated in branch 2.X (but it is neither deprecated nor deleted in trunk for now ...). This class did include a createInternalError static method that is useful in defensive programming for difficult cases. It is used at 4 different places in branch 2.X and could be used in other places too (I generally place one such thing in the default statement of a switch case when all cases are known to be handled, as a security layer for later changes in the number of cases). So I propose to add a dedicated exception for this feature, probably inheriting from MathIllegalStateException. Any thoughts ? Luc - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [jira] Issue Comment Edited: (MATH-475) MathUtils.equals(double, double, double) does not agree with Javadoc
Hi.
On Sat, Jan 15, 2011 at 12:48:45PM -0500, Phil Steitz (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/MATH-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982118#action_12982118
> ]
>
> Phil Steitz edited comment on MATH-475 at 1/15/11 12:48 PM:
>
>
> Very interesting example. How do you come up with this stuff, Sebb? :)
>
> I tend to agree with Gilles' view that if if a and b are not distinguishable
> as doubles, we don't really have any confidence in the value of abs(a - b),
> so the short-circuit in the current code is better. I would say just update
> the javadoc to make say something like
>
> "Returns true if the values are indistinguishable as doubles or the
> difference between them is within the range of allowed error (inclusive)."
>
> was (Author: psteitz):
> Very interesting example. How do you come up with this stuff, Sebb? :)
>
> I tend to agree with Gilles' view that if if a and b are not distinguishable
> as doubles, we don't really have any confidence in the value of abs(a - b),
> so the short-circuit in the current code is better. I would say just update
> the javadoc to make say something like
>
> "Returns true if there is no double value strictly between the arguments or
> the difference between them is within the range of allowed error (inclusive)."
Just to be sure that we agree on the semantics of "equals": The latter
description ("there is no double value strictly between the arguments")
seems more representative of the code. Indeed, 2 successive floating point
numbers _are_ distinguishable, but "equals" will nevertheless return true on
the ground that any real number within the interval could be mapped to
either of the two floating point numbers.
Gilles
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [jira] Issue Comment Edited: (MATH-475) MathUtils.equals(double, double, double) does not agree with Javadoc
On Sat, Jan 15, 2011 at 8:32 PM, Gilles Sadowski
wrote:
> Hi.
>
> On Sat, Jan 15, 2011 at 12:48:45PM -0500, Phil Steitz (JIRA) wrote:
>>
>> [
>> https://issues.apache.org/jira/browse/MATH-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982118#action_12982118
>> ]
>>
>> Phil Steitz edited comment on MATH-475 at 1/15/11 12:48 PM:
>>
>>
>> Very interesting example. How do you come up with this stuff, Sebb? :)
>>
>> I tend to agree with Gilles' view that if if a and b are not distinguishable
>> as doubles, we don't really have any confidence in the value of abs(a - b),
>> so the short-circuit in the current code is better. I would say just update
>> the javadoc to make say something like
>>
>> "Returns true if the values are indistinguishable as doubles or the
>> difference between them is within the range of allowed error (inclusive)."
>>
>> was (Author: psteitz):
>> Very interesting example. How do you come up with this stuff, Sebb? :)
>>
>> I tend to agree with Gilles' view that if if a and b are not distinguishable
>> as doubles, we don't really have any confidence in the value of abs(a - b),
>> so the short-circuit in the current code is better. I would say just update
>> the javadoc to make say something like
>>
>> "Returns true if there is no double value strictly between the arguments or
>> the difference between them is within the range of allowed error
>> (inclusive)."
>
> Just to be sure that we agree on the semantics of "equals": The latter
> description ("there is no double value strictly between the arguments")
> seems more representative of the code. Indeed, 2 successive floating point
> numbers _are_ distinguishable, but "equals" will nevertheless return true on
> the ground that any real number within the interval could be mapped to
> either of the two floating point numbers.
>
Sorry I got the second version of the comment wrong. You are right
that the current impl of equals identifies two consecutive doubles.
Phil
>
> Gilles
>
> -
> 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
[GUMP@vmgump]: Project commons-collections4 (in module apache-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 gene...@gump.apache.org. Project commons-collections4 has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-collections4 : Collections - commons-collections4-testframework : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-collections4/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/collections/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/collections/pom.xml -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-collections4/gump_work/build_apache-commons_commons-collections4.html Work Name: build_apache-commons_commons-collections4 (Type: Build) Work ended in a state of : Failed Elapsed: 16 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/collections/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/apache-commons/collections] M2_HOME: /opt/maven2 - required: org.apache.commons.collections.Closure[] found: org.apache.commons.collections.Closure[] [INFO] 8 errors [INFO] - [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/SwitchTransformer.java:[68,38] invalid inferred types for T; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Predicate[] found: org.apache.commons.collections.Predicate[] /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/SwitchTransformer.java:[69,40] invalid inferred types for I; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Transformer[] found: org.apache.commons.collections.Transformer[] /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/OnePredicate.java:[66,38] invalid inferred types for T; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Predicate[] found: org.apache.commons.collections.Predicate[] /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/SwitchClosure.java:[66,38] invalid inferred types for T; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Predicate[] found: org.apache.commons.collections.Predicate[] /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/SwitchClosure.java:[67,36] invalid inferred types for E; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Closure[] found: org.apache.commons.collections.Closure[] /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/ChainedTransformer.java:[56,40] invalid inferred types for I; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Transformer[] found: org.apache.commons.collections.Transformer[] /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/NonePredicate.java:[61,38] invalid inferred types for T; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Predicate[] found: org.apache.commons.collections.Predicate[] /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/ChainedClosure.java:[53,36] invalid inferred types for E; actual arguments do not conforms to inferred formal arguments required: org.apache.commons.collections.Closure[] found: org.apache.commons.collections.Closure[] [INFO] [INFO] For more information, run Maven with the -e switch [INFO] -
