I put this version in my parent pom after you first suggested it, but it seems
like it not using that version, as you pointed out.
-Original Message-
From: Robert Scholte [mailto:rfscho...@apache.org]
Sent: Tuesday, November 13, 2012 9:56 AM
To: Maven Users List
Subject: Re: mvn
I apologize, I replied to the wrong message. Pls disregard.
-Original Message-
From: Ken O'Connell [mailto:koconn...@casenetllc.com]
Sent: Tuesday, November 13, 2012 10:44 AM
To: Maven Users List
Subject: RE: mvn release:prepare cannot git-commit the pom.xml change
I put this version
:
On 13/11/2012 10:43 AM, Ken O'Connell wrote:
I put this version in my parent pom after you first suggested it, but
it seems like it not using that version, as you pointed out.
Did you put it in the dependencyManagement section? That controls
which version the children get to use
/a/apache-extras.org/p/maven-scm-provider-svnjava/wiki/Usage
Op Wed, 07 Nov 2012 21:51:48 +0100 schreef Ken O'Connell
koconn...@casenetllc.com:
I am hoping someone can help me get around this problem?
Trying to implement maven release plugin into our processes, I came
across this issue (http
I am hoping someone can help me get around this problem?
Trying to implement maven release plugin into our processes, I came across this
issue (http://jira.codehaus.org/browse/SCM-406 which is a svn/maven bug with
creating tags: 'tag already exists) in our release:prepare steps while
executing
Hi Manfred,
I have been struggling with the same thing here, and would love to know how to
control this. Under my scenario though, the dependency version (with the
classifier) is just ignored and not updated to the next dev iteration..
-Ken
-Original Message-
From: Manfred Moser
/version
/dependency
…
-Ken
Ken O'Connell
Release Engineer
[cid:image001.jpg@01CD7ED5.4671CF50]
Follow us on [cid:image002.gif@01CD7ED5.4671CF50]
http://twitter.com/#!/CasenetLLC [cid:image003.gif@01CD7ED5.4671CF50]
http://www.linkedin.com/company/casenet-llc
36 Crosby Drive | Bedford, MA
