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-javaflow has an issue affecting its community integration.
This is
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
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
The Apache Commons team is pleased to announce the release of
version 1.5.5 of Commons Pool. Commons Pool provides a general
purpose object pooling API, an implementation toolkit and some pool
implementations.
Version 1.5.5 is a patch release including bug fixes, documentation
improvements and
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-io-test has an issue affecting its community integration.
This iss
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=475&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Sat 11 Sep 2010 02:20:05 +
Finished at: Sat 11 Sep 2010 02:22:33 +
Total time: 2m 28s
Build Trigger: Schedule
Bu
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-digester has an issue affecting its community integration.
This is
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=474&projectId=65
Build statistics:
State: Failed
Previous State: Ok
Started at: Sat 11 Sep 2010 01:20:06 +
Finished at: Sat 11 Sep 2010 01:23:12 +
Total time: 3m 6s
Build Trigger: Schedule
Build N
On 9/10/10 6:27 PM, Simone Tripodi wrote:
Hi all guys,
the RC1 is driving me crazy... once resolved the gpg issues, following
the wiki guide[1] Rahul ans Seb suggested, once launched "mvn -Prc
release:perform" when going to deploy artifacts, the build was
blocked:
[INFO] [INFO] [deploy:deploy {e
On Fri, Sep 10, 2010 at 6:27 PM, Simone Tripodi
wrote:
> Hi all guys,
> the RC1 is driving me crazy... once resolved the gpg issues, following
> the wiki guide[1] Rahul ans Seb suggested, once launched "mvn -Prc
> release:perform" when going to deploy artifacts, the build was
> blocked:
>
> [INFO]
Hi all guys,
the RC1 is driving me crazy... once resolved the gpg issues, following
the wiki guide[1] Rahul ans Seb suggested, once launched "mvn -Prc
release:perform" when going to deploy artifacts, the build was
blocked:
[INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO]
[INFO]
[IN
Le 10/09/2010 22:55, Gilles Sadowski a écrit :
>>> I don't know whether it is one of those rare cases. The algorithm
>>> description in ALGOL uses the "=" sign while the FORTRAN implementation (in
>>> the appendix) works around the problem by inversing the checks:
>>
>> It may be the case. There is
> > I don't know whether it is one of those rare cases. The algorithm
> > description in ALGOL uses the "=" sign while the FORTRAN implementation (in
> > the appendix) works around the problem by inversing the checks:
>
> It may be the case. There is a similar one in the Brent solver, the
> semant
On Fri, Sep 10, 2010 at 11:53 AM, sebb wrote:
> On 10 September 2010 08:30, Simone Tripodi wrote:
>> Hi Seb,
>> thanks for your feedbacks. The problem I have is that even if I omit
>> the password waiting for the prompt, once the builds arrives ad the
>> gpg:sign execution, it is completely block
On 10 September 2010 08:30, Simone Tripodi wrote:
> Hi Seb,
> thanks for your feedbacks. The problem I have is that even if I omit
> the password waiting for the prompt, once the builds arrives ad the
> gpg:sign execution, it is completely blocked :(
> I'm using gpg 1.4.9, shall I have to upgrade
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=465&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 10 Sep 2010 13:20:04 +
Finished at: Fri 10 Sep 2010 13:22:35 +
Total time: 2m 30s
Build Trigger: Schedule
Bu
I took a look at this failure and it doesn't relate to the changes I just made:
---
Test set: org.apache.commons.beanutils.BeanificationTestCase
-
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=464&projectId=65
Build statistics:
State: Failed
Previous State: Ok
Started at: Fri 10 Sep 2010 12:20:07 +
Finished at: Fri 10 Sep 2010 12:23:08 +
Total time: 3m 0s
Build Trigger: Schedule
Build N
Hi Seb,
thanks for your feedbacks. The problem I have is that even if I omit
the password waiting for the prompt, once the builds arrives ad the
gpg:sign execution, it is completely blocked :(
I'm using gpg 1.4.9, shall I have to upgrade to 2?
Many thanks in advance, have a nice day,
Simo
http://p
19 matches
Mail list logo
