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

2012-03-24 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 65 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 -Dsimplelog.defaultlog=info 
--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
-
[INFO] SimpleSCXMLListener - /s2/s2.1/e1.2
[INFO] SimpleSCXMLListener - /s2/s2.1/e1.2
[INFO] SimpleSCXMLListener - /s2/s2.1
[INFO] SimpleSCXMLListener - /s2
[INFO] SimpleSCXMLListener - transition (event = s2.1.done, cond = null, from = 
/s2, to = /s3)
[INFO] SimpleSCXMLListener - /s3
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.15 sec
Running org.apache.commons.scxml.issues.Issue64Test
[INFO] SCXMLSemantics - null: Begin transition bug test ...
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SCXMLSemantics - null: somedata
[INFO] SCXMLSemantics - null: *somedata
[INFO] SimpleSCXMLListener - transition (event = show.bug, cond = null, from = 
/tranbug, to = /end)
[INFO] SimpleSCXMLListener - /end
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:30:21
 and digester match "scxml/datamodel/misplaced"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:36:19
 and digester match "scxml/state/onentry/foo"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://my.foo.example/"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:37:22
 and digester match "scxml/state/onentry/bar"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:41:21
 and digester match "scxml/state/transition/datamodel"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://www.w3.org/2005/07/scxml"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:42:41
 and digester match "scxml/state/transition/datamodel/data"
[WARN] SCXMLParser - Ignoring element  in namespace 
"http://my.foo.example/"; at 
file:/srv/gump/public/workspace/apache-commons/scxml/target/test-classes/org/apache/commons/scxml/issues/issue64-02.xml:49:14
 and digester match "scxml/baz"
[INFO] SCXMLSemantics - null: Begin transition bug test ...
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SimpleSCXMLListener - /tranbug
[INFO] SCXMLSemantics - null: null
[WARN] SimpleErrorReporter - EXPRESSION_ERROR (eval(''*' + dummy'):null): 
[INFO] SimpleSCXMLListener - transition (event = show.bug, cond = null, from = 
/tranbug, to = /end)
[INFO] SimpleSCXMLListener - /end
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 sec

Results :

Failed tests: 
  testCustomActionCallbacks(org.apache.commons.scxml.model.CustomActionTest)

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

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO]

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

2012-03-24 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-testframework has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 23 runs.
The current state of this project is 'Failed', with reason 'Missing Build 
Outputs'.
For reference only, the following projects are affected by this:
- commons-collections4-testframework :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-collections4-testframework/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-collections-testframework-*[0-9T].jar] 
identifier set to project name
 -INFO- Failed with reason missing build outputs
 -ERROR- Missing Output: 
/srv/gump/public/workspace/apache-commons/collections/target/commons-collections-testframework-*[0-9T].jar
 -ERROR- See Directory Listing Work for Missing Outputs
 -INFO- Failed to extract fallback artifacts from Gump Repository

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

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 1225032012, vmgump.apache.org:vmgump:1225032012
Gump E-mail Identifier (unique within run) #20.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

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

2012-03-24 Thread commons-graph development 
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-graph has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 17 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-graph :  Apache commons sandbox


Full details are available at:

http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/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-graph-*[0-9T].jar] identifier set to project 
name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/commons-sandbox/graph/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-sandbox/graph/pom.xml
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-graph/gump_work/build_commons-sandbox_commons-graph.html
Work Name: build_commons-sandbox_commons-graph (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/commons-sandbox/graph/gump_mvn_settings.xml install 
[Working Directory: /srv/gump/public/workspace/commons-sandbox/graph]
M2_HOME: /opt/maven2
-
symbol  : method 
applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[82,47]
 cannot find symbol
symbol  : method 
applyingDepthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[102,43]
 cannot find symbol
symbol  : method 
applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/flow/DefaultMaxFlowAlgorithmSelector.java:[109,47]
 cannot find symbol
symbol  : method 
applyingBreadthFirstSearch(org.apache.commons.graph.flow.FlowNetworkHandler)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector>>
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/spanning/DefaultSpanningTreeSourceSelector.java:[111,96]
 applyingDijkstra(WO) in 
org.apache.commons.graph.shortestpath.ShortestPathAlgorithmSelector,java.lang.Object,org.apache.commons.graph.WeightedGraph>
 cannot be applied to (WO)
[ERROR] 
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/connectivity/DefaultConnectivityAlgorithmsSelector.java:[70,64]
 cannot find symbol
symbol  : method 
applyingDepthFirstSearch(org.apache.commons.graph.connectivity.ConnectedComponentHandler)
location: interface 
org.apache.commons.graph.visit.VisitAlgorithmsSelector
[INFO] 10 errors 
[INFO] -
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure

/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[169,59]
 
withConnections(org.apache.commons.graph.builder.GraphConnection)
 in 
org.apache.commons.graph.builder.LinkedConnectionBuilder>
 cannot be applied to (org.apache.commons.graph.builder.GraphConnection)
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[181,71]
 
withConnections(org.apache.commons.graph.builder.GraphConnection)
 in 
org.apache.commons.graph.builder.LinkedConnectionBuilder>
 cannot be applied to (org.apache.commons.graph.builder.GraphConnection)
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:[193,61]
 
withConnections(org.apache.commons.graph.builder.GraphConnection)
 in 
org.apache.commons.graph.builder.LinkedConnectionBuilder>
 cannot be applied to (org.apache.commons.graph.builder.GraphConnection)
/srv/gump/public/workspace/commons-sandbox/graph/src/main/java/org/apache/commons/graph/CommonsGraph.java:

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

2012-03-24 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-exec-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 2 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-exec-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-exec-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/exec/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/exec/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/gump_work/build_apache-commons_commons-exec-test.html
Work Name: build_apache-commons_commons-exec-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 24 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/exec]
M2_HOME: /opt/maven2
-
FOO..
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 
(Exit value: 143)
Process completed in 2055 millis; below is its output
Process timed out and was killed.
Executing [sh, -c, src/test/scripts/invoker.sh]
invoker.sh -- going to start daemon process
cd: 21: can't cd to ../../../target
invoker.sh --  daemon process was started
Process completed in 8044 millis; above is its output
0: process has terminated: false
1: process has terminated: false
2: process has terminated: false
3: process has terminated: false
4: process has terminated: false
5: process has terminated: false
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.022 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.028 ms
Process completed in 2004 millis; below is its output
Process timed out and was killed by watchdog.
gdal_translate
HDF5:"/home/kk/grass/data/4404.he5"://HDFEOS/GRIDS/OMI_Column_Amount_O3/Data_Fields/ColumnAmountO3/home/kk/4.tif
FOO..
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.901 sec <<< 
FAILURE!

Results :

Failed tests: 
  testExec_60(org.apache.commons.exec.DefaultExecutorTest)

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

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

Please refer to 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 minute 23 seconds
[INFO] Finished at: Sun Mar 25 02:49:24 UTC 2012
[INFO] Final Memory: 25M/65M
[INFO] 
-

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

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 1225032012, vmgump.apache.org:vmgump:1225032012
Gump E-mail Identifier (unique within run) #15.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

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

2012-03-24 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-digester3 has an issue affecting its community integration.
This issue affects 2 projects,
 and has been outstanding for 84 runs.
The current state of this project is 'Failed', with reason 'Missing Build 
Outputs'.
For reference only, the following projects are affected by this:
- commons-digester3 :  XML to Java Object Configuration
- commons-digester3-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/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-digester3-*[0-9T].jar] identifier set to 
project name
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml
 -DEBUG- Maven POM in: 
/srv/gump/public/workspace/apache-commons/digester/pom.xml
 -INFO- Failed with reason missing build outputs
 -ERROR- Missing Output: 
/srv/gump/public/workspace/apache-commons/digester/target/commons-digester3-*[0-9T].jar
 -ERROR- See Directory Listing Work for Missing Outputs
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-digester3/gump_work/build_apache-commons_commons-digester3.html
Work Name: build_apache-commons_commons-digester3 (Type: Build)
Work ended in a state of : Success
Elapsed: 1 min 33 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/apache-commons/digester/gump_mvn_settings.xml 
package 
[Working Directory: /srv/gump/public/workspace/apache-commons/digester]
M2_HOME: /opt/maven2
-
Downloading: 
http://localhost:8192/maven2/org/apache/maven/maven-monitor/2.2.1/maven-monitor-2.2.1.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/wagon/wagon-ssh/1.0-beta-6/wagon-ssh-1.0-beta-6.pom

Downloading: 
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.1/plexus-archiver-1.1.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-repository-builder/1.0-alpha-2/maven-repository-builder-1.0-alpha-2.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.0-alpha-1/maven-common-artifact-filters-1.0-alpha-1.pom

Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-shared-components/6/maven-shared-components-6.pom

Downloading: 
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.1/plexus-archiver-1.1.jar
Downloading: 
http://localhost:8192/maven2/org/apache/maven/shared/maven-repository-builder/1.0-alpha-2/maven-repository-builder-1.0-alpha-2.jar


[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor: 
/srv/gump/public/workspace/apache-commons/digester/dist/src/main/assembly/bin.xml
[INFO] Reading assembly descriptor: 
/srv/gump/public/workspace/apache-commons/digester/dist/src/main/assembly/src.xml
[INFO] Building tar : 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-bin.tar.gz
[INFO] Building zip: 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-bin.zip
[INFO] Building tar : 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-src.tar.gz
[INFO] Building zip: 
/srv/gump/public/workspace/apache-commons/digester/dist/target/commons-digester3-3.3-SNAPSHOT-src.zip
[INFO] 
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Commons Digester ... SUCCESS [9.875s]
[INFO] Apache Commons Digester :: Core ... SUCCESS [30.219s]
[INFO] Apache Commons Digester :: Annotations Processor .. SUCCESS [2.550s]
[INFO] Commons Digester :: Examples .. SUCCESS [0.606s]
[INFO] Apache Commons Digester :: Examples :: Annotations :: Atom  SUCCESS 
[2.974s]
[INFO] Apache Commons Digester :: Examples :: API :: Address Book  SUCCESS 
[1.971s]
[INFO] Apache Commons Digester :: Examples :: API :: Catalog . SUCCESS [1.842s]
[INFO] Apache Commons Digester :: Examples :: API :: DB Insert  SUCCESS [1.932s]
[INFO] Apache Commons Digester :: Examples :: API :: Document Markup  SUCCESS 
[1.576s]
[INFO] Apache Commons Digester :: Examples :: EDSL :: Atom ... SUCCESS [1.933s]
[INFO] Apache Commons Digester :: Examples :: Plugins :: Pipeline  SUCCESS 
[1.714s]
[INFO] Apache Commons Digester :: Examples ::

Re: [CSV] trimming spaces - are both leading/trailing required?

2012-03-24 Thread Emmanuel Bourg 
+1 for a single parameter controlling the trimming of the values (quoted 
or not).


Emmanuel Bourg


Le 23/03/2012 12:36, sebb a écrit :

Do we really need to support independent leading/trailing spaces?

I've been unable to find any reference to formats that require this.

-
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

Re: [all] how to make Jira aware of releases

2012-03-24 Thread Luc Maisonobe 
Le 24/03/2012 20:12, Thomas Neidhart a écrit :
> On 03/24/2012 07:33 PM, Luc Maisonobe wrote:
>> Le 24/03/2012 17:35, Thomas Neidhart a écrit :
>>> On 03/24/2012 05:29 PM, Luc Maisonobe wrote:
 Hi all,

 I have tried to tell Jira that version 3.0 of [math] has already been
 shipped, but I don't find how to do it. Some pages tell me I should
 connect to something called bamboo for release management, but I don't
 know what it is.

 Does someone know how we declare releases ?
>>>
>>> >From what I have seen, in jira under versions, you can declare a
>>> specific version as being released (with a release date).
>>>
>>> https://issues.apache.org/jira/plugins/servlet/project-config/MATH/versions
>>
>> Thanks Thomas,
>>
>> I had found that page but somehow missed the "manage version" link on
>> the right.
>>
>> The release date for 3.0 has been set now.
> 
> Hi Luc,
> 
> I think you still have to mark it as released, otherwise there will be
> no changelog/release notes available for this version.
> 
> On the manage versions page, when you hover of the 3.0 line, there is a
> small tool icon on the right side. In the menu there is a "Release"
> action available that would mark this version as being released.

Done, thanks

Luc

> 
> Thomas
> 
> -
> 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

Re: [all] how to make Jira aware of releases

2012-03-24 Thread Thomas Neidhart 
On 03/24/2012 07:33 PM, Luc Maisonobe wrote:
> Le 24/03/2012 17:35, Thomas Neidhart a écrit :
>> On 03/24/2012 05:29 PM, Luc Maisonobe wrote:
>>> Hi all,
>>>
>>> I have tried to tell Jira that version 3.0 of [math] has already been
>>> shipped, but I don't find how to do it. Some pages tell me I should
>>> connect to something called bamboo for release management, but I don't
>>> know what it is.
>>>
>>> Does someone know how we declare releases ?
>>
>> >From what I have seen, in jira under versions, you can declare a
>> specific version as being released (with a release date).
>>
>> https://issues.apache.org/jira/plugins/servlet/project-config/MATH/versions
> 
> Thanks Thomas,
> 
> I had found that page but somehow missed the "manage version" link on
> the right.
> 
> The release date for 3.0 has been set now.

Hi Luc,

I think you still have to mark it as released, otherwise there will be
no changelog/release notes available for this version.

On the manage versions page, when you hover of the 3.0 line, there is a
small tool icon on the right side. In the menu there is a "Release"
action available that would mark this version as being released.

Thomas

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

Re: [all] how to make Jira aware of releases

2012-03-24 Thread Luc Maisonobe 
Le 24/03/2012 17:35, Thomas Neidhart a écrit :
> On 03/24/2012 05:29 PM, Luc Maisonobe wrote:
>> Hi all,
>>
>> I have tried to tell Jira that version 3.0 of [math] has already been
>> shipped, but I don't find how to do it. Some pages tell me I should
>> connect to something called bamboo for release management, but I don't
>> know what it is.
>>
>> Does someone know how we declare releases ?
> 
>>From what I have seen, in jira under versions, you can declare a
> specific version as being released (with a release date).
> 
> https://issues.apache.org/jira/plugins/servlet/project-config/MATH/versions

Thanks Thomas,

I had found that page but somehow missed the "manage version" link on
the right.

The release date for 3.0 has been set now.

Luc


> Thomas
> 
> -
> 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

Re: [all] how to make Jira aware of releases

2012-03-24 Thread Thomas Neidhart 
On 03/24/2012 05:29 PM, Luc Maisonobe wrote:
> Hi all,
> 
> I have tried to tell Jira that version 3.0 of [math] has already been
> shipped, but I don't find how to do it. Some pages tell me I should
> connect to something called bamboo for release management, but I don't
> know what it is.
> 
> Does someone know how we declare releases ?

>From what I have seen, in jira under versions, you can declare a
specific version as being released (with a release date).

https://issues.apache.org/jira/plugins/servlet/project-config/MATH/versions

Thomas

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

[all] how to make Jira aware of releases

2012-03-24 Thread Luc Maisonobe 
Hi all,

I have tried to tell Jira that version 3.0 of [math] has already been
shipped, but I don't find how to do it. Some pages tell me I should
connect to something called bamboo for release management, but I don't
know what it is.

Does someone know how we declare releases ?

thanks in advance
Luc

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

Re: [math] Commons-Math 3.1?

2012-03-24 Thread Thomas Neidhart 
On 03/18/2012 02:07 PM, Gilles Sadowski wrote:
> On Sun, Mar 18, 2012 at 10:35:51AM +0100, Sébastien Brisard wrote:
>> Dear all,
>>
>>>
>>> We should also close the Jira issues that have been solved as of 3.0.
>>> For newcomers, our policy on JIRA issues is that we mark them as
>>> resolved when the fix is available in the subversion repository, and we
>>> mark them as closed when the fix has been released in an official version.
>>>
>> I closed the tickets for which I was the reported and/or assignee. I
>> prefer not to touch the other ones.
> 
> You are welcome to close them all, if you want.

I have closed all fixed issues in a bulk operation. The issues marked as
"won't fix" or "not a problem" or "later" or "incomplete" have not been
touched.

Thomas

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

Re: Commons-Math release schedule

2012-03-24 Thread Luc Maisonobe 
Le -10/01/-28163 20:59, Hassan Siddiqui a écrit :
> Dear Commons-Math developers

Hi Hassan,

> 
> My name is Hassan Siddiqui and I am working on a Java scientific project
> that involves a significant amount of numerical analysis code. There are
> some 300+ developers and scientist involved in this project.

I guess I (and Gilles even more than me) know which project you are
talking about ...

> 
> We are using Commons-Math already to an extent but we do intend to be
> more involved.

Fine.

> 
> But one question I would like to ask is what is the process for
> arranging for a new release of Commons-Math. I ask because we have
> 6-month release schedule for our mathematical and utility library, which
> makes use of Commons Math, and we would like to see whether we can have
> releases of Commons Math that could fit that release cycle.

Yes. We have not been very good at this for the last release and it was
way too late. However, we do want to be more in line with the "release
early, really often" credo.

What is most needed is help in resolving the issues that are registered
in our JIRA tracking system
(). Opening new issues also
help improving the product, of course, but help in solving them is most
wanted.

As far as simple issues are concerned, they can be dicussed on the JIRA
tracker itself, and patches can be attached (not forgetting to check the
box allowing us to include the patch in the main code). Testing the
already provided patch and cleaning them so they do have appropriate
comments, javadocs and test cases helps. When discussion on issues is
too long, it is better to switch the discussion to the developers
mailing list, as it is a more appropriate place for this.

When the component has reached a state where another release is worth
doing, then asking for such a release on the dev list and helping in
freezing the code and polishing it is greatly appreciated.

> 
> We are more than happy to assist in Commons Math releases, if this helps.

Thanks for your help.

Luc

> 
> Regards
> 
> -Hassan.
> 
> 
> 
> This message and any attachments are intended for the use of the
> addressee or addressees only. The unauthorised disclosure, use,
> dissemination or copying (either in whole or in part) of its content is
> not permitted. If you received this message in error, please notify the
> sender and delete it from your system. Emails can be altered and their
> integrity cannot be guaranteed by the sender.
> 
> Please consider the environment before printing this email.
> 
> 


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

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

2012-03-24 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-exec-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-exec-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-exec-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/exec/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/exec/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-exec-test/gump_work/build_apache-commons_commons-exec-test.html
Work Name: build_apache-commons_commons-exec-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 24 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/exec/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/exec]
M2_HOME: /opt/maven2
-
FOO..
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 
(Exit value: 143)
Process completed in 2020 millis; below is its output
Process timed out and was killed.
Executing [sh, -c, src/test/scripts/invoker.sh]
invoker.sh -- going to start daemon process
invoker.sh --  daemon process was started
cd: 21: can't cd to ../../../target
Process completed in 8025 millis; above is its output
0: process has terminated: false
1: process has terminated: false
2: process has terminated: false
3: process has terminated: false
4: process has terminated: false
5: process has terminated: false
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.020 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.027 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.024 ms
Process completed in 2004 millis; below is its output
Process timed out and was killed by watchdog.
gdal_translate
HDF5:"/home/kk/grass/data/4404.he5"://HDFEOS/GRIDS/OMI_Column_Amount_O3/Data_Fields/ColumnAmountO3/home/kk/4.tif
FOO..
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.814 sec <<< 
FAILURE!

Results :

Failed tests: 
  testExec_60(org.apache.commons.exec.DefaultExecutorTest)

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

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

Please refer to 
/srv/gump/public/workspace/apache-commons/exec/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 1 minute 23 seconds
[INFO] Finished at: Sat Mar 24 14:45:10 UTC 2012
[INFO] Final Memory: 25M/65M
[INFO] 
-

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

== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 06001224032012, vmgump.apache.org:vmgump:06001224032012
Gump E-mail Identifier (unique within run) #2.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

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

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

2012-03-24 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-vfs2-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 50 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-vfs2-test :  Apache Commons


Full details are available at:

http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2-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/vfs/gump_mvn_settings.xml]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/vfs/pom.xml
 -INFO- Project Reports in: 
/srv/gump/public/workspace/apache-commons/vfs/core/target/surefire-reports



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-vfs2-test/gump_work/build_apache-commons_commons-vfs2-test.html
Work Name: build_apache-commons_commons-vfs2-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 17 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/vfs/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/apache-commons/vfs]
M2_HOME: /opt/maven2
-
Tests in error: 
  
testDefaultInstance(org.apache.commons.vfs2.test.FileSystemManagerFactoryTestCase):
 Could not create a file system manager of class 
"org.apache.commons.vfs2.impl.StandardFileSystemManager".
  org.apache.commons.vfs2.PatternFileSelectorTest: Could not create a file 
system manager of class 
"org.apache.commons.vfs2.impl.StandardFileSystemManager".
  org.apache.commons.vfs2.FileTypeSelectorTest: Could not create a file system 
manager of class "org.apache.commons.vfs2.impl.StandardFileSystemManager".
  org.apache.commons.vfs2.FileIteratorTest: Could not create a file system 
manager of class "org.apache.commons.vfs2.impl.StandardFileSystemManager".
  
junit.framework.TestSuite@c75e4fc(org.apache.commons.vfs2.test.CacheTestSuite): 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
junit.framework.TestSuite@7e78fc6(org.apache.commons.vfs2.test.CacheTestSuite): 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
testDelegatingBad(org.apache.commons.vfs2.util.DelegatingFileSystemOptionsBuilderTest):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
testConfiguration(org.apache.commons.vfs2.util.DelegatingFileSystemOptionsBuilderTest):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
testDelegatingGood(org.apache.commons.vfs2.util.DelegatingFileSystemOptionsBuilderTest):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
junit.framework.TestSuite@379e8f17(org.apache.commons.vfs2.test.ProviderTestSuite):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
junit.framework.TestSuite@39385660(org.apache.commons.vfs2.test.ProviderTestSuite):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
junit.framework.TestSuite@44a613f8(org.apache.commons.vfs2.test.ProviderTestSuite):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
junit.framework.TestSuite@40589e56(org.apache.commons.vfs2.test.ProviderTestSuite):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
junit.framework.TestSuite@6c69d02b(org.apache.commons.vfs2.provider.ftp.test.FtpProviderTestCase$1):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  
junit.framework.TestSuite@50269997(org.apache.commons.vfs2.test.ProviderTestSuite):
 
org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
  org.apache.commons.vfs2.provider.test.FileObjectSortTestCase: Could not 
create a file system manager of class 
"org.apache.commons.vfs2.impl.StandardFileSystemManager".
  
junit.framework.TestSuite@162db19d(org.ap