On 14 August 2011 14:47, Gary Gregory <garydgreg...@gmail.com> wrote: > On Sun, Aug 14, 2011 at 9:41 AM, sebb <seb...@gmail.com> wrote: >> On 14 August 2011 14:34, Gary Gregory <garydgreg...@gmail.com> wrote: >>> On Aug 14, 2011, at 8:22, sebb <seb...@gmail.com> wrote: >>> >>>> That was because the POM was still showing 3.0.1, and Continuum can >>>> only deploy SNAPSHOTS. >>>> >>>> I've update the pom to 3.0.2 SNAPSHOT, and the build now succeeds. >>>> >>>> By the way, the build failures would not happen if release tags were >>>> created from a new checkout, as the trunk would then always be in >>>> SNAPSHOT mode. >>> >>> Which is what happens if you use the nexus build procedure. As opposed >>> to the manual style. >> >> No, Nexus has nothing to do with this. >> I used manual tag creation with Nexus several times. > > Hi, > > The last time I used the steps from > https://wiki.apache.org/commons/UsingNexus, it required that the POM > be a SNAPSHOT. That's what I mean by the Nexus 'procedure'.
Yes, the pom has to be SNAPSHOT to deploy a SNAPSHOT - that is true for non-Nexus deployment as well. The Wiki could perhaps be clearer, but the intention of that section is to describe how to deploy a snapshot using Nexus as an initial test stage before doing the release proper. Later on, the page describes deployment of the release candidate. Nexus changes very little - basically it just intercepts deployments and holds non-SNAPSHOT deployments in a staging area until they are formally approved and released. [Snaphots are deployed without needing staging]. This prevents accidental deployment. AIUI previously using the -Prelease profile with deploy would actually deploy the artifacts, with no chance to stop it once performed. The staging area can also be used in release votes. That's why I think Nexus a good thing. > Gary > >> >>> Gary >>> >>>> >>>> On 14 August 2011 05:21, Continuum@vmbuild <contin...@apache.org> wrote: >>>>> Online report : >>>>> http://vmbuild.apache.org/continuum/buildResult.action?buildId=11233&projectId=95 >>>>> >>>>> Build statistics: >>>>> State: Failed >>>>> Previous State: Failed >>>>> Started at: Sun 14 Aug 2011 04:20:45 +0000 >>>>> Finished at: Sun 14 Aug 2011 04:21:53 +0000 >>>>> Total time: 1m 7s >>>>> Build Trigger: Schedule >>>>> Build Number: 214 >>>>> 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_AU, platform encoding: UTF-8 >>>>> OS name: "linux" version: "2.6.32-31-server" arch: "amd64" >>>>> Family: "unix" >>>>> >>>>> **************************************************************************** >>>>> SCM Changes: >>>>> **************************************************************************** >>>>> Changed: bayard @ Sun 14 Aug 2011 03:25:18 +0000 >>>>> Comment: Incrementing the clirr version >>>>> Files changed: >>>>> /commons/proper/lang/trunk/pom.xml ( 1157459 ) >>>>> >>>>> **************************************************************************** >>>>> 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: 2039 >>>>> Failures: 0 >>>>> Errors: 0 >>>>> Success Rate: 100 >>>>> Total time: 17.730001 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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 >> >> > > > > -- > Thank you, > Gary > > http://garygregory.wordpress.com/ > http://garygregory.com/ > http://people.apache.org/~ggregory/ > http://twitter.com/GaryGregory > > --------------------------------------------------------------------- > 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
