You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by aldana <al...@gmx.de> on 2008/06/20 12:19:36 UTC
maven release-plugin: create-branch and behaviour of update
dependencies
hi,
i am using maven-release plugin to create branches. updating its own version
and creating project in scm works fine.
what i do miss is that the update of snapshot versions of dependencies is
not asked for.
but when branching sometimes the actual branch should update snapshot
dependencies too, because sometimes they are branched also (for isolation
reasons).
what i expect is that after executing release:branch, maven asks me if i
want to upgrade version for each snapshot dependency.
the parameter of goal release:branch 'updateDependencies' does not seem to
give me this option.
has anybody succeeded or does somebody know whether this works at all?
thanks.
-----
manuel aldana
aldana((at))gmx.de
software-engineering blog: http://www.aldana-online.de
--
View this message in context: http://www.nabble.com/maven-release-plugin%3A-create-branch-and-behaviour-of-update-dependencies-tp18026487p18026487.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
RE: maven release-plugin: create-branch and behaviour of update
dependencies
Posted by aldana <al...@gmx.de>.
hi marco,
thanks for your thoughts.
of course i wouldn't want the plugin to automatically decide what to
upgrade. what i would like is that it asks me in command-line dialog way
which dependency-snapshots i want to upgrade in dependant project.
you're right to map the coupling of branch-packages by maven multimodule
concept. so far we didn't go for it for historic and IDE plugin reasons, but
we are thinking to migrate soon.
Beelen, M. - SPLXL wrote:
>
> Hello Manuel,
>
> I'm not surprised that the maven-release-plugin doesn't interfere with
> the versions of dependencies in a project.
>
> IMHO you should change your expectations of the release:branche. The
> maven-release-plugin works on the current artifact. Whether or not other
> artifacts have been changed is out-of-scope for the release-plugin.
>
> I just wonder if you really would want maven to 'guess' which
> dependencies should be updated as well and if so: based on what argument
> should dependencies be allegeable for 'automatic updating'.
>
> It appairs to me that you want your projects to have a strong link
> concerning the versionNumbers of the artifacts.
> - Project A version 1.0-SNAPSHOT depends on Project B version version
> 1.0-SNAPSHOT
> - Project A version 1.1-SNAPSHOT depends on Project B version version
> 1.1-SNAPSHOT
>
> If that assumption is correct and you really want your artifact to be
> that tightly coupled, I would suggest that you move to a
> multi-module-project-structure[1], with all related modules in the same
> trunk/brances.
>
>
> HTH.
>
>
> [1] : http://docs.codehaus.org/display/MAVENUSER/Multi-modules+projects
>
>
> With kind regards,
> Marco Beelen
> ~Software Engineer~
>
> Iprofs BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> www.iprofs.nl
>
>
>
> -----Original Message-----
> From: aldana [mailto:aldana@gmx.de]
> Sent: Friday, June 20, 2008 12:20 PM
> To: users@maven.apache.org
> Subject: maven release-plugin: create-branch and behaviour of update
> dependencies
>
>
> hi,
>
> i am using maven-release plugin to create branches. updating its own
> version and creating project in scm works fine.
>
> what i do miss is that the update of snapshot versions of dependencies
> is not asked for.
> but when branching sometimes the actual branch should update snapshot
> dependencies too, because sometimes they are branched also (for
> isolation reasons).
>
> what i expect is that after executing release:branch, maven asks me if i
> want to upgrade version for each snapshot dependency.
>
> the parameter of goal release:branch 'updateDependencies' does not seem
> to give me this option.
>
> has anybody succeeded or does somebody know whether this works at all?
> thanks.
>
> -----
> manuel aldana
> aldana((at))gmx.de
> software-engineering blog: http://www.aldana-online.de
> --
> View this message in context:
> http://www.nabble.com/maven-release-plugin%3A-create-branch-and-behaviou
> r-of-update-dependencies-tp18026487p18026487.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
>
> **********************************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee
> only. If you are not the addressee, you are notified that no part
> of the e-mail or any attachment may be disclosed, copied or
> distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately
> by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
> and/or its employees shall not be liable for the incorrect or
> incomplete transmission of this e-mail or any attachments, nor
> responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> registered number 33014286
> **********************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
-----
manuel aldana
aldana((at))gmx.de
software-engineering blog: http://www.aldana-online.de
--
View this message in context: http://www.nabble.com/maven-release-plugin%3A-create-branch-and-behaviour-of-update-dependencies-tp18026487p18030877.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
RE: maven release-plugin: create-branch and behaviour of update dependencies
Posted by "Beelen, M. - SPLXL" <Ma...@klm.com>.
Hello Manuel,
I'm not surprised that the maven-release-plugin doesn't interfere with
the versions of dependencies in a project.
IMHO you should change your expectations of the release:branche. The
maven-release-plugin works on the current artifact. Whether or not other
artifacts have been changed is out-of-scope for the release-plugin.
I just wonder if you really would want maven to 'guess' which
dependencies should be updated as well and if so: based on what argument
should dependencies be allegeable for 'automatic updating'.
It appairs to me that you want your projects to have a strong link
concerning the versionNumbers of the artifacts.
- Project A version 1.0-SNAPSHOT depends on Project B version version
1.0-SNAPSHOT
- Project A version 1.1-SNAPSHOT depends on Project B version version
1.1-SNAPSHOT
If that assumption is correct and you really want your artifact to be
that tightly coupled, I would suggest that you move to a
multi-module-project-structure[1], with all related modules in the same
trunk/brances.
HTH.
[1] : http://docs.codehaus.org/display/MAVENUSER/Multi-modules+projects
With kind regards,
Marco Beelen
~Software Engineer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-----Original Message-----
From: aldana [mailto:aldana@gmx.de]
Sent: Friday, June 20, 2008 12:20 PM
To: users@maven.apache.org
Subject: maven release-plugin: create-branch and behaviour of update
dependencies
hi,
i am using maven-release plugin to create branches. updating its own
version and creating project in scm works fine.
what i do miss is that the update of snapshot versions of dependencies
is not asked for.
but when branching sometimes the actual branch should update snapshot
dependencies too, because sometimes they are branched also (for
isolation reasons).
what i expect is that after executing release:branch, maven asks me if i
want to upgrade version for each snapshot dependency.
the parameter of goal release:branch 'updateDependencies' does not seem
to give me this option.
has anybody succeeded or does somebody know whether this works at all?
thanks.
-----
manuel aldana
aldana((at))gmx.de
software-engineering blog: http://www.aldana-online.de
--
View this message in context:
http://www.nabble.com/maven-release-plugin%3A-create-branch-and-behaviou
r-of-update-dependencies-tp18026487p18026487.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
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org