Re: [lang3] Test Fail in Headless Mode (at Least on a Mac)

2010-12-03 Thread Henri Yandell 
On Wed, Dec 1, 2010 at 7:57 AM, Matt Benson  wrote:
>
> On Dec 1, 2010, at 2:45 AM, Stefan Bodewig wrote:
>
>> On 2010-12-01, Henri Yandell wrote:
>>
>>> I've fixed this in r1040879.
>>
>> I can confirm it is fixed for Gump as well.  I removed all awt.headless
>> settings from the Gump descriptor and the build still passes on adam.
>>
>
> Having thought I was following this thread, being an OSX user, and having 
> worked in the event package I can only apologize for having apparently 
> skimmed over the part of the thread that revealed that this is where the 
> fault was.  Thanks for fixing this, Hen.
>
> -Matt

No prob, gives me something to do :)

Hen

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

RE: [VFS] Maven 3.0.1?

2010-12-03 Thread Gary Gregory 
Ah, for the first time, 'mvn test' worked with Maven 3! 

First 'mvn clean test' failed, then 'mvn clean' worked, then 'mvn test' worked. 
Go figure.

Gary Gregory
Senior Software Engineer
Rocket Software
3340 Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA
Tel: +1.404.760.1560
Email: ggreg...@seagullsoftware.com
Web: seagull.rocketsoftware.com  


> -Original Message-
> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
> Sent: Friday, December 03, 2010 01:40
> To: Commons Developers List
> Subject: Re: [VFS] Maven 3.0.1?
> 
> It is very noisy but it works for me.  I actually tried it before I voted to
> release 3.0.1 and just did an svn up and ran it again on my MacBook Pro.
> 
> I've not tried the site plugin.
> 
> I'm not planning on doing the vfs release with 3.0.1 though.
> 
> Ralph
> 
> On Dec 2, 2010, at 8:06 PM, Gary Gregory wrote:
> 
> > Hi All,
> >
> > Can anyone get VFS to build with Maven 3.0.1?
> > Gary Gregory
> > Senior Software Engineer
> > Rocket Software
> > 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA
> > Tel: +1.404.760.1560
> > Email: ggreg...@seagullsoftware.com
> > Web: seagull.rocketsoftware.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

[g...@vmgump]: Project commons-collections4 (in module apache-commons) failed

2010-12-03 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-collections4 has an issue affecting its community integration.
This issue affects 2 projects.
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: 34 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] 
[INFO] Total time:

RE: VFS release

2010-12-03 Thread Gary Gregory 
> -Original Message-
> From: Jörg Schaible [mailto:joerg.schai...@gmx.de]
> Sent: Thursday, December 02, 2010 14:11
> To: dev@commons.apache.org
> Subject: RE: VFS release
> 
> Gary Gregory wrote:
> 
> > How about warnings like:
> >
> > Description ResourcePathLocationType
> > The serializable class FileNotFolderException does not declare a static
> > final serialVersionUID field of type long
> FileNotFolderException.java
> > /commons-vfs2/src/main/java/org/apache/commons/vfs2 line 24 Java
> Problem
> >
> > ?
> 
> The serialVersionUID is part of the binary compatibility therefore it should
> be set to be sure. Setting it implies though that you update it every time
> you change the binary layout of the class (ot take further actions to keep
> serialization compatibility). Without using an explicit value, the
> serialVeeionUID is computed on its own and you might not even notice the
> problem (in former times different compilers created sometimes different
> UIDs). In our code we set it normally to the date of last modification if
> the binary layout e.g. 20101102L.

I usually add serialVersionUID = -1 but I do like your convention. So I added 
serialVersionUID = 20101208L

Gary

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

[math] Re: [jira] Created: (MATH-451) "solvers": Make the maximum number of evaluations a parameter of the "solve" methods

2010-12-03 Thread Luc Maisonobe 
Hi,

Le 03/12/2010 16:19, Gilles (JIRA) a écrit :
> "solvers": Make the maximum number of evaluations a parameter of the "solve" 
> methods
> 
> 
>  Key: MATH-451
>  URL: https://issues.apache.org/jira/browse/MATH-451
>  Project: Commons Math
>   Issue Type: Improvement
> Reporter: Gilles
> Assignee: Gilles
> Priority: Minor
>  Fix For: 3.0
> 
> 
> Currently, the number of allowed evaluations is set by the 
> {{setMaxEvaluations}} method.
> In the ML, it was proposed to pass that parameter when calling the {{solve}} 
> method. The setter will be removed.
> The existing {{solve}} methods will remain, using a default value (100) for 
> the the maximum number of evaluations.
> 
> 

For simplifying transition, this should probably be added in 2.X rather
than in 3.0. Of course it IS an incompatible change since it is in a
public interface, but this interface is not intended for people to
implement it. It is rather an interface commons-math implements in the
spirit of the algorithm design pattern: the user can rely on the
interface definition if he wants a generic solver (or he uses a specific
solver if a needs special features available only in one type of solver).

So I would propose to first add the new methods in the interface in 2.X,
and only deprecate the old ones without maxEvaluations. We would delete
the deprecated methods as proposed in 3.0.

I'm not sure if there should how the default value should be handled: an
additional method in the interface or a special handling if for example
the provided value is 0 or negative ? Also as this maxEvaluation is
mostly used as a safeguard to avoid infinite loops, a default value
should be much higher than 100. Probably something like 1000 or event
higher. I would personnaly prefer to not have a default value and let
the user always set one as he wants according to his type of problem.
However, I'm on the fence on it.

best regards,
Luc

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

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

2010-12-03 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.
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: 21 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.861 sec
Running org.apache.commons.scxml.test.TestingTestSuite
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.commons.scxml.env.EnvTestSuite
Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.205 sec
Running org.apache.commons.scxml.SCXMLTestSuite
Tests run: 71, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.018 sec <<< 
FAILURE!
Running org.apache.commons.scxml.issues.IssuesTestSuite
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec
Running org.apache.commons.scxml.model.ModelTestSuite
Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.579 sec <<< 
FAILURE!
Running org.apache.commons.scxml.env.faces.EnvFacesTestSuite
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 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.038 sec
Running org.apache.commons.scxml.env.jexl.EnvJexlTestSuite
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
Running org.apache.commons.scxml.env.servlet.EnvServletTestSuite
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.commons.scxml.io.IOTestSuite
Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.416 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: 19 seconds
[INFO] Finished at: Fri Dec 03 20:28:10 UTC 2010
[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 06001203122010, vmgump.apache.org:vmgump:06001203122010
Gump E-mail Identifier (unique within run) #8.

--
Apache Gump
http://gump

[GUMP@vmgump]: Project commons-id (in module commons-sandbox) failed

2010-12-03 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-id 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-id :  Commons Identifier Package


Full details are available at:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/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-id-03122010.jar] identifier set to project 
name
 -DEBUG- (Apache Gump generated) Apache Maven Properties in: 
/srv/gump/public/workspace/commons-sandbox/id/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/id/project.xml
 -DEBUG- Maven project properties in: 
/srv/gump/public/workspace/commons-sandbox/id/project.properties
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-id/gump_work/build_commons-sandbox_commons-id.html
Work Name: build_commons-sandbox_commons-id (Type: Build)
Work ended in a state of : Failed
Elapsed: 27 secs
Command Line: maven --offline jar 
[Working Directory: /srv/gump/public/workspace/commons-sandbox/id]
-
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.58 sec
[junit] Running org.apache.commons.id.uuid.state.NodeTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.373 sec
[junit] Running 
org.apache.commons.id.uuid.state.ReadOnlyResourceStateImplTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.498 sec
[junit] Running org.apache.commons.id.uuid.state.ReadWriteFileStateImplTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.513 sec
[junit] Running org.apache.commons.id.uuid.state.StateHelperTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.294 sec
[junit] Running org.apache.commons.id.uuid.state.InMemoryStateImplTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.347 sec
[junit] Running org.apache.commons.id.uuid.UUIDTest
[junit] Tests run: 17, Failures: 0, Errors: 0, Time elapsed: 0.262 sec
[junit] Running org.apache.commons.id.uuid.NodeManagerImplTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.366 sec
[junit] Running org.apache.commons.id.uuid.task.UUIDTaskTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.423 sec
[junit] Running org.apache.commons.id.uuid.clock.ThreadClockImplTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.302 sec
[junit] Running org.apache.commons.id.uuid.clock.SystemClockImplTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.24 sec
[junit] Running org.apache.commons.id.serial.AlphanumericGeneratorTest
[junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.303 sec
[junit] Running org.apache.commons.id.serial.LongGeneratorTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.3 sec
[junit] Running org.apache.commons.id.serial.PrefixedNumericGeneratorTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.241 sec
[junit] Running org.apache.commons.id.serial.NumericGeneratorTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.245 sec
[junit] Running 
org.apache.commons.id.serial.PrefixedLeftPaddedNumericGeneratorTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.233 sec
[junit] Running 
org.apache.commons.id.serial.PrefixedAlphanumericGeneratorTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.237 sec
[junit] Running 
org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest
[junit] Tests run: 12, Failures: 1, Errors: 0, Time elapsed: 0.776 sec
[junit] [ERROR] TEST 
org.apache.commons.id.serial.TimeBasedAlphanumericIdentifierGeneratorTest FAILED
[junit] Running org.apache.commons.id.CompositeIdentifierGeneratorTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.338 sec
[junit] Running org.apache.commons.id.ConstantIdentifierGeneratorTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.252 sec

BUILD FAILED
File.. /home/gump/.maven/cache/maven-test-plugin-1.6.2/plugin.jelly
Element... fail
Line.. 181
Column 54
There were test failures.
Total time: 26 seconds
Finished at: Fri Dec 03 21:19:59 UTC 2010

-

To subscribe to this information via syndicated feeds:
- RSS: http://vmgum

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

2010-12-03 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-03122010.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: 6 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-jelly/je

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

2010-12-03 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.
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: 13 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.004 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.005 sec
Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec
Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.186 sec
Running org.apache.commons.proxy.interceptor.TestInterceptorChain
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running org.apache.commons.proxy.invoker.TestNullInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec
Running org.apache.commons.proxy.exception.TestDelegateProviderException
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running org.apache.commons.proxy.invoker.TestChainInvoker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec
Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 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.002 sec
Running org.apache.commons.proxy.provider.TestBeanProvider
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 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: 12 seconds
[INFO] Finished at: Fri Dec 03 21:21:19 UTC 2010
[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/gump/public/apache-commons/commons-pr

Re: [math] Re: [jira] Created: (MATH-451) "solvers": Make the maximum number of evaluations a parameter of the "solve" methods

2010-12-03 Thread Gilles Sadowski 
Hello.

> > 
> > Currently, the number of allowed evaluations is set by the 
> > {{setMaxEvaluations}} method.
> > In the ML, it was proposed to pass that parameter when calling the 
> > {{solve}} method. The setter will be removed.
> > The existing {{solve}} methods will remain, using a default value (100) for 
> > the the maximum number of evaluations.
> > 
> > 
> 
> For simplifying transition, this should probably be added in 2.X rather
> than in 3.0. Of course it IS an incompatible change since it is in a
> public interface, but this interface is not intended for people to
> implement it. It is rather an interface commons-math implements in the
> spirit of the algorithm design pattern: the user can rely on the
> interface definition if he wants a generic solver (or he uses a specific
> solver if a needs special features available only in one type of solver).
> 
> So I would propose to first add the new methods in the interface in 2.X,
> and only deprecate the old ones without maxEvaluations. We would delete
> the deprecated methods as proposed in 3.0.

Since it's breaking compatibility, I don't see how it could be allowed in
2.x.

Then, why do you want to deprecate and remove the existing methods?

> I'm not sure if there should how the default value should be handled: an
> additional method in the interface or a special handling if for example
> the provided value is 0 or negative ?

With a negative value, the "solve" will just throw immediately, reminding
the user that his choice doesn't make any sense.

> Also as this maxEvaluation is
> mostly used as a safeguard to avoid infinite loops, a default value
> should be much higher than 100. Probably something like 1000 or event
> higher.

I chose "100" because it is the default value for the number of iterations
in 2.1.
If there is a default, I think on the contrary that it should not be high:
when a user expects that an algorithm will take many iterations, he should
set the number explicitly. A relatively low number will help in drawing the
user's attention that some computation may be longer than he expects (or
maybe that the problem he tries to solve is ill defined).
The default should be a compromise between "works in most cases" and "don't
loose too much time before failing anyway".

> I would personnaly prefer to not have a default value and let
> the user always set one as he wants according to his type of problem.
> However, I'm on the fence on it.

One reason for keeping a default is that we don't have to change all the
calls in the unit tests...

Best,
Gilles

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