aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandros Karypidis <>
Subject Re: Version 0.3 in "parent" pom.xml?
Date Fri, 03 Sep 2010 17:32:03 GMT
  Hi all,

My understanding is that if a release is made from this "0.2-incubating" 
branch as it is now, then the Maven repository will obtain a new version 
of the "parent" artifact in it. The number we are discussing will be 
used for the "version" coordinate of the published artifact. The way 
things currently are, "0.3-incubating" will be used.

Take a look at 
and imagine that uploading this release will create a "0.3-incubaring" 
folder alongside the "0.1-incubating" to store this artifact. If in the 
future tou make a new "full" release (from a new 0.3-incubating branch, 
not a 0.2.1 patch from this branch), then you will not be able to re-use 
this project coordinate.

Assuming this pom does not change at all until that next "full" 0.3 
release, this won't matter much (this is related to the other discussion 
of whether parts o aries should be versioned and released individually 
or not: it's like "parent" is using its individual versioning scheme and 
has not changed between the "full" 0.2 and 0.3 releases).

In short:

If I'm not mistaken - there are implications also for the trunk: as soon 
as an artifact is published, you cannot change it without also changing 
its version number. As soon as you need to change the copy in the trunk, 
you will also have to change the version of the trunk (e.g. to use 
"0.3.1-incubating") so that there is no "clash" among the already 
published artifact and the "to-be-published" artifact.

On 3/9/2010 14:49, Alasdair Nottingham wrote:
> I agree. Until we know whether or not we will ever do a release from
> the 0.2 branch I don't see the point in fixing it. If we never do a
> release from the 0.2 branch we would just have wasted the effort.
> +1
> Alasdair
> On 2 September 2010 17:37, zoe slattery<>  wrote:
>>   On 02/09/2010 16:52, David Jencks wrote:
>>> On Sep 2, 2010, at 12:42 AM, zoe slattery wrote:
>>>> Hi - yes - absolutely. I should have made this a bit clearer but I didn't
>>>> fully understand it at the start. Once the release artifacts have been
>>>> created the branch is effectively a dead end. What the maven release plugin
>>>> does to it during the creation of the release makes it unusable for any
>>>> practical purpose.
>>> I don't follow your reasoning here.  If we intended bug fix releases on
>>> these branches for the components and had (for a development branch)
>>> correctly set the next branch version at 0.2.1-incubating-SNAPSHOT then I
>>> would expect that the svn tree would be all set up for development.  Other
>>> than the version (which conflicts with trunk) and our intentions what makes
>>> these branches unusable?
>> What makes it unusable is that I haven't set it up to be used -  by taking
>> the defaults from the maven release plugin I made it useless. This is
>> exactly the same in the 0.1-incubating branch. The only reason we might want
>> this to be set up more sensibly is if we have a requirement to do a
>> 0.2.1-incubating release because someone finds a problem with one of the 0.2
>> modules. That's a possibility and if/when that happens I'll be happy to fix
>> up the 0.2-incubating branch properly. I'll certainly add this to the Aries
>> release pages so that we get it right for the 0.3-incubating release.
>> Zoė
>>> thanks
>>> david jencks
>>>> Zoė
>>>>> I suspect that Zoe accepted the release plugin suggestion that the next
>>>>> version would be 0.3-incubating.  This would be appropriate on trunk
>>>>> when releasing on a branch like this it's probably better to add another
>>>>> decimal, 0.2.1-incubating.  However I hope this branch is a dead end
>>>>> nothing other than 0.2-incubating is ever released from it so it shouldn't
>>>>> make any practical difference.
>>>>> thanks
>>>>> david jencks
>>>>> On Sep 1, 2010, at 3:31 PM, Alexandros Karypidis wrote:
>>>>>> Hi all,
>>>>>> It seems weird that the 0.2-incubaring-RCx branch uses "0.3-..."
>>>>>> its<version>     tag:
>>>>>> <name>Aries :: Top Parent POM</name>
>>>>>> <version>0.3-incubating-SNAPSHOT</version>
>>>>>> <packaging>pom</packaging>
>>>>>> Is this intended to be this way?

View raw message