Hi Robert, just wanted to share. I came up with a nice algorithm :-) I do a
dryrun before I run release:branch and after the release:branch, i delete
the POM and rename POM.xml.branch to POM.xml and commit.
--
View this message in context:
http://maven.40175.n5.nabble.com/mvn-release-branch
Thanks Robert. We currently use Maven 2.0.10. I appreciate your help. I'm
totally new with the tool.
--
View this message in context:
http://maven.40175.n5.nabble.com/mvn-release-branch-updating-POM-incorrectly-tp5811978p5812320.html
Sent from the Maven - Users mailing list archive at Nabble.c
he
scm:branch[1]
best,
Robert
[1] http://maven.apache.org/scm/maven-scm-plugin/branch-mojo.html
Op Sat, 01 Nov 2014 22:45:20 +0100 schreef Leonie
:
Good day Robert,
I wondered if you might be aware of a plugin that I can use to update the
scm connection? Then I can create the branch wi
Good day Robert,
I wondered if you might be aware of a plugin that I can use to update the
scm connection? Then I can create the branch with mvn release:branch and
after that is complete I can update the connection with another command. I'm
trying to script a release. Some of the jars re
Hi Leonie,
I wasn't actually speaking about the Maven version, although that explains
why I couldn't see the versions of the plugins, but I was talking about
the maven-release-plugin version.
Because of that I assume you're using maven-release-plugin 2.0 (if you
haven't specified it in the
Thank you Robert. I'm not using the latest maven release. Using 2.0.10. Will
upgrade.
--
View this message in context:
http://maven.40175.n5.nabble.com/mvn-release-branch-updating-POM-incorrectly-tp5811978p5812022.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
bert
[1] https://jira.codehaus.org/browse/MRELEASE
Op Fri, 31 Oct 2014 16:41:04 +0100 schreef Leonie
:
Good day,
I hope someone can assist. I have posted something, but did not get any
reply. When running the release:branch, my branch gets created, but my
scn
connection url in the trunk POM is not updat
Good day,
I hope someone can assist. I have posted something, but did not get any
reply. When running the release:branch, my branch gets created, but my scn
connection url in the trunk POM is not updating to point to the new branch's
URL.
I tried to pinpoint the problem. I opened the P
Good day,
I hope someone can assist. Running mvn release:branch -Dbranchname=foo . The
problem is that my POM file's SCM connection does not always update to point
to my new branch.
I ran this command a few times with different branch names. Sometimes the
SCM connection updates, other time
On 1 Sep 2014, at 03:21, Mark Gibson wrote:
> Ok, thanks Robert.
>
> Sadly this doesn't fit my expectations or needs. I'll look to do something a
> little more manual.
Are you perhaps mixing up tagging and branching?
What you describe sounds like what release:prepare would do.
Regards,
Grah
ase Plugin - release:branch: branch versions not set as
expected
Hi,
IMO branches are mutable, so it makes sense that this will always result in a
-SNAPSHOT Only tags are considered immutable, so that will get a NON Snapshot.
IIRC only the versions of one of the poms will be updated, either the one
stay
.
thanks,
Robert
Op Fri, 29 Aug 2014 17:08:14 +0200 schreef Mark Gibson
:
(please see bottom of email for environment/version information)
I am trying to use the "release:branch" goal to create a branch, setting
the version in the POMs in both the new branch and the working cop
(please see bottom of email for environment/version information)
I am trying to use the "release:branch" goal to create a branch, setting the
version in the POMs in both the new branch and the working copies. No matter
what properties I define on the command line, the release
om 1.1 (say "FIX_1_1"), fix the bug on the branch and
create the bugfix release (say 1.1.0) from this branch
My question: is the release:branch goal supposed to be supporting this
use
case? I assumed yes, as I have found this example:
mvn release:branch -Dbra
to fix a bug in 1.1 immediately, without introducing any of the
changes that have happened on HEAD into the bugfix release, so I need to
start a branch from 1.1 (say "FIX_1_1"), fix the bug on the branch and
create the bugfix release (say 1.1.0) from this branch
My question: is the rele
and that - it has to commit release POMs before it creates a tag,
> because the tag may not be modified.
>
> If I want to perform a release from a specific revision, I have to create a
> branch first. And I thought that release:branch can help me here - it could
> create a branch then u
ub
- Original Message -
From: Laird Nelson
To: Maven Users List
Cc:
Sent: Friday, September 28, 2012 4:47 PM
Subject: Re: What does the "tag" parameter for release:branch do?
On Fri, Sep 28, 2012 at 12:34 AM, Anders Lindgren <
anders.lindg...@cinnober.com> wrote:
I would
strub
- Original Message -
> From: Laird Nelson
> To: Maven Users List
> Cc:
> Sent: Friday, September 28, 2012 4:47 PM
> Subject: Re: What does the "tag" parameter for release:branch do?
>
> On Fri, Sep 28, 2012 at 12:34 AM, Anders Lindgren <
> anders.li
On Fri, Sep 28, 2012 at 12:34 AM, Anders Lindgren <
anders.lindg...@cinnober.com> wrote:
> I would guess that it is used by SCM's like CVS which takes an existing
> tag as base for a new branch.
> The explanation could be better as many of the other parameters
> describes SVN specific usage.
>
Th
Or is could create a tag for the release.
That would make sense, I think.
Ron
On 28/09/2012 3:34 AM, Anders Lindgren wrote:
Hi Laird,
I would guess that it is used by SCM's like CVS which takes an existing
tag as base for a new branch.
The explanation could be better as many of the other param
Hi Laird,
I would guess that it is used by SCM's like CVS which takes an existing
tag as base for a new branch.
The explanation could be better as many of the other parameters
describes SVN specific usage.
/Anders
On Thu, 2012-09-27 at 19:16 +0200, Laird Nelson wrote:
> On Thu, Sep 27, 2012 at
On Thu, Sep 27, 2012 at 9:48 AM, Laird Nelson wrote:
> I can't figure out what the tag parameter is supposed to do for the
> maven-release-plugin branch goal.
>
I'm guessing that this is just a mistake; much of the branch goal seems to
bear a striking similarity to the perform goal; I smell cut-
I can't figure out what the tag parameter is supposed to do for the
maven-release-plugin branch goal. Could someone point me at some alternate
source of documentation?
The maven-release-plugin branch goal simply says (
http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html#tag):
T
Try release:prepare release:perform -Dtag=3.0-b01 -Darguments=-Dtag=3.0-b01
You probably don't need a dedicated branch.
Am 19.02.2012 16:11 schrieb "Dipl.-Ing. Torsten Liermann" <
l...@liermann-it.de>:
>
> Yes, it is unfortunately.
> But, when release:branch ask
Yes, it is unfortunately.
But, when release:branch ask me for the pom version of the branch, the pom will
have exactly this version string (without the SNAPSHOT extension).
I think, i will hack the release plugin for me.
my use case for reaching a fix version without affecting the development
Am 19.02.2012 01:29 schrieb "Dipl.-Ing. Torsten Liermann" <
l...@liermann-it.de>:
>
> Hi, (sorry, I can't speak english :( )
>
> I would like to create a branch with a release version in all pom's
>
> The Snapshot version of the trunk is 3.0.2-SNAPSHOT and the release
version should be 3.0-b01.
C
Looks like you are fighting maven (a loosing battle)
Only tags should have a fixed version
Sent from my iPhone
On 19 Feb 2012, at 00:29, "Dipl.-Ing. Torsten Liermann"
wrote:
> Hi, (sorry, I can't speak english :( )
>
> I would like to create a branch with a release version in all pom's
>
>
Hi, (sorry, I can't speak english :( )
I would like to create a branch with a release version in all pom's
The Snapshot version of the trunk is 3.0.2-SNAPSHOT and the release version
should be 3.0-b01.
Calling maven with
mvn org.apache.maven.plugins:maven-release-plugn:2.2.2:branch
-DbranchN
On Fri, Oct 7, 2011 at 2:14 PM, Laird Nelson wrote:
> It appeared that the tag option was simply ignored.
>
Bug filed against either the plugin option itself or the documentation:
http://jira.codehaus.org/browse/MRELEASE-712
Thanks,
Laird
--
http://about.me/lairdnelson
he resulting branch and the tag from
which I attempted to create it. They should have been nearly identical (but
for pom.xml version upgrades and some scm tweaking). They were not. It
appeared that the tag option was simply ignored.
My command line looked like this:
mvn release:branch -DbranchName=
I couldn't tell from the documentation what the "tag" option is for in the
maven-release-plugin branch goal.
I understand fully what it is for in the prepare goal.
My best guess was that maybe it was the tag from which a branch should be
created? I.e. in Subversion: svn copy ^/tags/the-tag-name-
You don't need to specify the version element in the child. If not
specified, the specified parent.version will be used as version. And then
you will not have this issue.
/Anders
On Tue, Jan 4, 2011 at 19:15, Yaakov Chaikin wrote:
> Hi,
>
> Our project has a parent pom that's located as a sister
Hi,
Our project has a parent pom that's located as a sister module to all
the other modules and the root pom is the rector pom that defines
different profiles of different sets of modules to build.
So, here is roughly our structure:
pom.xml (rector pom.xml which references parent pom.xml for its
On Tue, Nov 9, 2010 at 12:30 PM, Frederic Camblor wrote:
> -DupdateWorkingCopyVersion=false doesn't solve the problem.
>
> Just filed a JIRA : http://jira.codehaus.org/browse/MRELEASE-612
I linked it to http://jira.codehaus.org/browse/MRELEASE-335 (and
closed it as a duplicate).
--
Wendy
-
-DupdateWorkingCopyVersion=false doesn't solve the problem.
Just filed a JIRA : http://jira.codehaus.org/browse/MRELEASE-612
On Mon, Nov 8, 2010 at 11:35 PM, Jon Paynter wrote:
>
> I ran into simmilar behavior when trying to persuade the plugin to make me
> a
> new branch. The plugin seems to
I ran into simmilar behavior when trying to persuade the plugin to make me a
new branch. The plugin seems to get very confused when you change the
default values of updateWorkingCopyVersions or updateBranchVersions.
I did not get a strait answer so i found another solution here:
http://mojo.code
branchName}/
>> hierarchy
>> - Re-Modify pom in working directory to ${tag}
>> - Re-Commit pom on tag 1.0.0
>>
>> I would think it would act this way :
>> - SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/
>> hierarchy
>> - Checkout ${
> Our scm here is git
Which version of the release plugin? Make sure you are using the latest.
>> > so far I have this:
>> > mvn release:branch -DbranchName=TestBranch -DreleaseVersion=2.1.1
>> > -DautoVersionSubmodules=true -DupdateWorkingCopyVersions=false
&g
On Tue, Nov 2, 2010 at 9:44 AM, Zac Thompson wrote:
> On Fri, Oct 29, 2010 at 3:18 PM, Jon Paynter wrote:
> > Im trying to get the release:branch goal to create a new branch in my scm
> > with a given version number, but it doesnt appear to be working. Ive
> tried
> >
releaseVersion}-SNAPSHOT
> - Commit pom (on branch !) & scm
>
> Would it be some reason why the first strategy is applied ?
> Am I badly using release:branch goal ?
>
> Thanks in advance for your precisions.
> Frédéric
>
On Fri, Oct 29, 2010 at 3:18 PM, Jon Paynter wrote:
> Im trying to get the release:branch goal to create a new branch in my scm
> with a given version number, but it doesnt appear to be working. Ive tried
> various combinations of parameters from the release:prepare page, but none
>
Im trying to get the release:branch goal to create a new branch in my scm
with a given version number, but it doesnt appear to be working. Ive tried
various combinations of parameters from the release:prepare page, but none
of them seem to do what I want.
so far I have this:
mvn release:branch
gt; I would think it would act this way :
> - SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/
> hierarchy
> - Checkout ${branchBase}${branchName}/ in working directory
> - Modify pom to ${releaseVersion}-SNAPSHOT
> - Commit pom (on branch !) & scm
>
> Wou
releaseVersion}-SNAPSHOT
- Commit pom (on branch !) & scm
Would it be some reason why the first strategy is applied ?
Am I badly using release:branch goal ?
Thanks in advance for your precisions.
Frédéric
gt; An: Maven Users List
> Betreff: Re: Command line versions for release:branch doesn\'t work as
> described
> On Fri, Sep 24, 2010 at 11:35 AM, Christoph Kutzinski
> wrote:
>
> > Should I reopen MRELEASE-387 or create a new bug?
>
> Since it's partially
On Fri, Sep 24, 2010 at 11:35 AM, Christoph Kutzinski wrote:
> Should I reopen MRELEASE-387 or create a new bug?
Since it's partially working and the issue is already closed and
associated with a version number, opening a new issue would be best.
They can be linked to show the relationship.
--
Hi,
In the documentation of the release plugin it is written that you can specify
the versions via command line properties a la
-Dproject.rel.groupId:artifactId=1.2.3 and so on
(http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html )
According to http://jira.codehaus.org/brow
On Tue, Sep 21, 2010 at 11:07 AM, Christoph Kutzinski wrote:
> Anyone?
What happened when you tried it? :)
Given the lack of response, give it a try and then help out future
users by updating the docs to explain how it works (or filing a bug if
you find something that should work but doesn't.)
Anyone?
Am 20.09.2010 14:40, schrieb Christoph Kutzinski:
Hi,
I've used a release.properties file with the release:prepare/perform goals
successfully. Now I want to know if I can use a similar file with the
release:branch goal, too.
The documentation only mentions passing the new ver
Hi,
I've used a release.properties file with the release:prepare/perform goals
successfully. Now I want to know if I can use a similar file with the
release:branch goal, too.
The documentation only mentions passing the new versions via command line
arguments, but I fear that the numb
Hi,
I have a multi-module project and build ever month releases for this modules.
My process is like:
* Open release branch: "mvn release:branch"
* Release allignments
* Prepare releases: "mvn release:prepare"
* Perform releases: "mvn release:perf
Thanks for your interest to help me out here, Ron. Let me try to explain
more clearly what our current scenario is:
We make use of a company pom that includes everything that may be common to
all projects such as the built-in maven plugins (compiler, resources, etc)
and nail down the versions the
Ryan Connolly wrote:
Hi,
I have a question regarding the m-release-p branch goal. My team was
wondering if it was possible to disallow snapshot versions of plugins and
dependencies when creating certain branches, for example a release candidate
branch. They were boping we could catch tbe u
Hi,
I have a question regarding the m-release-p branch goal. My team was
wondering if it was possible to disallow snapshot versions of plugins and
dependencies when creating certain branches, for example a release candidate
branch. They were boping we could catch tbe use of snapshots before
I found it a little odd that the branch goal of the release plugin does
not change the SCM section back to trunk after it has created the
branch.
Isn't this wrong or am I not fully understanding the work flow?
---
Todd Thiessen
Hi,
On page:
http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html
there is a remark at the bottom to control the branch and current versions
with a command:
mvn --batch-mode release:branch -DbranchName=my-branch-1.2
-Dproject.rel.org.myCompany:projectA=1.2
:40 AM, Allan Ditzel wrote:
>
>> Really? Were you running it from the location the trunk was checked out?
>> For
>> us, if we do a mvn release:prepare in the location of the trunk, then
>> release:perform, and then cd into target/checkout and from there do mvn
>> release
ation of the trunk, then
release:perform, and then cd into target/checkout and from there do mvn
release:branch -DbranchName=my-branch -DupdateBranchVersions=true
-DupdateWorkingCopyVersions=false (interactive mode) then we're able to
branch without many problems. Also, if we do an svn co of a t
ase:prepare in the location of the trunk, then
> release:perform, and then cd into target/checkout and from there do mvn
> release:branch -DbranchName=my-branch -DupdateBranchVersions=true
> -DupdateWorkingCopyVersions=false (interactive mode) then we're able to
> branch without m
Really? Were you running it from the location the trunk was checked out? For
us, if we do a mvn release:prepare in the location of the trunk, then
release:perform, and then cd into target/checkout and from there do mvn
release:branch -DbranchName=my-branch -DupdateBranchVersions=true
personally, I couldn' t get release:branch to work at all, interactively or
batch.
On Wed, Oct 14, 2009 at 2:23 PM, Allan Ditzel wrote:
> Hi,
>
> I'm trying to make a branch from a tag in batch mode using the release
> plugin. The pom in the tag has its version set to 0
ctive
mode I'm able to create the branch correctly. Here is the command I am
executing:
mvn -B release:branch -DbranchName=testBranch-0.2.X
-DupdateBranchVersions=true -DupdateWorkingCopyVersions=false
-Dproject.rel.test.release_management:test-project=0.2.1 -Ptestprofile
I have also trie
2009, 11h24mn 19s
Objet : release:rollback after a release:branch
Hi,
I use :
mvn release:branch -DbranchName=branche -DupdateBranchVersions=false
-DupdateWorkingCopyVersions=false
And I got this error :
[INFO] Unable to branch SCM
Provider message:
The svn branch command failed.
Command output
Hi,
I use :
mvn release:branch -DbranchName=branche -DupdateBranchVersions=false
-DupdateWorkingCopyVersions=false
And I got this error :
[INFO] Unable to branch SCM
Provider message:
The svn branch command failed.
Command output:
svn: Commit failed (details follow):
svn: File
; I have the same question. What is the correct steps in order to create a
> branch from a tag using the release:branch goal?
>
> Thank you,
> Jason
>
>
> Nick Stolwijk wrote:
>>
>> Can someone comment on this mail? Is the release:branch goal fitted to
>> c
I have the same question. What is the correct steps in order to create a
branch from a tag using the release:branch goal?
Thank you,
Jason
Nick Stolwijk wrote:
>
> Can someone comment on this mail? Is the release:branch goal fitted to
> create a branch from a tag and update th
Can someone comment on this mail? Is the release:branch goal fitted to create a
branch from a tag and update the version numbers?
With regards,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: [EMAIL PROTECTED
I am trying to create a branch from a tag with the release plugin. I have a
checkout from trunk and try the following command:
mvn release:branch -Dtag=TestProject-1.4 -DbranchName=TestProject-1.4.x s
-DupdateBranchVersions=true
I was expecting that a branch (/branches/TestProject-1.4.x) was
ND request failed on '/repositories/modules/messaging/branches'
svn: '/repositories/modules/messaging/branches' path not found
So I have to manualy create branches folder remotely and re-run the
release:branch. Is there a reason to this?
I used Maven 2.0.9 with clean local repo.
Regards,
Borut
I have since found out that the Maven SCM implementation for Perforce
does not support the release:branch goal
Refer to http://docs.codehaus.org/display/SCM/SCM+Matrix
This probably explains the error but would have been more helpful if the
Maven documentation actually linked to this information
I've run into this issue as well. Tried lots of configuration options to
see if I work around it, but gave up in the end.
-Original Message-
From: Bracewell, Robert [mailto:[EMAIL PROTECTED]
Sent: 06 May 2008 12:42
To: users@maven.apache.org
Subject: Perforce and release:branch goa
Hi all,
Investigating the use of the release:branch goal but running into
issues. The error is listed below. I have to say that I have no issue
using the release:prepare goal so everything seems to be in place with
the SCM section of the pom.
Does anyone use the release:branch goal in
Hi,
why is branch name stated as optional at
http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html when
it clearly isn't? Also the example at
http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html is
saying
To execute this step, run:
mvn release:branch
Thanks for the quick reply, Emmanuel.
I upgraded to the beta-7 plugin version, and I am having better results.
What the plugin doco does specify is that the release:branch goal should be
invoked from a checkout location with the revision/tag you want to branch
from. (i.e. tags/).
I used the
ndard layout)
The release plugin doco doesn't indicate where I should be running the
release:branch goal from...
If I run it from the trunk, it creates a branch from the current development
version, regardless of whether I give it -Dtag=.
If I run it from a tag folder, it complains that I do
Hello,
I am trying to create a branch based on a release tag. The branch would be
used for maintenance purposes. (I am using an svn scm provider with the
standard layout)
The release plugin doco doesn't indicate where I should be running the
release:branch goal from...
If I run it fro
t
Re: Maven Release Plugin release:branch goal
Do you have tried with branchName=branchName/projectName ?
Emmanuel
[EMAIL PROTECTED] a écrit :
> Hi Everyone,
>
> Is there anyway to tell the release plugin, when doing the branch goal,
> the directory where to place the code in the bra
Do you have tried with branchName=branchName/projectName ?
Emmanuel
[EMAIL PROTECTED] a écrit :
Hi Everyone,
Is there anyway to tell the release plugin, when doing the branch goal,
the directory where to place the code in the branch. For example the
plugin copies your code to the branches/<
Hi Everyone,
Is there anyway to tell the release plugin, when doing the branch goal,
the directory where to place the code in the branch. For example the
plugin copies your code to the branches/<-DbranchName> directory. I would
like it to place the code in the branches/<-DbranchName>/projectN
79 matches
Mail list logo
