commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <joerg.schai...@gmx.de>
Subject Re: [dbcp] 1.3 release packaging - take two
Date Sat, 28 Nov 2009 19:01:00 GMT
Niall Pemberton wrote:

> 2009/11/28 Phil Steitz <phil.steitz@gmail.com>:

[snip]

>> I think adding this to the build.xml in trunk will be confusing. I
>> agree with Sebb that if we do that we need to comment it.  Since we
>> are going to have to have a branch to cut the 1.3 release from and
>> we also need to change the version number in the build files there,
>> I was thinking it might be better to create a build.xml just for 1.3
>> that eliminates the nojdbc4 stuff and executes the new goal as part
>> of the build. I am pretty sure the filtering operation is
>> idempotent, so should not be a problem executing repeatedly and this
>> would eliminate the possibility of forgetting to do it.  This and
>> the modified (version change only) pom.xml would replace build.xml,
>> pom.xml in the branch.

It's not enough to adjust the version in the POM, you have to adjust the SCM
URLs also to release with Maven from the branch.

>> The process for cutting 1.3.1/1.4.1 would then be
>> 0) create a 1.3.1 branch from trunk
>> 1) copy build.xml, pom.xml from 1.3 branch (alternatively, we could
>> maintain build.xml.1.3, pom.xml.1.3 in trunk and rename in the branch).
>> 2) backport any pom or build.xml changes from trunk to the 1.3
>> versions in the branch
>> 3) normal release stuff in trunk for 1.4, branch for 1.3
> 
> Sounds good to me. I don't mind either option for build.xml/pom.xml -
> whichever you prefer.

- Jörg


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


Mime
View raw message