ws-commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <andreas.veit...@gmail.com>
Subject Re: [Transport] Incrementing version number of trunk
Date Sat, 12 Dec 2009 10:08:26 GMT
mvn release:prepare executes the whole process, including creation of
a branch, but here we only need the last step (Bump the version in the
POMs to a new value y-SNAPSHOT). I will do it by hand.

Andreas

On Sat, Dec 12, 2009 at 05:47, Ruwan Linton <ruwan.linton@gmail.com> wrote:
> Well it seems we can :-)
>
> http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html
>
> [Disclaimer: I didn't try this]
>
> Thanks,
> Ruwan
>
> On Sat, Dec 12, 2009 at 10:16 AM, Ruwan Linton <ruwan.linton@gmail.com>
> wrote:
>>
>> Andreas,
>>
>> AFAIK, there is no means of changing the versions with the release plugin,
>> what I normally do is a search and replace. Since we shouldn't have any
>> SNAPSHOT dependencies when releasing, hopefully that will not affect the
>> other deps. A grep and sed, if you are on linux and on a terminal would do
>> the trick as well, which could be automated if you need to.
>>
>> We did this and prepared a release script once, but that is specific to
>> the product that you are releasing, for example [1].
>>
>> May be we could extend the release plugin or write a new plugin. :-)
>>
>> [1] - https://svn.wso2.org/repos/wso2/people/ruwan/scripts/release-2.0.sh
>>
>> Thanks,
>> Ruwan
>>
>> On Sat, Dec 12, 2009 at 12:27 AM, Andreas Veithen
>> <andreas.veithen@gmail.com> wrote:
>>>
>>> Ruwan,
>>>
>>> Do you know if changing the version number is something that can be
>>> done using the maven-release-plugin, or do we have to do it manually?
>>>
>>> Andreas
>>>
>>> On Fri, Dec 11, 2009 at 16:47, Ruwan Linton <ruwan.linton@gmail.com>
>>> wrote:
>>> > [missed commons-dev in the previous mail]
>>> >
>>> > Because OSGi versioning has a requirement that the bundle version has
>>> > to be
>>> > major.minor.micro.macro where as while macro can contain alpha
>>> > characters
>>> > all the other has to be numeric.
>>> >
>>> > Yes, we could keep the bundle version to that format and change the
>>> > physical
>>> > jar version name, but then again there is an issue with OSGi for them
>>> > to be
>>> > the same when running as a feature.
>>> >
>>> > There fore +1 for 1.1.0-SNAPSHOT
>>> >
>>> > Thanks,
>>> > Ruwan
>>> >
>>> > On Fri, Dec 11, 2009 at 10:00 AM, Amila Suriarachchi
>>> > <amilasuriarachchi@gmail.com> wrote:
>>> >>
>>> >> hi,
>>> >>
>>> >> What is the reason for keeping version number in the trunk?
>>> >> I think best thing is to use trunk as SNAPSHOT and once a branch is
>>> >> cut
>>> >> for
>>> >> 1.1 released then it should name as 1.1-SNAPSHOT.
>>> >>
>>> >> thanks,
>>> >> Amila.
>>> >>
>>> >> On Fri, Dec 11, 2009 at 2:10 AM, Andreas Veithen
>>> >> <andreas.veithen@gmail.com> wrote:
>>> >>>
>>> >>> All,
>>> >>>
>>> >>> I noticed that the trunk of the transport project has the same
>>> >>> version
>>> >>> number (1.0-SNAPSHOT) than the 1.0.0 branch. This causes some
>>> >>> confusion [1]. Obviously we should increment the version number
of
>>> >>> the
>>> >>> trunk. I propose 1.1-SNAPSHOT or 1.1.0-SNAPSHOT. Any preference?
>>> >>>
>>> >>> Andreas
>>> >>>
>>> >>> [1] http://markmail.org/message/uonvk2uh2nwjv7lq
>>> >>>
>>> >>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> >>> For additional commands, e-mail: dev-help@synapse.apache.org
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Amila Suriarachchi
>>> >> WSO2 Inc.
>>> >> blog: http://amilachinthaka.blogspot.com/
>>> >
>>> >
>>> >
>>> > --
>>> > Ruwan Linton
>>> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>>> > WSO2 Inc.; http://wso2.org
>>> > email: ruwan@wso2.com; cell: +94 77 341 3097
>>> > blog: http://ruwansblog.blogspot.com
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>
>>
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>

Mime
View raw message