I think it should actually be Codehaus' Bamboo, since every mojo-developer has access to it with its own credentails. Sonatype's CI Grid requires a separate account, other organization... -Robert
Date: Tue, 11 Jan 2011 11:56:51 +0100 From: [email protected] To: [email protected] Subject: Re: [mojo-dev] [Bamboo] Mojo - Parent POM - CI build 72 has FAILED. Change made by afloom Sorry, my bad. Fixed. Btw, why's this being built on Codehaus's Bamboo instance and not on Sonatype's CI Grid? The ciManagement section states the Sonatype grid... /Anders On Tue, Jan 11, 2011 at 11:43, Codehaus Bamboo <[email protected]> wrote: MOJO-PARENTCI-72 failed. Code has been updated by afloom. No failed tests found, a possible compilation error. Code Changes See full change details afloom Removed unnecessary version definition of m-enforcer-p as it is defined in pluginManagement (will prevent errors in future upgrades of this plugin). (13394) Error Summary See full build log [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1 Cause: Cannot find setter nor field in org.apache.maven.plugins.enforcer.RequireNoRepositories for 'allowSnapshotRepositories' [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator Want this information in your IDE? Actions View Online Add Comments View Artifacts Download Logs Link to JIRA issue
