Hi, So, we should not have <tag> in there at all?
Say I wanted to release Maven 2.2.2 from the branch, would this be the correct recipe? 1. Clone the Git repo for Maven 2. "Select" the branch/head called "maven-2.2.x" using Git 3. mvn release:prepare, mvn release:perform If that is correct how will someone who does a "check out" of the tag know which branch it originated from, without looking in Git history? Sorry if I'm using the wrong Git words here. Please correct me if I do, since I'm still learning... On Sat, Aug 10, 2013 at 2:54 PM, Olivier Lamy <ol...@apache.org> wrote: > On 10 August 2013 21:12, Dennis Lundberg <denn...@apache.org> wrote: >> Hi, >> >> I'm looking at the sources for Maven core in Git, which I'm learning >> as I go along. >> >> "master" is at version 3.1.1-SNAPSHOT and has this in its pom.xml >> <scm> >> >> <connection>scm:git:https://git-wip-us.apache.org/repos/asf/maven.git</connection> >> >> <developerConnection>scm:git:https://git-wip-us.apache.org/repos/asf/maven.git</developerConnection> >> <url>https://git-wip-us.apache.org/repos/asf?p=maven.git</url> >> <tag>HEAD</tag> >> </scm> >> >> The head "maven-3.0.x" is at version 3.0.6-SNAPSHOT and has this in its >> pom.xml >> <scm> >> >> <connection>scm:git:https://git-wip-us.apache.org/repos/asf/maven.git</connection> >> >> <developerConnection>scm:git:https://git-wip-us.apache.org/repos/asf/maven.git</developerConnection> >> <url>https://git-wip-us.apache.org/repos/asf?p=maven.git</url> >> <tag>HEAD</tag> >> </scm> >> >> Since this is identical to what is in "master" I don't think this >> would work if you tried to do a release using the Release Plugin. >> Wouldn't that release what is specified in <tag> i.e. "HEAD". Now, I >> have looked through our documentation and used Google to find a >> solution, but to no avail. From what I have gathered we should change >> the value of <tag>, but to what? Would it involve >> "ref/heads/maven-3.0.x"? >> >> The head "maven-2.2.x" is at version 2.2.2-RC1-SNAPSHOT and has this >> in its pom.xml >> <scm> >> >> <connection>scm:svn:http://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x</connection> >> >> <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x</developerConnection> >> >> <url>http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x</url> >> </scm> >> >> Obviously this has not been updated since the move to Git, which is >> one of the things I'm trying to fix. > > scm url will be the same for all branches. > It simply depend of the branch you are working on locally. > btw the <tag>HEAD</tag> in maven-3.0.x branch is wrong. > IHMO It's something to improve in the release plugin to put here the > current branch in use. > >> >> Hopefully someone who has made a release using Maven Release Plugin >> from a Git branch can shed some light on this. >> >> -- >> Dennis Lundberg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
