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.

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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to