Re: [VOTE] graduate [graph] as a proper component

[Phil Steitz]

On 12/19/11 12:52 AM, Phil Steitz wrote:
> On 12/19/11 12:35 AM, Simone Tripodi wrote:
>> On Mon, Dec 19, 2011 at 8:00 AM, Luc Maisonobe  wrote:
>>> Le 18/12/2011 23:10, James Carman a écrit :
 My concern is that the momentum dies off after we get it in proper and then
 we have to demote it later.
>>> I don't see any problem with this. For now the component seems to have a
>>> community, hence it is worht promoting it (this is a +1 from me). If
>>> later on the community fades away, then the component will move away,
>>> it's OK.
>>>
>> Indeed, thanks Luc, I don't see either what the issue is on managing
>> components lifecycle - if people lost interest on it, just open a new
>> vote to move it back to dormant.
> Technically, I don't think we ever agreed to change the lifecycle to
> allow components to go from proper to dormant.  Dead proper
> components go to the Attic.  We talked about extending the dormant
> category to include the various zombies that we still have listed as
> proper, but did not agree on it [1].  As of now, dormant only
> applies to sandbox components and we should not promote things that
> are likely to go dormant.  The sandbox exists to allow us to
> experiment with things and try to grow a community around ideas. 
> When we graduate something, we should be confident that it is going
> to become an active Commons component; otherwise it should stay in
> the sandbox.  I don't buy the argument that being in the sandbox
> somehow limits "visibility."  The sandbox is actually easier for
> non-Commons committers to get access to and has just as much
> "visibility" as proper among the Commons community.  The only
> constraint is that you can't cut releases from the sandbox; but that
> is not an issue in this case.
>
> Phil

Oops, forgot the link:

[1] http://markmail.org/message/anjdpx2s2cyojc65
>> we can bee conservative but dynamic at the same time.
>>
>> 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
>>
>>


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

Re: [VOTE] graduate [graph] as a proper component

[Phil Steitz]

On 12/19/11 12:35 AM, Simone Tripodi wrote:
> On Mon, Dec 19, 2011 at 8:00 AM, Luc Maisonobe  wrote:
>> Le 18/12/2011 23:10, James Carman a écrit :
>>> My concern is that the momentum dies off after we get it in proper and then
>>> we have to demote it later.
>> I don't see any problem with this. For now the component seems to have a
>> community, hence it is worht promoting it (this is a +1 from me). If
>> later on the community fades away, then the component will move away,
>> it's OK.
>>
> Indeed, thanks Luc, I don't see either what the issue is on managing
> components lifecycle - if people lost interest on it, just open a new
> vote to move it back to dormant.

Technically, I don't think we ever agreed to change the lifecycle to
allow components to go from proper to dormant.  Dead proper
components go to the Attic.  We talked about extending the dormant
category to include the various zombies that we still have listed as
proper, but did not agree on it [1].  As of now, dormant only
applies to sandbox components and we should not promote things that
are likely to go dormant.  The sandbox exists to allow us to
experiment with things and try to grow a community around ideas. 
When we graduate something, we should be confident that it is going
to become an active Commons component; otherwise it should stay in
the sandbox.  I don't buy the argument that being in the sandbox
somehow limits "visibility."  The sandbox is actually easier for
non-Commons committers to get access to and has just as much
"visibility" as proper among the Commons community.  The only
constraint is that you can't cut releases from the sandbox; but that
is not an issue in this case.

Phil
> we can bee conservative but dynamic at the same time.
>
> 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
>
>


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

Re: [VOTE] graduate [graph] as a proper component

[Simone Tripodi]

On Mon, Dec 19, 2011 at 8:00 AM, Luc Maisonobe  wrote:
> Le 18/12/2011 23:10, James Carman a écrit :
>> My concern is that the momentum dies off after we get it in proper and then
>> we have to demote it later.
>
> I don't see any problem with this. For now the component seems to have a
> community, hence it is worht promoting it (this is a +1 from me). If
> later on the community fades away, then the component will move away,
> it's OK.
>

Indeed, thanks Luc, I don't see either what the issue is on managing
components lifecycle - if people lost interest on it, just open a new
vote to move it back to dormant.
we can bee conservative but dynamic at the same time.

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: [sanselan] rename proposals

[Simone Tripodi]

sure it makes sense, once broken, break as needed
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Mon, Dec 19, 2011 at 7:30 AM, Damjan Jovanovic  wrote:
> +1
> and if we're breaking binary compatibility this way, I am breaking it in
> other ways too.
>
> On Sun, Dec 18, 2011 at 11:18 PM, Gary Gregory wrote:
>
>> Hi:
>>
>> I propose the following package renames:
>>
>> org.apache.commons.sanselan.common.byteSources ->
>> org.apache.commons.sanselan.common.bytesource
>> org.apache.commons.sanselan.formats.jpeg.exifRewrite ->
>> org.apache.commons.sanselan.formats.jpeg.exif
>> org.apache.commons.sanselan.sampleUsage ->
>> org.apache.commons.sanselan.examples
>>
>> For class names, there is a current mix of camel case and CAPS, sometimes
>> in the same package: GifImageParser and GIFHeaderInfo.
>>
>> I propose to camel case all class names.
>>
>> Gary
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>> Spring Batch in Action: http://bit.ly/bqpbCK
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>

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

Re: [sanselan] how to build a release

[Phil Steitz]

On 12/17/11 7:55 AM, Gary Gregory wrote:
> Another slightly odd looking thing is to have
> org.apache.commons.sanselan.common as a package. There is also a util
> packages. I wonder I this stuff can be moved around in some way that
> looks and feels less scattered.
>
> Op Ed:
> On a different tak, personally, I've never liked sanselan as a package
> in the [commons] universe. I want to just see org.apache.commons.image
> or some such. Just like we have .io, .lang, .net, and so on. All
> commons packages are functional IIRC, not some goofy name.

+1 - we talked about this IIRC when [sanselan] was incubating and
decided not to force the name change.  I think it was to make it
easier for then current users and developers to keep engagement /
momentum.  I think its worth asking again now that it has moved into
Commons and repackaging is going to be necessary anyway.  Why not
just change to o.a.c.image?

Phil
>
> Gary
>
> On Dec 17, 2011, at 8:48, sebb  wrote:
>
>> On 17 December 2011 13:09, Gary Gregory  wrote:
>>> On Dec 17, 2011, at 5:58, sebb  wrote:
>>>
 On 17 December 2011 06:05, Damjan Jovanovic  wrote:
> On Sat, Dec 17, 2011 at 1:35 AM, Gary Gregory 
> wrote:
>
>> On Fri, Dec 16, 2011 at 5:54 PM, sebb  wrote:
>>
>>> On 16 December 2011 20:49, Gary Gregory  wrote:
 On Fri, Dec 16, 2011 at 1:43 PM, sebb  wrote:

> On 16 December 2011 17:27, Simone Tripodi 
> wrote:
>> AH yes, that's because Sanselan came from the Incubator and hasn't
>> been updated yet :P
> Yes - that's good (as it happens).
>
> The previous (incubator) Maven release was under the groupId
> org.apache.sanselan, and the package was also o.a.sanselan
>
> The package name has been changed already, so we can change the Maven
> groupId to o.a.commons, which will automatically give Nexus access.
>
 I see "package org.apache.sanselan" all over in
 https://svn.apache.org/repos/asf/commons/proper/sanselan/trunk

 Do I have the right project checked out?
>>> Oops!  Yes, you do.
>>>
>>> Sorry, got that wrong - I thought I had checked the current package.
>>>
>>> In which case, we either need to
>>> * keep the package name & make another release under the old Maven
>> coords,
>>> or
>>> * change the package to o.a.c and make a release under Maven o.a.c.
>>>
>>  IMO "change the package to o.a.c", should be done now.
>>
>> I'll could it unless you or anyone gets to it first, or makes other kinds
>> of noises.
>>
>>
> If a 1.0 release is necessary, I'd like to make other changes too before
> that.
 If the package name is changed to o.a.commons, the
>>> Note that there are other package name oddities like mixed case
>>> package names which should be all lower case.
>> +1 to fixing those - it's obvious what the proper solution is there.
>>
>> The tricky bit is getting the API correct ... or at least sufficiently
>> correct that a further break in binary compat. is very unlikely.
>>
>>> Gary
>>>
 Commons versioning
 guidelines require a major version bump.
 Probably a good idea anyway to release as 1.0 to show that the
 incubation stage is finally over.

 The package name change means there's no need to keep binary
 compatibility - users will have to edit and recompile anyway.
 But ideally fix all broken bits of the API at once to avoid having to
 change the package name again in the future.

> As for the Java 1.5 update, that would make a Java ME port harder to do,
> but I'd rather have an Android port anyway.
>
> Damjan
 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org

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


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

Re: [VOTE] graduate [graph] as a proper component

[Luc Maisonobe]

Le 19/12/2011 07:16, Phil Steitz a écrit :
> 
> 
> 
> 
> On Dec 18, 2011, at 3:10 PM, James Carman
>  wrote:
> 
>> My concern is that the momentum dies off after we get it in proper
>> and then we have to demote it later.  I am interested, but I don't
>> know how much hands-on time I'll have for it.  If we get it to a
>> mature state and let it prove itself a bit first, I think it has a
>> better chance.  That's just my opinion and obviously there are many
>> others who disagree so I don't even know why I'm taking the time to
>> type this on my phone. Probably just looking for an excuse to play
>> with ice cream sandwich.   :)
> 
> I agree with you but with maybe a different emphasis.  The
> requirement we used was three committers willing to actively help
> move the component along.  I don't see being ready for a release as a
> hard requirement, but I do see the need for more than one active
> committer and Ideally 3 or more before something gets promoted.  Are
> the people voting +1 planning to commit on [graph]?  Are there
> others?

I voted +1 despite I don't intend to commit yet.

Luc

> 
> Phil
>> On Dec 18, 2011 3:22 PM, "Simone Tripodi"
>>  wrote:
>> 
>>> Hi James!
>>> 
>>> can't we prepare the release in proper? Maybe it would be easier 
>>> attracting more people interested on contributing and get it
>>> ready for a release quicker...
>>> 
>>> Best, -Simo
>>> 
>>> http://people.apache.org/~simonetripodi/ 
>>> http://simonetripodi.livejournal.com/ 
>>> http://twitter.com/simonetripodi http://www.99soft.org/
>>> 
>>> 
>>> 
>>> On Sun, Dec 18, 2011 at 9:18 PM, James Carman 
>>>  wrote:
 Can we get it ready for release first? On Dec 18, 2011 3:13 PM,
 "Simone Tripodi" 
>>> wrote:
 
> Hi all, Since I proposed[1] to resurrect commons-graph from
> dormant to sandbox, there's been not only my personal
> activity, but we have recorded a good number of discussions
> on the ML and received contributions on JIRA[2], involving
> not only PMC such as James but also from users, such as
> Claudio Squarcella, Matthew Pococ and Marco Speranza. I think
> we have now, including users that took part with the
> unbinding vote in the proposal, a good number of people
> interested in this commons component and see it released,
> that's why today I'm calling for a vote to accept it in the
> propers. So please cast your vote!
> 
> [ ] +1 Accept [graph] as a proper component [ ] +/- 0 uhm... 
> [ ] -1 Don't accept it - and please explain why
> 
> Open will stay open for 72h and closes on Wed 21th, 8:15 PM
> CET.
> 
> Many thanks in advance, all the best! -Simo
> 
> [1] http://markmail.org/message/mlvqiqhqm2nqhofr [2] 
> SANDBOX-334 SANDBOX-336 SANDBOX-338 SANDBOX-332 SANDBOX-333 
> SANDBOX-335 SANDBOX-337 SANDBOX-344 SANDBOX-345
> 
> 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
> 
> 
>>> 
>>> -
>>>
>>> 
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>>> 
> 
> -
>
> 
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


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

Re: [VOTE] graduate [graph] as a proper component

[Luc Maisonobe]

Le 18/12/2011 23:10, James Carman a écrit :
> My concern is that the momentum dies off after we get it in proper and then
> we have to demote it later.

I don't see any problem with this. For now the component seems to have a
community, hence it is worht promoting it (this is a +1 from me). If
later on the community fades away, then the component will move away,
it's OK.

Luc

> I am interested, but I don't know how much
> hands-on time I'll have for it.  If we get it to a mature state and let it
> prove itself a bit first, I think it has a better chance.  That's just my
> opinion and obviously there are many others who disagree so I don't even
> know why I'm taking the time to type this on my phone. Probably just
> looking for an excuse to play with ice cream sandwich.   :)
> On Dec 18, 2011 3:22 PM, "Simone Tripodi"  wrote:
> 
>> Hi James!
>>
>> can't we prepare the release in proper? Maybe it would be easier
>> attracting more people interested on contributing and get it ready for
>> a release quicker...
>>
>> Best,
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> On Sun, Dec 18, 2011 at 9:18 PM, James Carman
>>  wrote:
>>> Can we get it ready for release first?
>>> On Dec 18, 2011 3:13 PM, "Simone Tripodi" 
>> wrote:
>>>
 Hi all,
 Since I proposed[1] to resurrect commons-graph from dormant to
 sandbox, there's been not only my personal activity, but we have
 recorded a good number of discussions on the ML and received
 contributions on JIRA[2], involving not only PMC such as James but
 also from users, such as Claudio Squarcella, Matthew Pococ and Marco
 Speranza.
 I think we have now, including users that took part with the unbinding
 vote in the proposal, a good number of people interested in this
 commons component and see it released, that's why today I'm calling
 for a vote to accept it in the propers.
 So please cast your vote!

 [ ] +1 Accept [graph] as a proper component
 [ ] +/- 0 uhm...
 [ ] -1 Don't accept it - and please explain why

 Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.

 Many thanks in advance, all the best!
 -Simo

 [1] http://markmail.org/message/mlvqiqhqm2nqhofr
 [2]
SANDBOX-334
SANDBOX-336
SANDBOX-338
SANDBOX-332
SANDBOX-333
SANDBOX-335
SANDBOX-337
SANDBOX-344
SANDBOX-345

 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


>>
>> -
>> 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: [VOTE] graduate [graph] as a proper component

[Phil Steitz]

On Dec 18, 2011, at 3:10 PM, James Carman  wrote:

> My concern is that the momentum dies off after we get it in proper and then
> we have to demote it later.  I am interested, but I don't know how much
> hands-on time I'll have for it.  If we get it to a mature state and let it
> prove itself a bit first, I think it has a better chance.  That's just my
> opinion and obviously there are many others who disagree so I don't even
> know why I'm taking the time to type this on my phone. Probably just
> looking for an excuse to play with ice cream sandwich.   :)

I agree with you but with maybe a different emphasis.  The requirement we used 
was three committers willing to actively help move the component along.  I 
don't see being ready for a release as a hard requirement, but I do see the 
need for more than one active committer and Ideally 3 or more before something 
gets promoted.  Are the people voting +1 planning to commit on [graph]?  Are 
there others?

Phil
> On Dec 18, 2011 3:22 PM, "Simone Tripodi"  wrote:
> 
>> Hi James!
>> 
>> can't we prepare the release in proper? Maybe it would be easier
>> attracting more people interested on contributing and get it ready for
>> a release quicker...
>> 
>> Best,
>> -Simo
>> 
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>> 
>> 
>> 
>> On Sun, Dec 18, 2011 at 9:18 PM, James Carman
>>  wrote:
>>> Can we get it ready for release first?
>>> On Dec 18, 2011 3:13 PM, "Simone Tripodi" 
>> wrote:
>>> 
 Hi all,
 Since I proposed[1] to resurrect commons-graph from dormant to
 sandbox, there's been not only my personal activity, but we have
 recorded a good number of discussions on the ML and received
 contributions on JIRA[2], involving not only PMC such as James but
 also from users, such as Claudio Squarcella, Matthew Pococ and Marco
 Speranza.
 I think we have now, including users that took part with the unbinding
 vote in the proposal, a good number of people interested in this
 commons component and see it released, that's why today I'm calling
 for a vote to accept it in the propers.
 So please cast your vote!
 
 [ ] +1 Accept [graph] as a proper component
 [ ] +/- 0 uhm...
 [ ] -1 Don't accept it - and please explain why
 
 Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.
 
 Many thanks in advance, all the best!
 -Simo
 
 [1] http://markmail.org/message/mlvqiqhqm2nqhofr
 [2]
   SANDBOX-334
   SANDBOX-336
   SANDBOX-338
   SANDBOX-332
   SANDBOX-333
   SANDBOX-335
   SANDBOX-337
   SANDBOX-344
   SANDBOX-345
 
 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
 
 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

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

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

[Gump]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at gene...@gump.apache.org.

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


Full details are available at:

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

That said, some information snippets are provided here.

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



The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html
Work Name: build_apache-commons_commons-proxy-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 11 secs
Command Line: /opt/maven2/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test 
[Working Directory: /srv/gump/public/workspace/apache-commons/proxy]
M2_HOME: /opt/maven2
-
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.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.003 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.004 sec
Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 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.02 sec
Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 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.035 sec
Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory
Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.187 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.024 sec
Running org.apache.commons.proxy.provider.TestBeanProvider
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec

Results :

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

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

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

Please refer to 
/srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the 
individual test results.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 10 seconds
[INFO] Finished at: Mon Dec 19 05:34:15 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

Re: [VOTE] graduate [graph] as a proper component

[James Carman]

My concern is that the momentum dies off after we get it in proper and then
we have to demote it later.  I am interested, but I don't know how much
hands-on time I'll have for it.  If we get it to a mature state and let it
prove itself a bit first, I think it has a better chance.  That's just my
opinion and obviously there are many others who disagree so I don't even
know why I'm taking the time to type this on my phone. Probably just
looking for an excuse to play with ice cream sandwich.   :)
On Dec 18, 2011 3:22 PM, "Simone Tripodi"  wrote:

> Hi James!
>
> can't we prepare the release in proper? Maybe it would be easier
> attracting more people interested on contributing and get it ready for
> a release quicker...
>
> Best,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Sun, Dec 18, 2011 at 9:18 PM, James Carman
>  wrote:
> > Can we get it ready for release first?
> > On Dec 18, 2011 3:13 PM, "Simone Tripodi" 
> wrote:
> >
> >> Hi all,
> >> Since I proposed[1] to resurrect commons-graph from dormant to
> >> sandbox, there's been not only my personal activity, but we have
> >> recorded a good number of discussions on the ML and received
> >> contributions on JIRA[2], involving not only PMC such as James but
> >> also from users, such as Claudio Squarcella, Matthew Pococ and Marco
> >> Speranza.
> >> I think we have now, including users that took part with the unbinding
> >> vote in the proposal, a good number of people interested in this
> >> commons component and see it released, that's why today I'm calling
> >> for a vote to accept it in the propers.
> >> So please cast your vote!
> >>
> >> [ ] +1 Accept [graph] as a proper component
> >> [ ] +/- 0 uhm...
> >> [ ] -1 Don't accept it - and please explain why
> >>
> >> Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.
> >>
> >> Many thanks in advance, all the best!
> >> -Simo
> >>
> >> [1] http://markmail.org/message/mlvqiqhqm2nqhofr
> >> [2]
> >>SANDBOX-334
> >>SANDBOX-336
> >>SANDBOX-338
> >>SANDBOX-332
> >>SANDBOX-333
> >>SANDBOX-335
> >>SANDBOX-337
> >>SANDBOX-344
> >>SANDBOX-345
> >>
> >> 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
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] graduate [graph] as a proper component

[Siegfried Goeschl]

+1

Siegfried Goeschl

On 18.12.11 21:12, Simone Tripodi wrote:

Hi all,
Since I proposed[1] to resurrect commons-graph from dormant to
sandbox, there's been not only my personal activity, but we have
recorded a good number of discussions on the ML and received
contributions on JIRA[2], involving not only PMC such as James but
also from users, such as Claudio Squarcella, Matthew Pococ and Marco
Speranza.
I think we have now, including users that took part with the unbinding
vote in the proposal, a good number of people interested in this
commons component and see it released, that's why today I'm calling
for a vote to accept it in the propers.
So please cast your vote!

[ ] +1 Accept [graph] as a proper component
[ ] +/- 0 uhm...
[ ] -1 Don't accept it - and please explain why

Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.

Many thanks in advance, all the best!
-Simo

[1] http://markmail.org/message/mlvqiqhqm2nqhofr
[2]
 SANDBOX-334
SANDBOX-336
SANDBOX-338
SANDBOX-332
SANDBOX-333
SANDBOX-335
SANDBOX-337
SANDBOX-344
SANDBOX-345

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




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

Re: [VOTE] graduate [graph] as a proper component

[Gary Gregory]

+1 :)

Gary

On Dec 18, 2011, at 15:13, Simone Tripodi  wrote:

> Hi all,
> Since I proposed[1] to resurrect commons-graph from dormant to
> sandbox, there's been not only my personal activity, but we have
> recorded a good number of discussions on the ML and received
> contributions on JIRA[2], involving not only PMC such as James but
> also from users, such as Claudio Squarcella, Matthew Pococ and Marco
> Speranza.
> I think we have now, including users that took part with the unbinding
> vote in the proposal, a good number of people interested in this
> commons component and see it released, that's why today I'm calling
> for a vote to accept it in the propers.
> So please cast your vote!
>
> [ ] +1 Accept [graph] as a proper component
> [ ] +/- 0 uhm...
> [ ] -1 Don't accept it - and please explain why
>
> Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.
>
> Many thanks in advance, all the best!
> -Simo
>
> [1] http://markmail.org/message/mlvqiqhqm2nqhofr
> [2]
>SANDBOX-334
>SANDBOX-336
>SANDBOX-338
>SANDBOX-332
>SANDBOX-333
>SANDBOX-335
>SANDBOX-337
>SANDBOX-344
>SANDBOX-345
>
> 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
>

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

Re: [VOTE] graduate [graph] as a proper component

[Christian Grobmeier]

+1 go proper


On Sun, Dec 18, 2011 at 9:42 PM, Oliver Heger
 wrote:
> Am 18.12.2011 21:22, schrieb Simone Tripodi:
>> can't we prepare the release in proper? Maybe it would be easier
>> attracting more people interested on contributing and get it ready for
>> a release quicker...
>
> I agree. If it is in proper, there is a good chance that it gains more
> attention. So +1 for the move.

+1

I think proper status should not be tied to a release, it should tied
to active development, which is the case here.

Cheers
Christian


>
> Oliver
>
>
>>
>> Best,
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> On Sun, Dec 18, 2011 at 9:18 PM, James Carman
>>   wrote:
>>>
>>> Can we get it ready for release first?
>>> On Dec 18, 2011 3:13 PM, "Simone Tripodi"
>>>  wrote:
>>>
 Hi all,
 Since I proposed[1] to resurrect commons-graph from dormant to
 sandbox, there's been not only my personal activity, but we have
 recorded a good number of discussions on the ML and received
 contributions on JIRA[2], involving not only PMC such as James but
 also from users, such as Claudio Squarcella, Matthew Pococ and Marco
 Speranza.
 I think we have now, including users that took part with the unbinding
 vote in the proposal, a good number of people interested in this
 commons component and see it released, that's why today I'm calling
 for a vote to accept it in the propers.
 So please cast your vote!

 [ ] +1 Accept [graph] as a proper component
 [ ] +/- 0 uhm...
 [ ] -1 Don't accept it - and please explain why

 Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.

 Many thanks in advance, all the best!
 -Simo

 [1] http://markmail.org/message/mlvqiqhqm2nqhofr
 [2]
        SANDBOX-334
        SANDBOX-336
        SANDBOX-338
        SANDBOX-332
        SANDBOX-333
        SANDBOX-335
        SANDBOX-337
        SANDBOX-344
        SANDBOX-345

 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


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



-- 
http://www.grobmeier.de
https://www.timeandbill.de

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

Re: [VOTE] graduate [graph] as a proper component

[Oliver Heger]

Am 18.12.2011 21:22, schrieb Simone Tripodi:

Hi James!

can't we prepare the release in proper? Maybe it would be easier
attracting more people interested on contributing and get it ready for
a release quicker...


I agree. If it is in proper, there is a good chance that it gains more 
attention. So +1 for the move.


Oliver



Best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Sun, Dec 18, 2011 at 9:18 PM, James Carman
  wrote:

Can we get it ready for release first?
On Dec 18, 2011 3:13 PM, "Simone Tripodi"  wrote:


Hi all,
Since I proposed[1] to resurrect commons-graph from dormant to
sandbox, there's been not only my personal activity, but we have
recorded a good number of discussions on the ML and received
contributions on JIRA[2], involving not only PMC such as James but
also from users, such as Claudio Squarcella, Matthew Pococ and Marco
Speranza.
I think we have now, including users that took part with the unbinding
vote in the proposal, a good number of people interested in this
commons component and see it released, that's why today I'm calling
for a vote to accept it in the propers.
So please cast your vote!

[ ] +1 Accept [graph] as a proper component
[ ] +/- 0 uhm...
[ ] -1 Don't accept it - and please explain why

Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.

Many thanks in advance, all the best!
-Simo

[1] http://markmail.org/message/mlvqiqhqm2nqhofr
[2]
SANDBOX-334
SANDBOX-336
SANDBOX-338
SANDBOX-332
SANDBOX-333
SANDBOX-335
SANDBOX-337
SANDBOX-344
SANDBOX-345

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




-
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: [dbutils] CaseInsensitiveHashMap in BasicRowProcessor should extend LinkedHashMap

[stefano masiero]

Hi Hasan,
I don't have a generic order for keys, my order is the same of the fields
in select list:
select , , ...,  from ...
when the resultset of this query is mapped, values in the map are inserted
in this order , , ..., .
I'd like that map.keySet().iterator() let me iterate over values in that
order, i.e. insertion-order.
This is a custom order but I have to parse the query to get it. I think it
should be the order that a client would expect.
>From the LinkedHashMap javadoc:
"This implementation spares its clients from the unspecified, generally
chaotic ordering provided by
HashMap
 (and 
Hashtable),
without incurring the increased cost associated with
TreeMap
."



On Sun, Dec 18, 2011 at 7:46 PM, Hasan Diwan  wrote:

> On 18 December 2011 10:31, aris2world  wrote:
> > I've a question about CaseInsensitiveHashMap in BasicRowProcessor: it
> > extends HashMap but if it will extend LinkedHashMap I think the resulting
> > Map could seem more consistent with the executed query to a client
> > perspective.
> > I mean: when the method toMap puts the columns of the resultset into the
> > map, the insertion order is the same of the columns in the select list of
> > the executed query. It will be useful to me to extract values in the same
> > order when I'm iterating over the key set of the returned map. This is
> > accomplished in a simply way with a LinkedHashMap. What do you think
> about
> > it?
>
> I think you should be able to (untested):
> HashMap map = basicRowProcessorInstance.toMap();
> List  keys = new ArrayList(map.keySet());
> Collections.sort(keys);
> now keys will be sorted alphabetically by String's default Comparator,
> but you can also specify a custom one.
>
> --
> Sent from my mobile device
> Envoyait de mon portable
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] graduate [graph] as a proper component

[Simone Tripodi]

Hi James!

can't we prepare the release in proper? Maybe it would be easier
attracting more people interested on contributing and get it ready for
a release quicker...

Best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Sun, Dec 18, 2011 at 9:18 PM, James Carman
 wrote:
> Can we get it ready for release first?
> On Dec 18, 2011 3:13 PM, "Simone Tripodi"  wrote:
>
>> Hi all,
>> Since I proposed[1] to resurrect commons-graph from dormant to
>> sandbox, there's been not only my personal activity, but we have
>> recorded a good number of discussions on the ML and received
>> contributions on JIRA[2], involving not only PMC such as James but
>> also from users, such as Claudio Squarcella, Matthew Pococ and Marco
>> Speranza.
>> I think we have now, including users that took part with the unbinding
>> vote in the proposal, a good number of people interested in this
>> commons component and see it released, that's why today I'm calling
>> for a vote to accept it in the propers.
>> So please cast your vote!
>>
>> [ ] +1 Accept [graph] as a proper component
>> [ ] +/- 0 uhm...
>> [ ] -1 Don't accept it - and please explain why
>>
>> Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.
>>
>> Many thanks in advance, all the best!
>> -Simo
>>
>> [1] http://markmail.org/message/mlvqiqhqm2nqhofr
>> [2]
>>        SANDBOX-334
>>        SANDBOX-336
>>        SANDBOX-338
>>        SANDBOX-332
>>        SANDBOX-333
>>        SANDBOX-335
>>        SANDBOX-337
>>        SANDBOX-344
>>        SANDBOX-345
>>
>> 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
>>
>>

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

Re: [VOTE] graduate [graph] as a proper component

[James Carman]

Can we get it ready for release first?
On Dec 18, 2011 3:13 PM, "Simone Tripodi"  wrote:

> Hi all,
> Since I proposed[1] to resurrect commons-graph from dormant to
> sandbox, there's been not only my personal activity, but we have
> recorded a good number of discussions on the ML and received
> contributions on JIRA[2], involving not only PMC such as James but
> also from users, such as Claudio Squarcella, Matthew Pococ and Marco
> Speranza.
> I think we have now, including users that took part with the unbinding
> vote in the proposal, a good number of people interested in this
> commons component and see it released, that's why today I'm calling
> for a vote to accept it in the propers.
> So please cast your vote!
>
> [ ] +1 Accept [graph] as a proper component
> [ ] +/- 0 uhm...
> [ ] -1 Don't accept it - and please explain why
>
> Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.
>
> Many thanks in advance, all the best!
> -Simo
>
> [1] http://markmail.org/message/mlvqiqhqm2nqhofr
> [2]
>SANDBOX-334
>SANDBOX-336
>SANDBOX-338
>SANDBOX-332
>SANDBOX-333
>SANDBOX-335
>SANDBOX-337
>SANDBOX-344
>SANDBOX-345
>
> 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
>
>

[VOTE] graduate [graph] as a proper component

[Simone Tripodi]

Hi all,
Since I proposed[1] to resurrect commons-graph from dormant to
sandbox, there's been not only my personal activity, but we have
recorded a good number of discussions on the ML and received
contributions on JIRA[2], involving not only PMC such as James but
also from users, such as Claudio Squarcella, Matthew Pococ and Marco
Speranza.
I think we have now, including users that took part with the unbinding
vote in the proposal, a good number of people interested in this
commons component and see it released, that's why today I'm calling
for a vote to accept it in the propers.
So please cast your vote!

[ ] +1 Accept [graph] as a proper component
[ ] +/- 0 uhm...
[ ] -1 Don't accept it - and please explain why

Open will stay open for 72h and closes on Wed 21th, 8:15 PM CET.

Many thanks in advance, all the best!
-Simo

[1] http://markmail.org/message/mlvqiqhqm2nqhofr
[2]
SANDBOX-334
SANDBOX-336
SANDBOX-338
SANDBOX-332
SANDBOX-333
SANDBOX-335
SANDBOX-337
SANDBOX-344
SANDBOX-345

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: [dbutils]

[Hasan Diwan]

On 18 December 2011 10:31, aris2world  wrote:
> I've a question about CaseInsensitiveHashMap in BasicRowProcessor: it
> extends HashMap but if it will extend LinkedHashMap I think the resulting
> Map could seem more consistent with the executed query to a client
> perspective.
> I mean: when the method toMap puts the columns of the resultset into the
> map, the insertion order is the same of the columns in the select list of
> the executed query. It will be useful to me to extract values in the same
> order when I'm iterating over the key set of the returned map. This is
> accomplished in a simply way with a LinkedHashMap. What do you think about
> it?

I think you should be able to (untested):
HashMap map = basicRowProcessorInstance.toMap();
List  keys = new ArrayList(map.keySet());
Collections.sort(keys);
now keys will be sorted alphabetically by String's default Comparator,
but you can also specify a custom one.

-- 
Sent from my mobile device
Envoyait de mon portable

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

[dbutils]

[aris2world]

Hi all
I've a question about CaseInsensitiveHashMap in BasicRowProcessor: it
extends HashMap but if it will extend LinkedHashMap I think the resulting
Map could seem more consistent with the executed query to a client
perspective.

I mean: when the method toMap puts the columns of the resultset into the
map, the insertion order is the same of the columns in the select list of
the executed query. It will be useful to me to extract values in the same
order when I'm iterating over the key set of the returned map. This is
accomplished in a simply way with a LinkedHashMap. What do you think about
it?
Thank you
aris

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

[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 22 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..
gdal_translate
HDF5:"/home/kk/grass/data/4404.he5"://HDFEOS/GRIDS/OMI_Column_Amount_O3/Data_Fields/ColumnAmountO3/home/kk/4.tif
FOO..
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.019 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.024 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.
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 
(Exit value: 143)
Process completed in 2005 millis; below is its output
Process timed out and was killed.
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
Preparing to execute process - commandLine=[/bin/ls, /opt]
Process spun off successfully - process=/bin/ls
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 8036 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
Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.777 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 21 seconds
[INFO] Finished at: Sun Dec 18 14:15:53 UTC 2011
[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 05001218122011, vmgump.apache.org:vmgump:05001218122011
Gump E-mail Identifier (unique within run) #1.

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