maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de>
Subject Re: AW: release plugin doesnt update parent pom
Date Sat, 26 Dec 2009 12:25:31 GMT
hi!

since I have not much time left now, I can only ask a quick hint:

What about moving the parent pom.xml (containing the <dependencyManagement>) down into
your build directory and create an own 'build' pom.xml (containing the <modules>) in
the parent directory? This definitely works and is used e.g. by JBoss folks for their 'version-matrix'
(see e.g. the weld build).

LieGrue,
strub

--- is_maximum <mnrz57@gmail.com> schrieb am Sa, 26.12.2009:

> Von: is_maximum <mnrz57@gmail.com>
> Betreff: Re: AW: release plugin doesnt update parent pom
> An: users@maven.apache.org
> Datum: Samstag, 26. Dezember 2009, 13:11
> 
> Thanks.
> Actually NO. it create the release version with the same
> parent SNAPSHOT
> version. This only happens if you have a parent pom and not
> dependency. To
> clarify let me tell you that we have a core-parent project
> which is contains
> only a pom.xml with common dependencies for all projects to
> be inherited. in
> each project if I have a SNAPSHOT version, the release goal
> will fail but in
> our case that core-parent is SNAPSHOT it only asks to
> update and I reply
> 'yes' but no change is applied.
> 
> Yes you're right that the plugin cannot access the scm path
> of the
> core-parent so I supposed that it can read from the remote
> repository and
> find (suggest) the last release version.
> 
> This is useful because we use TeamCity to automatically
> build and generate
> release version say weekly. Because this process runs
> automatically we
> cannot change the SNAPSHOT version manually. 
> 
> Another problem is that the first question the
> release:prepare asks :
> 
> There are still some remaining snapshot dependencies.: Do
> you want to
> resolve them now? (yes/no) no:
> 
> and you see the default is NO and if you answer no the
> process will fail, so
> I think this should be defaulted to YES because when I am
> going to create a
> release (especially in multi-module projects) I need to
> resolve all the
> snapshot version.
> Why I need it to be dafaulted to yes? because we can ask
> our TeamCity
> software to create release version with -B option so
> everything will go
> right
> 
> Do you agree me?
> 
> Thanks for your reply
> 
> 
> 
> 
> 
> struberg wrote:
> > 
> > I think this is a minor bug.
> > 
> > let's sum up the facts:
> > 
> > a.) if you start the mvn release:prepare in a certain
> directory, maven
> > will _not_ automatically step out of this directory.
> > 
> > b.) If the parent pom is outside of your <scm>
> url location, then it
> > cannot get updated.
> > 
> > I think the correct behaviour would be to fail with a
> 'cannot release with
> > a SNAPSHOT dependency' exception in your case. 
> > 
> > You can easily work around this issue if you manually
> release the parent
> > pom first.
> > 
> > LieGrue,
> > strub
> >  
> > --- is_maximum <mnrz57@gmail.com>
> schrieb am Sa, 26.12.2009:
> > 
> >> Von: is_maximum <mnrz57@gmail.com>
> >> Betreff: release plugin doesnt update parent pom
> >> An: users@maven.apache.org
> >> Datum: Samstag, 26. Dezember 2009, 12:10
> >> 
> >> Hi
> >> Consider a multi-module project with a root
> pom.xml and
> >> this root pom has
> >> another parent pom.xml which is considered as
> separated
> >> project 
> >> 
> >> <parent>
> >>    
> >> <groupId>com.foo.core</groupId>
> >>    
> >> <artifactId>core-parent</artifactId>
> >>    
> >> <version>0.0.2-SNAPSHOT</version>
> >> </parent>
> >> 
> >> when executing release:prepare however the command
> asks to
> >> update this
> >> parent dependency to 0.0.3-SNAPSHOT but in action
> no
> >> changes I can see and
> >> this parent pom version remains intact
> >> 
> >> is this a bug or I missed something here?
> >> 
> >> 
> >> -----
> >> --
> >> Regards
> >> 
> >> Mohammad Norouzi
> >> 
> >> Help each other to reach the future faster
> >> 
> >> http://pixelshot.wordpress.com Pixelshot
> Photoblog 
> >> 
> >> http://brainable.blogspot.com Brainable
> Blog 
> >> 
> >> 
> >> -- 
> >> View this message in context:
> >> http://old.nabble.com/release-plugin-doesnt-update-parent-pom-tp26926510p26926510.html
> >> Sent from the Maven - Users mailing list archive
> at
> >> Nabble.com.
> >> 
> >> 
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >> 
> >> 
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Sie sind Spam leid? Yahoo! Mail verfügt über einen
> herausragenden Schutz
> > gegen Massenmails. 
> > http://mail.yahoo.com
> > 
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> > 
> > 
> > 
> 
> 
> -----
> --
> Regards
> 
> Mohammad Norouzi
> 
> Help each other to reach the future faster
> 
> http://pixelshot.wordpress.com Pixelshot Photoblog 
> 
> http://brainable.blogspot.com Brainable Blog 
> 
> 
> -- 
> View this message in context: http://old.nabble.com/release-plugin-doesnt-update-parent-pom-tp26926510p26926790.html
> Sent from the Maven - Users mailing list archive at
> Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.

http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message