Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of gudnabrsam@gmail.com designates
 209.85.213.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type:content-transfer-encoding;
        b=GU05KYJpocTSYWuBj6RVJguKyLYeWCG+fTyybuRoIybu8Dl2yXxntbj7qgL2KYFpgY
         PptMD7w1KCB71RO849Bb7dksH+GHkot051pHxBqtX4TY+ek917u+YjT0yJct1lqX0PWU
         aa2fZ53a5Nl/pNSczNS1vI82VgFxJ+vd3HaEU=
MIME-Version: 1.0
Reply-To: gudnabrsam@gmail.com
In-Reply-To: <BANLkTim+k5Nq-H08dkEg+R3W+nfRT9PCOg@mail.gmail.com>
References: <4DF85B4E.1020200@tue.nl>
	<4DF861E7.80404@free.fr>
	<BANLkTimzQB43a=-psaxDgv5wCWr4MjeYNQ@mail.gmail.com>
	<20110615115625.GE3310@dusk.harfang.homelinux.org>
	<BANLkTinqp3GFvP2U7wDsc=WQBL+ZH=JyGw@mail.gmail.com>
	<BANLkTim+k5Nq-H08dkEg+R3W+nfRT9PCOg@mail.gmail.com>
Date: Wed, 15 Jun 2011 10:02:36 -0500
Message-ID: <BANLkTimkwO345JwZ1onJcugKmDAncuKWLQ@mail.gmail.com>
Subject: Re: [Math] download development snapshot
From: Matt Benson <gudnabrsam@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 15, 2011 at 9:57 AM, sebb <sebbaz@gmail.com> wrote:
> On 15 June 2011 15:34, Matt Benson <gudnabrsam@gmail.com> wrote:
>> On Wed, Jun 15, 2011 at 6:56 AM, Gilles Sadowski
>> <gilles@harfang.homelinux.org> wrote:
>>> On Wed, Jun 15, 2011 at 09:31:24AM +0100, sebb wrote:
>>>> For components that use Nexus, it's trivial to use mvn deploy on a
>>>> SNAPSHOT release.
>>>>
>>>> This can be useful for developers to check that a patch solves their p=
roblem.
>>>>
>>>> However, snapshots should not be advertised to the general user
>>>> public, so should never be referenced from download pages, nor on the
>>>> user list.
>>>>
>>>> But AFAIK it would be OK to mention the snapshot on the JIRA issue.
>>>>
>>>> There are also some projects that use the CI servers to upload
>>>> snapshots. Not sure how that is done.
>>>
>>> It would be nice to have a "latest" snapshot together with all snapshot=
s
>>> that are supposed to solve a given issue. "latest" would be overwritten=
 by
>>> the last issue snapshot.
>>> E.g. assuming that issue (MATH-799) is resolved, the following snapshot=
s
>>> would be available:
>>>
>>> =A0math-commons.MATH-774.jar
>>> =A0math-commons.latest.jar -> math-commons.MATH-774.jar
>>>
>>> Then, later, when issue MATH-768 is resolved:
>>>
>>> =A0math-commons.MATH-774.jar
>>> =A0math-commons.MATH-768.jar
>>> =A0math-commons.latest.jar -> math-commons.MATH-768.jar
>>>
>>
>> This snapshot-per-resolved-issue scheme certainly isn't something I'd
>> care to implement by hand. =A0I don't really think that degree of detail
>> is necessary.
>
> +1, latest should be sufficient for checking if the issues are resolved.
>
>> It would be nice to publish our CI builds to the
>> snapshots repo. =A0These are typically dated in the repo. =A0E.g. Jenkin=
s
>> will have svn info available per-build, so the only piece potentially
>> missing from this mixture would be the correlation between a given
>> snapshot and the Jenkins build.
>
> JMeter solves this by including the svn info as part of the version
> id, which is logged/displayed on startup.
> It also uses the revision as part of the snapshot build name.
>
> This is done with Ant, but it should be easy enough to adapt the code
> for Maven builds.
>
> I don't think it will be possible to rename the snapshot artifacts, as
> they are auto-generated by Maven, but updating the code should be easy
> enough, and it might even be possible to add the SVN info to the
> manifest which is present in all jars.
>
>> Not sure how the other available CI
>> options stack up in this regard. =A0Since AFAIK our CI builds currently
>> are done in Continuum, I would be shocked to find that publishing a
>> snapshot isn't part of its repertoire.
>
> No idea whether Continuum supports snapshot publication - try asking
> on the builds@a.o list.
>
> However, this will all take some effort to achieve.
>
> In the short term, the occasional manual mvn deploy + update of JIRA
> with the reference should work for many use cases.

I would amend to say a simple "I have published a SNAPSHOT containing
this fix" should be enough for JIRA.  Usually once fixed, things stay
fixed, time being something we only know how to move through in a
forward direction and all.

Matt

>
>> Matt
>>
>>> [Such a history might be useful to help users spot which change might h=
ave
>>> resulted in breaking something.]
>>>
>>>
>>> Best regards,
>>> Gilles
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

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