aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Hughes <>
Subject Re: [DISCUSSION] Aries release - version of sample (was: svn commit: r915049 ...)
Date Mon, 22 Feb 2010 23:04:45 GMT
On 22 February 2010 22:52, Joe Bohn <> wrote:
> Jeremy Hughes wrote:
>> On 22 February 2010 22:23, Joe Bohn <> wrote:
>>> Would it be possible to use something like 0.1.1-incubating-SNAPSHOT and
>>> 0.1.2-incubating-SNAPSHOT for the purpose of this sample (which would
>>> translate to 0.1.1 and 0.1.2 as we release)?  I doubt that we will do a
>>> future release of 0.1.* release of all of Aries.  If we do a subsequent
>>> pre-1.0 release it would probably be named 0.2 (in which case we could
>>> use
>>> 0.2.1 and 0.2.2 for this sample again).  It seems to me that we need to
>>> pick
>>> something that has a relationship to the related Aries release.
>> Won't the maven-release-plugin ask for the version the artifacts
>> should be released at, effectively change it for all poms, create the
>> artifacts, check in the poms, tag the HEAD, then check in new poms
>> that say something like 0.2-incubating-SNAPSHOT. i.e. using the
>> release plugin, the version of the artifacts have to be the same
>> across the board.
> Yes, the maven-release-plugin will do that for child pom with a version that
> matches the one you are releasing.  However, given that we are looking for
> some alternative version for these lower level sample poms, the release
> plugin will ignore them (or complain if there are SNAPSHOT references that
> are not 0.1-incubating-SNAPSHOT when you attempt the release).  That means
> that there must be some manual effort to set the versions for these modules
> prior to using the maven-release-plugin.  So no matter what you do you have
> some manual work and the maven-release-plugin can't help.

OK thanks, I'll try some dry-runs to see what happens.

> I was simply proposing that the scheme used be somehow related to the Aries
> release version and also that it be kept as a "SNAPSHOT" until we are ready
> to release.  I am concerned about using anything for now that does not
> include "SNAPSHOT" in anything.  If we were to publish snapshots now then
> these artifacts with versions like 1.0.0 and 1.0.1 will be pushed to the
> maven snapshot repo and that can create some headaches in the future.

+1 sorry I missed that point.

>>> Joe
>>> Jeremy Hughes wrote:
>>>> I noticed this sample module doesn't have a version with the
>>>> incubating-SNAPSHOT suffix like other modules. This is because it's
>>>> part of a sample.
>>>> Zoe, it looks like you're creating a JPA impl (v1.1.0) of the blog
>>>> persistence bundle so that the JDBC impl (at v1.0.0) can be replaced
>>>> with the JPA impl.
>>>> Given this I think we need to find a way to release these bundles
>>>> despite not having the -0.1-incubating suffix. But we are prevented
>>>> from releasing artifacts at that version. If the artifact we were to
>>>> release the sample bundles in a zip or preferably eba (perhaps in a
>>>> zip distro) then we can release the zip with -0.1-incubating in its
>>>> name and have it contain sample bundles at the 1.0.0 and 1.1.0
>>>> versions.
>>>> So the part I'm trying to understand how to do is how to generate
>>>> these bundle jars for inclusion with a release artifact without having
>>>> to release the bundle jars as artifacts in themselves.
>>>> Any ideas?
>>>> Cheers,
>>>> Jeremy
>>>> On 22 February 2010 20:33,  <> wrote:
>>>>> Author: zoe
>>>>> Date: Mon Feb 22 20:33:33 2010
>>>>> New Revision: 915049
> <snip>

View raw message