Re: [GUMP@vmgump]: Project commons-configuration (in module apache-commons) failed
Which version of JUnit is used by GUMP? According to the Javadocs for
version 4.10, there should be a method TemporaryFolder.newFile() with an
empty argument list.
Oliver
Am 26.12.2011 07:20, schrieb 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-configuration has an issue affecting its community integration.
This issue affects 2 projects,
and has been outstanding for 46 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-configuration : Apache Commons
- commons-configuration-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/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-configuration-*[0-9T].jar] identifier set to
project name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/apache-commons/configuration/pom.xml
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/gump_work/build_apache-commons_commons-configuration.html
Work Name: build_apache-commons_commons-configuration (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 mins 41 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings
/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/apache-commons/configuration]
M2_HOME: /opt/maven2
-
Downloading:
http://localhost:8192/maven2/org/apache/maven/maven-archiver/2.4.1/maven-archiver-2.4.1.jar
Downloading:
http://localhost:8192/maven2/org/easymock/easymock/2.4/easymock-2.4.jar
Downloading:
http://localhost:8192/maven2/biz/aQute/bndlib/1.43.0/bndlib-1.43.0.jar
Downloading:
http://localhost:8192/maven2/org/apache/maven/shared/maven-dependency-tree/1.2/maven-dependency-tree-1.2.jar
Downloading:
http://localhost:8192/maven2/org/apache/felix/org.apache.felix.bundlerepository/1.6.6/org.apache.felix.bundlerepository-1.6.6.jar
Downloading:
http://localhost:8192/maven2/org/osgi/org.osgi.core/4.1.0/org.osgi.core-4.1.0.jar
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.0/plexus-archiver-1.0.jar
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-io/1.0/plexus-io-1.0.jar
[INFO] [bundle:manifest {execution: bundle-manifest}]
[debug] execute contextualize
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 96 resources
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 111 source files to
/srv/gump/public/workspace/apache-commons/configuration/target/test-classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[203,26]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[261,29]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[314,32]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[INFO] 3 errors
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[203,26]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[261,29]
newFile(java.lang.String) i
Re: [math] Strange svn conflict
Hi, and many thanks for your help > > I have a few questions still: > > - Can you run 'svn diff -c r1210359' (against either mirror) and confirm > that that is exactly what you intended to commit? > Done on the EU mirror: the diff file seems OK to me. > > - Why would the N other files have been committed in that revision? > Recall that those files had no text changes and their property lists > were re-set to the values they already had. > I now recall what hapened at that time. As of r1206451 (see MATH-711), interface files xxxDistribution.java and default implementation xxxDistributionImpl.java have been merged. I did this piece of refactoring with Eclipse, and realized later that during the process, all SVN properties had gone. Or so it appeared in Eclipse (since you wrote that the properties had not really gone). So r1210359 had two purposes 1. restore the SVN properties, 2. solve MATH-715 (which resulted in "real" modifications of PascalDistribution.java). I hope I am not the one to blame for the current mess. I now realize that I should have operated the refactoring outside Eclipse, using SVN to remove the interface files, and rename the implementation files. Also I should have used SVN as a command-line tool to check for the presence of the SVN properties. Again, I hope I did not cause too much damage. What can I do to try and repair that? > > - How to reproduce the errors you saw? Can you show the output of `svn > diff` at the time of a failed commit attempt? > I hope this mailing list allows for attachements, in which case you will find attached the patch I've been trying to commit for several days now. It is a rather large patch, but I don't think that this is the cause for our current troubles, since I've tried to commit only a small piece and it did not work either. Just to be sure the trouble was still occuring, I've just tried to commit these changes, and here is what I get. org.tigris.subversion.javahl.ClientException: Merge conflict during commit svn: Commit failed (details follow): svn: File or directory 'main/java/org/apache/commons/math/distribution/BinomialDistribution.java' is out of date; try updating svn: resource out of date; try updating > > - You used "SVN/1.6.15 SVNKit/1.3.5 (http://svnkit.com/) r7406" in that > commit. The servers ran 1.7.0. My client was 1.7.0 too. > Actually, I'm using this time svn --version svn, version 1.6.17 (r1128011) compiled Aug 25 2011, 17:51:49 Should I move to svn 1.7 ? > > As to the diagnosis: > > - The non-functional propchanges should have been collapsed and removed > before or during the commit. This should happen within the FS > backend: the changed-paths information should not list such files with > 'prop_mod=TRUE'. I'm not sure if other layers should do such > collapsing too. > I'm sorry this is far out of my league... But I do hope that I've answered your questions. > > Thanks, > > Daniel > Thank *you*, Sébastien - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [math] Strange svn conflict
> [...] > I hope I am not the one to blame for the current mess. I now realize > that I should have operated the refactoring outside Eclipse, using SVN > to remove the interface files, and rename the implementation files. > Also I should have used SVN as a command-line tool to check for the > presence of the SVN properties. Again, I hope I did not cause too much > damage. What can I do to try and repair that? This problem can, and did, occur even without using Eclipse. > [...] Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [GUMP@vmgump]: Project commons-configuration (in module apache-commons) failed
2011/12/26 Oliver Heger :
> Which version of JUnit is used by GUMP? According to the Javadocs for
> version 4.10, there should be a method TemporaryFolder.newFile() with an
> empty argument list.
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/details.html
says "junit-26122011.jar"
and that that jar comes from junit project at Gump,
http://vmgump.apache.org/gump/public/junit/junit/index.html
The git update log for junit project
http://vmgump.apache.org/gump/public/junit/gump_work/update_junit.html
says at the end
[[[
Pull is not possible because you have unmerged files.
Please, fix them up in the work tree, and then use 'git add/rm '
as appropriate to mark resolution, or use 'git commit -a'.
]]]
Is that of any concern?
I agree that
https://github.com/KentBeck/junit/blob/master/src/main/java/org/junit/rules/TemporaryFolder.java
has newFile(), so this issue is strange.
>
> Oliver
>
> Am 26.12.2011 07:20, schrieb 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-configuration has an issue affecting its community
>> integration.
>> This issue affects 2 projects,
>> and has been outstanding for 46 runs.
>> The current state of this project is 'Failed', with reason 'Build Failed'.
>> For reference only, the following projects are affected by this:
>> - commons-configuration : Apache Commons
>> - commons-configuration-test : Apache Commons
>>
>>
>> Full details are available at:
>>
>> http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/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-configuration-*[0-9T].jar] identifier
>> set to project name
>> -DEBUG- (Apache Gump generated) Apache Maven Settings in:
>> /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
>> -INFO- Failed with reason build failed
>> -DEBUG- Maven POM in:
>> /srv/gump/public/workspace/apache-commons/configuration/pom.xml
>> -DEBUG- Extracted fallback artifacts from Gump Repository
>>
>>
>>
>> The following work was performed:
>>
>> http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/gump_work/build_apache-commons_commons-configuration.html
>> Work Name: build_apache-commons_commons-configuration (Type: Build)
>> Work ended in a state of : Failed
>> Elapsed: 3 mins 41 secs
>> Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings
>> /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
>> package
>> [Working Directory:
>> /srv/gump/public/workspace/apache-commons/configuration]
>> M2_HOME: /opt/maven2
>> -
>> Downloading:
>> http://localhost:8192/maven2/org/apache/maven/maven-archiver/2.4.1/maven-archiver-2.4.1.jar
>> Downloading:
>> http://localhost:8192/maven2/org/easymock/easymock/2.4/easymock-2.4.jar
>> Downloading:
>> http://localhost:8192/maven2/biz/aQute/bndlib/1.43.0/bndlib-1.43.0.jar
>> Downloading:
>> http://localhost:8192/maven2/org/apache/maven/shared/maven-dependency-tree/1.2/maven-dependency-tree-1.2.jar
>>
>>
>>
>>
>>
>> Downloading:
>> http://localhost:8192/maven2/org/apache/felix/org.apache.felix.bundlerepository/1.6.6/org.apache.felix.bundlerepository-1.6.6.jar
>> Downloading:
>> http://localhost:8192/maven2/org/osgi/org.osgi.core/4.1.0/org.osgi.core-4.1.0.jar
>> Downloading:
>> http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.0/plexus-archiver-1.0.jar
>>
>>
>>
>> Downloading:
>> http://localhost:8192/maven2/org/codehaus/plexus/plexus-io/1.0/plexus-io-1.0.jar
>>
>> [INFO] [bundle:manifest {execution: bundle-manifest}]
>> [debug] execute contextualize
>> [INFO] [resources:testResources {execution: default-testResources}]
>> [INFO] Using 'iso-8859-1' encoding to copy filtered resources.
>> [INFO] Copying 96 resources
>> [INFO] Copying 2 resources
>> [INFO] Copying 2 resources to META-INF
>> [INFO] [compiler:testCompile {execution: default-testCompile}]
>> [INFO] Compiling 111 source files to
>> /srv/gump/public/workspace/apache-commons/configuration/target/test-classes
>> [INFO] -
>> [ERROR] COMPILATION ERROR :
>> [INFO] -
>> [ERROR]
>> /srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[203,26]
>> newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be
>> applied to ()
>> [ERROR]
>> /srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[261,29]
>> newFile(java.lang.String) in
[GUMP@vmgump]: Project commons-configuration (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-configuration 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-configuration : Apache Commons
- commons-configuration-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/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-configuration-*[0-9T].jar] identifier set to
project name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/apache-commons/configuration/pom.xml
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/gump_work/build_apache-commons_commons-configuration.html
Work Name: build_apache-commons_commons-configuration (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 mins 40 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings
/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/apache-commons/configuration]
M2_HOME: /opt/maven2
-
Downloading:
http://localhost:8192/maven2/org/apache/maven/maven-archiver/2.4.1/maven-archiver-2.4.1.jar
Downloading:
http://localhost:8192/maven2/org/easymock/easymock/2.4/easymock-2.4.jar
Downloading:
http://localhost:8192/maven2/biz/aQute/bndlib/1.43.0/bndlib-1.43.0.jar
Downloading:
http://localhost:8192/maven2/org/apache/maven/shared/maven-dependency-tree/1.2/maven-dependency-tree-1.2.jar
Downloading:
http://localhost:8192/maven2/org/apache/felix/org.apache.felix.bundlerepository/1.6.6/org.apache.felix.bundlerepository-1.6.6.jar
Downloading:
http://localhost:8192/maven2/org/osgi/org.osgi.core/4.1.0/org.osgi.core-4.1.0.jar
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.0/plexus-archiver-1.0.jar
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-io/1.0/plexus-io-1.0.jar
[INFO] [bundle:manifest {execution: bundle-manifest}]
[debug] execute contextualize
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 96 resources
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 111 source files to
/srv/gump/public/workspace/apache-commons/configuration/target/test-classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[203,26]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[261,29]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[314,32]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[INFO] 3 errors
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[203,26]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[261,29]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[314,32]
newFile(java.lang.String) in org.junit.rules.Tem
Re: [Graph] On graph weight type(s)
Hi Claudio!
just make your proposal and attach it to a jira Issue :)
Hope to hear from you soon, all the best!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Dec 23, 2011 at 6:02 PM, wrote:
> Hi,
>
> I like the idea of external weights. Actually that could work for other
> properties of the graph as well. I see a couple of use cases there.
>
> As for lazy implementations, I like them too but with much less priority
> for now.
>
> Anyway, first things first: guys should I infer an implicit 'yes' from
> your answers and go ahead with the proposed change for weights? Anyone
> else has a word on this? I am just applying some lazy pattern here --
> discuss before coding ;)
>
> Claudio
>
>
>> On 23 December 2011 10:38, Simone Tripodi
>> wrote:
>>
>>> Hi Matthew!
>>>
>>
>>
>>> Usually algorithms (like Dijkstra) already have clear enunciates and
>>> steps are known, so we could safety expose 1 APIs that hide all that
>>> details to clients wrapping your proposals.
>>>
>>
>> That's what façades are for. I totally agree with providing users with
>> utility methods that hide all the guts.
>>
>>
>>>
>>> WDYT? Thanks again!!!
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Fri, Dec 23, 2011 at 10:44 AM, Matthew Pocock
>>> wrote:
>>> > Hi Simo,
>>> >
>>> > I guess the 5 minutes to run example would be:
>>> >
>>> > ShortestPathFunction.dijkstra
>>> > .makeResult(graph, EdgeWeight.forWeightedEdge, Monotonic.sumDouble)
>>> > .findShortestPath(source, target);
>>> >
>>> > I was assuming that there would be standard pallets of all the
>>> strategies
>>> > available statically in the obvious places. Actually, now I see the
>>> code
>>> > written out in full like that, I'd perhaps consider renaming
>>> makeResult
>>> to
>>> > `calculate` or `prepare` or some other verb.
>>> >
>>> > Matthew
>>> >
>>> > On 23 December 2011 08:47, Simone Tripodi
>>> wrote:
>>> >
>>> >> Hi Matthew!
>>> >>
>>> >> at a first looks it is really interesting, just give me the time to
>>> >> digest because at the same time I had the feeling of a little
>>> >> over-engineering activity, I am worried that "5 minutes to run" users
>>> >> would find it not so immediate.
>>> >>
>>> >> Thanks for providing stuff to learn from!
>>> >> All the best,
>>> >> -Simo
>>> >>
>>> >> http://people.apache.org/~simonetripodi/
>>> >> http://simonetripodi.livejournal.com/
>>> >> http://twitter.com/simonetripodi
>>> >> http://www.99soft.org/
>>> >>
>>> >>
>>> >>
>>> >> On Thu, Dec 22, 2011 at 6:25 PM, Matthew Pocock
>>> >> wrote:
>>> >> > Hi,
>>> >> >
>>> >> > Just thought I'd throw something out here. My experience is that I
>>> often
>>> >> > take the same graph (as in the exact same data, same objects) but
>>> at
>>> >> > different times want to use different weights. So, rather than
>>> having
>>> >> Edge
>>> >> > extend Weighted, I'd factor weights out into their own
>>> interface:
>>> >> >
>>> >> > /**
>>> >> > * An edge weight function.
>>> >> > *
>>> >> > * note: perhaps this should more generally just be a Function1>> B>, if
>>> >> > we have such a thing handy.
>>> >> > *
>>> >> > * @tparam E edge type
>>> >> > * @tparam W weight type
>>> >> > */
>>> >> > public interface EdgeWeight {
>>> >> > public W getWeight(E: Edge);
>>> >> > }
>>> >> >
>>> >> > /**
>>> >> > * A combination of a monoid and comparator that satisfy
>>> monotinicity
>>> of
>>> >> > the addition operation with respect to the comparator.
>>> >> > *
>>> >> > * ∀a: m.compare(m.zero, a) <= 0
>>> >> > * ∀a,b: m.compare(a, m.append(a, b)) <= 0
>>> >> > */
>>> >> > public interface Monotonic extends Monoid, Comparator
>>> >> >
>>> >> > Also, some algorithms calculate all shortest paths at once, while
>>> others
>>> >> > calculate them individually and independently. It's probably even
>>> >> possible
>>> >> > to calculate some lazily. So, the interfaces for shortest paths
>>> should
>>> >> > decouple setting up a strategy for all shortest paths from an
>>> object
>>> that
>>> >> > can be used to fetch a specific shortest path.
>>> >> >
>>> >> > /**
>>> >> > * An algorithm for finding shortest paths between vertices of a
>>> graph,
>>> >> > given some edge weighting function and
>>> >> > * a well-behaved combinator for edges between connected vertices.
>>> >> > */
>>> >> > public interface ShortestPathFunction>> >> Edge,
>>> >> > G extends DirectedGraph, W> {
>>> >> > public ShortestPathResult makeResult(G graph,
>>> EdgeWeight>> W>
>>> >> > weighting, Monotonic combineWith);
>>> >> > }
>>> >> >
>>> >> > /**
>>> >> > * The shortest paths between vertices in a graph.
>>> >> > */
>>> >> > public interface ShortestPathResult>> Edge,
>>> >> W>
>>> >> > {
>>> >> > public WeightedPath findShortestPath(V source, V target);
>>> >> > }
>>> >> >
>>
[CLI] discuss experimental CLI binder APIs
Hi all guys, I have been experimenting a new set of CLI APIs outside the ASF, taking the best from existing CLI and some other non-ASF libraries, mainly Cédric's JCommander[1], the purposes are: * using fluent APIs; * simplify the Options building; * reducing the number of involved components; * triggering actions when options are parsed; A simple (not working) APIs usage can be found on the GitHub's space[2]. So, I would much more than happy to move the effort to [commons] and donate the prototype, if people think it would be a worth give a try to innovate [cli]. Otherwise, I will have to finalize it outside the ASF. Feedbacks are welcome, many thanks in advance! -Simo [1] http://jcommander.org/ [2] http://s.apache.org/xS http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[CLI] Enhancement ideas [Was: WELCOME to dev@commons.apache.org]
Changing the subject so Jay's email gets noticed. Hen On Wed, Dec 21, 2011 at 3:24 PM, Jay Vyas wrote: > Hi guys : I wanted to add some features to CLI > > 1) Options iterators , make them generic > 2) Add an option for setting ALL options to mandatory. > 3) Add an option to add groups, using the addOption api, the same way we > add options. > > In any case - would such contirbutions be welcome.. and if so - who would i > push commits to ? - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [CLI] discuss experimental CLI binder APIs
Hi Simone, I don't know how others make use of CLI, what I'm going to discuss is only my personal point of view. I have to do with the command line stuff one time per project (more or less), and I have to admit that the CLI api (even though is a good one) is every time hard to apply. This is probably due the sporadic use. Conversely, JCommander has a very low learning curve. The example you provided is good enough, but it is still far away in terms of learning curve. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 26 December 2011 22:35, Simone Tripodi wrote: > Hi all guys, > I have been experimenting a new set of CLI APIs outside the ASF, > taking the best from existing CLI and some other non-ASF libraries, > mainly Cédric's JCommander[1], the purposes are: > > * using fluent APIs; > * simplify the Options building; > * reducing the number of involved components; > * triggering actions when options are parsed; > > A simple (not working) APIs usage can be found on the GitHub's space[2]. > > So, I would much more than happy to move the effort to [commons] and > donate the prototype, if people think it would be a worth give a try > to innovate [cli]. > Otherwise, I will have to finalize it outside the ASF. > Feedbacks are welcome, many thanks in advance! > -Simo > > [1] http://jcommander.org/ > [2] http://s.apache.org/xS > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [CLI] discuss experimental CLI binder APIs
Hola Izio! > Conversely, JCommander has a very low learning curve. sure I'm JCommander user myself, but that are the reason why that approach cannot universally applied * it's not complete (yet) since it doesn't support Java-alike dynamic options such as `-Dproperty=value` (they need to be collected in a Properties/Map instance) * it forces all parameters to be collected in POJOs - that is not universally good (hey could be used to be passed in a pom.xml); * it doesn't support Posix parser; * wrong converters binding can be detected at runtime only - since they are expressed in annotations, nothing can be done from the compiler side; * it would be useful performing blocking actions when detecting some parameters, i.e. like --help that prints the usage message and exit; * ... shall I continue? :) > The example you provided is good enough, but it is still far away in terms > of learning curve. UH... Seriously? Being fluent-APIs should be at least easier of current [cli] APIs... Thanks for the feedbacks! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GUMP@vmgump]: Project commons-sanselan-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-sanselan-test has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 13 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-sanselan-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-sanselan-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/sanselan/gump_mvn_settings.xml]
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/sanselan/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/apache-commons/sanselan/pom.xml
-INFO- Project Reports in:
/srv/gump/public/workspace/apache-commons/sanselan/target/surefire-reports
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-sanselan-test/gump_work/build_apache-commons_commons-sanselan-test.html
Work Name: build_apache-commons_commons-sanselan-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 29 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings
/srv/gump/public/workspace/apache-commons/sanselan/gump_mvn_settings.xml test
[Working Directory: /srv/gump/public/workspace/apache-commons/sanselan]
M2_HOME: /opt/maven2
-
Running org.apache.commons.sanselan.formats.jpeg.exif.TextFieldTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.561 sec
Running
org.apache.commons.sanselan.formats.jpeg.exif.WriteExifMetadataExampleTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.507 sec
Running org.apache.commons.sanselan.formats.jpeg.exif.ExifRewriteTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.619 sec
Running org.apache.commons.sanselan.formats.jpeg.exif.MakerNoteFieldTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.581 sec
Running org.apache.commons.sanselan.formats.jpeg.exif.AsciiFieldTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.086 sec
Running org.apache.commons.sanselan.formats.jpeg.exif.ExifDumpTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.486 sec
Running org.apache.commons.sanselan.formats.jpeg.exif.WriteTagsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.apache.commons.sanselan.formats.jpeg.exif.GpsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.447 sec
Running org.apache.commons.sanselan.formats.jpeg.iptc.IptcDumpTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.468 sec
Running org.apache.commons.sanselan.formats.jpeg.iptc.IptcUpdateTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.665 sec
Running org.apache.commons.sanselan.common.BinaryFileFunctionsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec
Running org.apache.commons.sanselan.common.RationalNumberTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running org.apache.commons.sanselan.common.bytesource.ByteSourceImageTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.485 sec
Running org.apache.commons.sanselan.common.bytesource.ByteSourceDataTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.156 sec
Running org.apache.commons.sanselan.color.ColorConversionsTest
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec <<<
FAILURE!
Results :
Failed tests:
testCMYKtoRGB(org.apache.commons.sanselan.color.ColorConversionsTest): {C: 0.0,
M: 0.0, Y: 64.0, K: 64.0} expected: but was:
Tests run: 86, 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/sanselan/target/surefire-reports for
the individual test results.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 2 minutes 28 seconds
[INFO] Finished at: Tue Dec 27 02:22:12 UTC 2011
[INFO] Final Memory: 34M/83M
[INFO]
Re: [GUMP@vmgump]: Project commons-configuration (in module apache-commons) failed
On 2011-12-26, Konstantin Kolinko wrote: > 2011/12/26 Oliver Heger : >> Which version of JUnit is used by GUMP? According to the Javadocs for >> version 4.10, there should be a method TemporaryFolder.newFile() with an >> empty argument list. > http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/details.html > says "junit-26122011.jar" > and that that jar comes from junit project at Gump, > http://vmgump.apache.org/gump/public/junit/junit/index.html In theory it is the tip of JUnit's master branch. > The git update log for junit project > http://vmgump.apache.org/gump/public/junit/gump_work/update_junit.html > says at the end > [[[ > Pull is not possible because you have unmerged files. > Please, fix them up in the work tree, and then use 'git add/rm ' > as appropriate to mark resolution, or use 'git commit -a'. > ]]] > Is that of any concern? Probably. I'm not sure how long this has been the case. We may be trailing behing JUnit's tip. For now I have purged the working copy of JUnit and the next run will check out a fresh one - which I hope will resolve the issue for configuration. Later (I intend to have a slow week) I'll try to figure out why we've gotten into this situation. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GUMP@vmgump]: Project commons-configuration (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-configuration has an issue affecting its community integration.
This issue affects 2 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-configuration : Apache Commons
- commons-configuration-test : Apache Commons
Full details are available at:
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/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-configuration-*[0-9T].jar] identifier set to
project name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/apache-commons/configuration/pom.xml
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/gump_work/build_apache-commons_commons-configuration.html
Work Name: build_apache-commons_commons-configuration (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 mins 46 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings
/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/apache-commons/configuration]
M2_HOME: /opt/maven2
-
Downloading:
http://localhost:8192/maven2/org/apache/maven/maven-archiver/2.4.1/maven-archiver-2.4.1.jar
Downloading:
http://localhost:8192/maven2/org/easymock/easymock/2.4/easymock-2.4.jar
Downloading:
http://localhost:8192/maven2/biz/aQute/bndlib/1.43.0/bndlib-1.43.0.jar
Downloading:
http://localhost:8192/maven2/org/apache/maven/shared/maven-dependency-tree/1.2/maven-dependency-tree-1.2.jar
Downloading:
http://localhost:8192/maven2/org/apache/felix/org.apache.felix.bundlerepository/1.6.6/org.apache.felix.bundlerepository-1.6.6.jar
Downloading:
http://localhost:8192/maven2/org/osgi/org.osgi.core/4.1.0/org.osgi.core-4.1.0.jar
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-archiver/1.0/plexus-archiver-1.0.jar
Downloading:
http://localhost:8192/maven2/org/codehaus/plexus/plexus-io/1.0/plexus-io-1.0.jar
[INFO] [bundle:manifest {execution: bundle-manifest}]
[debug] execute contextualize
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 96 resources
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 111 source files to
/srv/gump/public/workspace/apache-commons/configuration/target/test-classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[203,26]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[261,29]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[ERROR]
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[314,32]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
[INFO] 3 errors
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[203,26]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[261,29]
newFile(java.lang.String) in org.junit.rules.TemporaryFolder cannot be applied
to ()
/srv/gump/public/workspace/apache-commons/configuration/src/test/java/org/apache/commons/configuration/TestFileConfiguration.java:[314,32]
newFile(ja
[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 303 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: 12 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/proxy] M2_HOME: /opt/maven2 - Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.factory.util.TestMethodSignature Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.proxy.provider.TestConstantProvider Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 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.014 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 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.015 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.19 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.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: 11 seconds [INFO] Finished at: Tue Dec 27 07:29:41 UTC 2011 [INFO] Final Memory: 24M/58M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml - Atom: http://vmgump.apache.o
