Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of jnord@cisco.com designates
 173.37.86.72 as permitted sender)
From: "James Nord (jnord)" <jnord@cisco.com>
To: Maven Developers List <dev@maven.apache.org>
Subject: RE: Testing [Vote] plugins?
Thread-Topic: Testing [Vote] plugins?
Thread-Index: Ac4DjooFsN/+Mcl4TYiu3Q2kMMVhCgAoUcsAAAvuiSA=
Date: Wed, 6 Feb 2013 12:41:31 +0000
Message-ID: <5629A6219DB3E544AB84388D90149787F99B8C@xmb-aln-x03.cisco.com>
References: <5629A6219DB3E544AB84388D90149787F992FF@xmb-aln-x03.cisco.com>
 <CADVp3v_3WVK4Xcr871fB-AbxTYVGbj4XcZ2X9qqUvZocKx-z8Q@mail.gmail.com>
In-Reply-To: 
 <CADVp3v_3WVK4Xcr871fB-AbxTYVGbj4XcZ2X9qqUvZocKx-z8Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> If these are being released into Central - then they *will* never change.
> They are Golden.

> Prior to getting their, e.g. during the voting process, these jars are re=
leased
> into a staging area.
> You are invited to try those jars from the staging area to ensure they do=
nt
> have regression issues etc.

That's what I would like to do.

> If you do this then you generally delete your local m2 cache
> (~/.m2/repository) or you use a new settings.xml file that points to a
> different location.

Meanwhile these are in all the caches of the MRMs and it needs more work th=
an would ideally be needed (if you want to widen testing to more of the com=
munity)

> You would not normally use an MRM in this scenario as the staging jars ar=
e
> not yet Golden.

This definition of release contradicts mavens definition.
    A release is something that has no -SNAPSHOT (or timestamp) at the end =
of its version.

Thus these are releases even if they do not make it onto central (and delet=
ing nexus stages after allowing any maven to consume from it is a bad thing=
 and imho one of the things that nexus pro really needs to improve on)

I am also well aware of how nexus staging works - and staging is not the is=
sue, reusing the same release version is the issue.
All this extra hand fudging would disappear if the versions where used wher=
e unique e.g 1.0.0-1 vote fails next is 1.0.0-2.

But also how can I test it if I can't use it...  (esp the maven-release-plu=
gin!)
Most tests to be useful would be done in a CI environment with auto testing=
 - configuring different jobs to have different settings would be a PITA.

> If the release fail, then the staging areas are deleted and the process s=
tarts
> again.  Nothing has happened to Central yet.

But the artifacts have been used elsewhere (even just testing is using it..=
.).


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