release plugin doesnt update parent pom
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 com.foo.core core-parent 0.0.2-SNAPSHOT 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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: release plugin doesnt update parent pom
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 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 schrieb am Sa, 26.12.2009: > Von: is_maximum > 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 > > > > com.foo.core > > core-parent > > 0.0.2-SNAPSHOT > > > 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-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: release plugin doesnt update parent pom
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 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 schrieb am Sa, 26.12.2009: > >> Von: is_maximum >> 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 >> >> >> >> com.foo.core >> >> core-parent >> >> 0.0.2-SNAPSHOT >> >> >> 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-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@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-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: release plugin doesnt update parent pom
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 ) down into your build directory and create an own 'build' pom.xml (containing the ) 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 schrieb am Sa, 26.12.2009: > Von: is_maximum > 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 > 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 > schrieb am Sa, 26.12.2009: > > > >> Von: is_maximum > >> 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 > >> > >> > >> > >> com.foo.core > >> > >> core-parent > >> > >> 0.0.2-SNAPSHOT > >> > >> > >> 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-unsubscr...@maven.apache.org >
Re: AW: release plugin doesnt update parent pom
Thanks Well this definitely works but here in our company there are more than 15 projects each developed by a team and the parent dependencies placed in core-parent are actually needed for all the projects and they are considered as our local framework so I can't ask each project manager to move down all the parent dependencies. This also contradicts the project inheritance claimed by Maven2 As I know this sort of inheritance is used in same Maven project. In repository I can see each component in Maven is inherited from a parent and even that parent is inherited from another one. And May I create an improvement in your issue tracker to set the default asnwer of following question to yes? There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: And can you give me a link about that weld build? I can't find anything useful about it Thanks Mark Struberg wrote: > > 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 > ) down into your build directory and create an own > 'build' pom.xml (containing the ) 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 schrieb am Sa, 26.12.2009: > >> Von: is_maximum >> 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 >> 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 >> schrieb am Sa, 26.12.2009: >> > >> >> Von: is_maximum >> >> 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
