AFAIR in eclipse m2e ( I don't use it anymore ) you can checkout the code of any maven dependency/project (materialize feature). I'm almost sure that it is using informations from SCM part in the POM to do it. I think it isn't the only usage of it. I'm not 100% satisfied of this usage because such information can change in the future (imagine a SVN -> git migration or any change in the scm hosting of a project - URL ...)
--------- Arnaud Le 10 août 2013 à 20:02, Mark Struberg <[email protected]> a écrit : > I found that most people use > <pushChanges>false and > <localCheckout>true > > Which renders most of the <tag> stuff useless in GIT. > > LieGrue, > strub > > > > > ----- Original Message ----- >> From: Fred Cooke <[email protected]> >> To: Maven Developers List <[email protected]> >> Cc: >> Sent: Saturday, 10 August 2013, 15:19 >> Subject: Re: What is the correct Git SCM URL for a branch? >> >> Convention over configuration is fine. Dictatorships end badly. Make it the >> convention, and allow it to be configured off. This is where Maven has >> always failed from time to time, especially in the old days. The less it's >> true, the better. >> >> On Sat, Aug 10, 2013 at 3:13 PM, Olivier Lamy <[email protected]> wrote: >> >>> On 10 August 2013 23:06, Fred Cooke <[email protected]> wrote: >>>> Please keep such information leakage optional. The editing of, and >> indeed >>>> adding of, the "tag" element by the release plugin should >> already be >>>> optional IMO. >>> >>> Why? >>> With such information I know which tag has been used to build >>> artifacts. ( >> http://repo.maven.apache.org/maven2/org/apache/maven/maven/3.0.5/maven-3.0.5.pom >>> ) >>> Without this it's not possible with only the git url. >>> For people/tools using scm informations for rebuilding packages etc.. >>> it can be very interesting. >>> >>> >>>> Especially if it breaks formatting of the POM, which it does >>>> in some cases, at least. And yeah, I know why, and I know it's not >> a >>>> trivial fix. (Thanks to Robert for educating me many months ago). >>>> >>>> On Sat, Aug 10, 2013 at 2:54 PM, Olivier Lamy <[email protected]> >> wrote: >>>> >>>>> On 10 August 2013 21:12, Dennis Lundberg >> <[email protected]> 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: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>>> >>>>> -- >>>>> Olivier Lamy >>>>> Ecetera: http://ecetera.com.au >>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>> >>> >>> >>> -- >>> Olivier Lamy >>> Ecetera: http://ecetera.com.au >>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
