You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Continuum@vmbuild" <co...@apache.org> on 2011/08/02 18:00:01 UTC

[continuum] BUILD FAILURE: Apache Commons - Commons EL - Default Maven 2 Build Definition (Java 1.5)

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10757&projectId=78

Build statistics:
  State: Failed
  Previous State: Ok
  Started at: Tue 2 Aug 2011 15:59:50 +0000
  Finished at: Tue 2 Aug 2011 16:00:00 +0000
  Total time: 10s
  Build Trigger: Forced
  Build Number: 5
  Exit code: 1
  Building machine hostname: vmbuild
  Operating system : Linux(unknown)
  Java Home version : 
          java version "1.6.0_24"
          Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
          Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
        
  Builder version :
          Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+0000)
          Java version: 1.6.0_24
          Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
          Default locale: en_US, platform encoding: ANSI_X3.4-1968
          OS name: "linux" version: "2.6.32-31-server" arch: "amd64" Family: "unix"
    
****************************************************************************
SCM Changes:
****************************************************************************
No files changed

****************************************************************************
Dependencies Changes:
****************************************************************************
No dependencies changed


****************************************************************************
Build Definition:
****************************************************************************
POM filename: pom.xml
Goals: clean deploy   
Arguments: --batch-mode -Pjava-1.5
Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: COMMONS_SCHEDULE
Profile Name: Maven 2.2.1
Description: Default Maven 2 Build Definition (Java 1.5)

****************************************************************************
Test Summary:
****************************************************************************
Tests: 4
Failures: 0
Errors: 0
Success Rate: 100
Total time: 0.096





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

Re: Is this really needed !? Was: [continuum] BUILD FAILURE: XXX

Posted by Emmanuel Bourg <eb...@apache.org>.
Le 02/08/2011 18:04, Mladen Turk a écrit :
> I see there is online report.
> Is there really a need for such high volume of messages to
> the developers list like there's not enough email messages
> already?
>
> Yesterday there was 30 messages like those, so I suppose
> the same number is going to hit us today.
>
> Couldn't the parties interested in those mails either
> just check the web page or create a separate mailing list?

Sorry for the spam, this is the result of trials and errors in the 
process of configuring Continuum to deploy the snapshots.

I'm to blame for the first wave, I expected to build only one project 
but everything went off. The second wave was triggered after Brett 
Porter configured the build account allowed to deploy the artifacts on 
the server hosting Continuum.

Emmanuel Bourg

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

Is this really needed !? Was: [continuum] BUILD FAILURE: XXX

Posted by Mladen Turk <mt...@apache.org>.
On 08/02/2011 06:00 PM, Continuum@vmbuild wrote:
> Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=10757&projectId=78
>

I see there is online report.
Is there really a need for such high volume of messages to
the developers list like there's not enough email messages
already?

Yesterday there was 30 messages like those, so I suppose
the same number is going to hit us today.

Couldn't the parties interested in those mails either
just check the web page or create a separate mailing list?


Regards
-- 
^TM

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