Maven-release-plugin checking in the pom twice

[Mr Debasis]

Hi All,
 I am using release-plugin.i observed it is checking in the pom twice.one is
for release and other is for next development iteration.
The second time check in is keeping me in problem.
I am having 7 submodules.release checkin is working perfectly i,e -it is
changing the version no of all the submodules pom.and creating the tag.works
fine

when second time it checks in it is again changing the version of the pom
i,e old version.which i don,t want.
If I released my project then again why should i keep working in the older
version i don't understand.

Example-my version was-3.0
my release version is 3.1.
but in the next development iteration the parent pom version is 3.1-snapshot
and submodules version becomes 3.0.but i want parent pom version should be
3.1-snapshot and submodules should be 3.1 not 3.0.

How can i achieve that.other wise i can't use this plugin .i need to change
the version no of my pom manually and creating tag manually.

Thanks,
Debasis

--
View this message in context: http://old.nabble.com/Maven-release-plugin-checking-in-the-pom-twice-tp26251139p26251139.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[David C. Hicks]

Typically, you will be developing a SNAPSHOT version of the release
version.  In other words, you might be working on 3.0-SNAPSHOT.  When
you do the release, you should release 3.0.  Your next development
version would then be 3.1-SNAPSHOT.  Your submodules will generally have
the same version as your master.

It sounds to me like the release plugin is doing exactly what it's
supposed to do, though.

Dave

DebasisM wrote:

> Hi All,
>  I am using release-plugin.i observed it is checking in the pom twice.one is
> for release and other is for next development iteration.
> The second time check in is keeping me in problem.
> I am having 7 submodules.release checkin is working perfectly i,e -it is
> changing the version no of all the submodules pom.and creating the tag.works
> fine
>
> when second time it checks in it is again changing the version of the pom
> i,e old version.which i don,t want.
> If I released my project then again why should i keep working in the older
> version i don't understand.
>
> Example-my version was-3.0
> my release version is 3.1.
> but in the next development iteration the parent pom version is 3.1-snapshot
> and submodules version becomes 3.0.but i want parent pom version should be
> 3.1-snapshot and submodules should be 3.1 not 3.0.
>
> How can i achieve that.other wise i can't use this plugin .i need to change
> the version no of my pom manually and creating tag manually.
>
> Thanks,
> Debasis
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Dan Tran]

most likely is your pom configuration.

I would suggest you to use a well know maven project with multiple
modules sub module and try to figure what is different between yours
and the well one.

I would pick http://svn.apache.org/repos/asf/maven/scm/trunk or

http://svn.apache.org/repos/asf/maven/surefire/trunk

good luck

-Dan


On Sat, Nov 7, 2009 at 9:30 PM, David C. Hicks <[hidden email]> wrote:

> Typically, you will be developing a SNAPSHOT version of the release
> version.  In other words, you might be working on 3.0-SNAPSHOT.  When
> you do the release, you should release 3.0.  Your next development
> version would then be 3.1-SNAPSHOT.  Your submodules will generally have
> the same version as your master.
>
> It sounds to me like the release plugin is doing exactly what it's
> supposed to do, though.
>
> Dave
>
> DebasisM wrote:
>> Hi All,
>>  I am using release-plugin.i observed it is checking in the pom twice.one is
>> for release and other is for next development iteration.
>> The second time check in is keeping me in problem.
>> I am having 7 submodules.release checkin is working perfectly i,e -it is
>> changing the version no of all the submodules pom.and creating the tag.works
>> fine
>>
>> when second time it checks in it is again changing the version of the pom
>> i,e old version.which i don,t want.
>> If I released my project then again why should i keep working in the older
>> version i don't understand.
>>
>> Example-my version was-3.0
>> my release version is 3.1.
>> but in the next development iteration the parent pom version is 3.1-snapshot
>> and submodules version becomes 3.0.but i want parent pom version should be
>> 3.1-snapshot and submodules should be 3.1 not 3.0.
>>
>> How can i achieve that.other wise i can't use this plugin .i need to change
>> the version no of my pom manually and creating tag manually.
>>
>> Thanks,
>> Debasis
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]