You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dennis Lundberg <de...@apache.org> on 2013/08/10 13:12:00 UTC
What is the correct Git SCM URL for a branch?
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Hervé BOUTEMY <he...@free.fr>.
here is current state:
- using github link does fix web access in modules problems: see actual
3.1.1staging [1]
- with MPIR-291, branches and tags are supported: "git clone --branch <tag>"
instructions are generated
- with MPIR-290, I did a hack to remove module path from git clone
instructions
with these enhancements, I think git in reports is consistent now: no more
non-working instructions generated
What is still missing IMHO is:
- git scm transform rule during release to modify web access link
- update in scm component scm:git: format to support module path at end, to
replace MPIR-290 hack with something better designed
any other idea?
anybody to work on some of the remaining points?
Regards,
Hervé
[1] http://maven.apache.org/ref/3-LATEST/maven-core/source-repository.html
Le lundi 2 septembre 2013 20:13:42 Robert Scholte a écrit :
> Op Mon, 02 Sep 2013 07:13:27 +0200 schreef Chris Graham
>
> <ch...@gmail.com>:
> > On Sun, Sep 1, 2013 at 8:21 PM, Hervé BOUTEMY <he...@free.fr>
> >
> > wrote:
> >> if I read Jazz SCM url format [1], in a multi-module build, scm info
> >> automatically calculated from root to modules (ie appending artifact-id)
> >> will
> >> give wrong scm info, no?
> >> did you try it?
> >
> > All of my testing was for multi module projects. Nested ones. So it was
> > never a problem.
> >
> > There is an ugly work around/hack (that automatically happens) for
> > non-nest
> > projects. So add a dummy path to the end of the Component name, and it
> > seems to work out.
> >
> > As the SCM section is only in the root pom, it does not seem to be
> > effected.
> >
> > A tag (in maven SCM terms) is the equivalent of a snapshot of a component
> > (in Jazz SCM terms). Technically, it is a collection of Change Sets, but
> > effectively works out to be a "tag" for a given component.
> >
> > So I think of all modules as a part of the same component (just like all
> > modules under a trank/branch in svn). so it tends to work nicely.
> >
> >> there are 2 other parts:
> >> - m-release-p: did you add any logic to deal with plugin scm info
> >> modification
> >> when tagging a version?
> >
> > I didn't, but I think that Robert had to add some logic in there that
> > applied to Jazz (and I think some others as well). I'd have to go back
> > and
> > look.
>
> Indeed, there are several ScmTranslator implementations, see
> http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/sr
> c/main/java/org/apache/maven/shared/release/scm/ It's still a dream to
> remove any scm implementation specific code from this project...
>
> Robert
>
> >> - m-pir-p: when you do a checkout (or clone, or view, I don't know the
> >> exact
> >> term for Jazz), IIUC, you get a repository copy: did you write some
> >> instructions in the generated page to cd to module base directory?
> >> (again
> >> for
> >> multi-module builds)
> >
> > You're the first to ask about this.
> >
> > I just quickly run a site build, and the generated URL's in the Source
> > Repository pages are wrong, as they assume the ability to check out just
> > one module of a multi module project (eg SVN terms, a svn checkout of
> > .../trunk/Module). This shows the CVS/SVN embedded thinking that is
> > pretty
> > much implicit across much of the SCM and Release modules.
> >
> > I do not believe that it is possible to check out (via the command line,
> > I
> > think that you _may_ be able to via the GUI) one sub dir (ie Module) of a
> > Jazz SCM Component.
> >
> > A checkout in Jazz SCM terms is a "Load". :-)
> >
> > See:
> >
> > http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-jazz/in
> > dex.html
> >
> >
> > [1] http://maven.apache.org/scm/jazz.html
> >
> >> Le dimanche 1 septembre 2013 09:54:39 Chris Graham a écrit :
> >> > I did something similar in the Jazz provider. It's a complex URL, or
> >>
> >> can
> >> be
> >>
> >> > if it needs to be, but it's still a single line.
> >> >
> >> > It's just a matter of making the parser smarted. And that's local to
> >>
> >> the
> >>
> >> > provider, so go nuts. I also put lots of unit tests in there to
> >>
> >> illustrate
> >>
> >> > the correct and incorrect usage.
> >> >
> >> > -Chris
> >> >
> >> > On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY <herve.boutemy@free.fr
> >> >
> >> >wrote:
> >> > > Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit :
> >> > > > I agree that a single SCM line doesn't really match anymore with
> >>
> >> systems
> >>
> >> > > > like DSCM (git, Mercurial)
> >> > > > It would have been better if we could think of a better way to
> >>
> >> define
> >>
> >> > > this
> >> > >
> >> > > > in a newer POM-model.
> >> > >
> >> > > it was overkill at the time Maven was done, and even today,
> >>
> >> splitting
> >> scm
> >>
> >> > > developerConnection into 3 parts seems overkill for classical SCMs,
> >>
> >> even
> >>
> >> > > if
> >> > > doable
> >> > >
> >> > > notice that even with "single SCM line", we can have multiple
> >>
> >> fields,
> >> like
> >>
> >> > > we
> >> > > already have for example with git to distinguish fetch and push
> >>
> >> urls:
> >> > > <developerConnection>scm:git:
> >> > > [fetch=]
> >>
> >> http://mywebserver.org/path_to_repository[push=]ssh://username@otherserve
> >> r
> >>
> >> > > :8898/~/repopath.git </developerConnection>
> >> > >
> >> > > in the same spirit, we could support a branch and a path parts
> >>
> >> > > <developerConnection>scm:git:
> >> https://git-wip-us.apache.org/repos/asf/maven.git[branch=]maven-3.0.x[pat
> >> h
> >>
> >> > > =]/maven-core </developerConnection>
> >> > >
> >> > > with such scm url format, we have the structure we like without POM
> >>
> >> format
> >>
> >> > > change, and module value inheritance by adding artifact-id to the
> >>
> >> url
> >>
> >> > > stays
> >> > > simple and consistent
> >> > >
> >> > >
> >> > > Regards,
> >> > >
> >> > > Hervé
> >>
> >> ---------------------------------------------------------------------
> >>
> >> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> > > For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Robert Scholte <rf...@apache.org>.
Op Mon, 02 Sep 2013 07:13:27 +0200 schreef Chris Graham
<ch...@gmail.com>:
> On Sun, Sep 1, 2013 at 8:21 PM, Hervé BOUTEMY <he...@free.fr>
> wrote:
>
>> if I read Jazz SCM url format [1], in a multi-module build, scm info
>> automatically calculated from root to modules (ie appending artifact-id)
>> will
>> give wrong scm info, no?
>> did you try it?
>>
>>
> All of my testing was for multi module projects. Nested ones. So it was
> never a problem.
>
> There is an ugly work around/hack (that automatically happens) for
> non-nest
> projects. So add a dummy path to the end of the Component name, and it
> seems to work out.
>
> As the SCM section is only in the root pom, it does not seem to be
> effected.
>
> A tag (in maven SCM terms) is the equivalent of a snapshot of a component
> (in Jazz SCM terms). Technically, it is a collection of Change Sets, but
> effectively works out to be a "tag" for a given component.
>
> So I think of all modules as a part of the same component (just like all
> modules under a trank/branch in svn). so it tends to work nicely.
>
>
>> there are 2 other parts:
>> - m-release-p: did you add any logic to deal with plugin scm info
>> modification
>> when tagging a version?
>>
>
> I didn't, but I think that Robert had to add some logic in there that
> applied to Jazz (and I think some others as well). I'd have to go back
> and
> look.
>
Indeed, there are several ScmTranslator implementations, see
http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/java/org/apache/maven/shared/release/scm/
It's still a dream to remove any scm implementation specific code from
this project...
Robert
>
>> - m-pir-p: when you do a checkout (or clone, or view, I don't know the
>> exact
>> term for Jazz), IIUC, you get a repository copy: did you write some
>> instructions in the generated page to cd to module base directory?
>> (again
>> for
>> multi-module builds)
>>
>
> You're the first to ask about this.
>
> I just quickly run a site build, and the generated URL's in the Source
> Repository pages are wrong, as they assume the ability to check out just
> one module of a multi module project (eg SVN terms, a svn checkout of
> .../trunk/Module). This shows the CVS/SVN embedded thinking that is
> pretty
> much implicit across much of the SCM and Release modules.
>
> I do not believe that it is possible to check out (via the command line,
> I
> think that you _may_ be able to via the GUI) one sub dir (ie Module) of a
> Jazz SCM Component.
>
> A checkout in Jazz SCM terms is a "Load". :-)
>
> See:
>
> http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-jazz/index.html
>
>
> [1] http://maven.apache.org/scm/jazz.html
>>
>> Le dimanche 1 septembre 2013 09:54:39 Chris Graham a écrit :
>> > I did something similar in the Jazz provider. It's a complex URL, or
>> can
>> be
>> > if it needs to be, but it's still a single line.
>> >
>> > It's just a matter of making the parser smarted. And that's local to
>> the
>> > provider, so go nuts. I also put lots of unit tests in there to
>> illustrate
>> > the correct and incorrect usage.
>> >
>> > -Chris
>> >
>> > On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY <herve.boutemy@free.fr
>> >wrote:
>> > > Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit :
>> > > > I agree that a single SCM line doesn't really match anymore with
>> systems
>> > > > like DSCM (git, Mercurial)
>> > > > It would have been better if we could think of a better way to
>> define
>> > >
>> > > this
>> > >
>> > > > in a newer POM-model.
>> > >
>> > > it was overkill at the time Maven was done, and even today,
>> splitting
>> scm
>> > > developerConnection into 3 parts seems overkill for classical SCMs,
>> even
>> > > if
>> > > doable
>> > >
>> > > notice that even with "single SCM line", we can have multiple
>> fields,
>> like
>> > > we
>> > > already have for example with git to distinguish fetch and push
>> urls:
>> > > <developerConnection>scm:git:
>> > > [fetch=]
>> > >
>> http://mywebserver.org/path_to_repository[push=]ssh://username@otherserver
>> > > :8898/~/repopath.git </developerConnection>
>> > >
>> > > in the same spirit, we could support a branch and a path parts
>> > > <developerConnection>scm:git:
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git[branch=]maven-3.0.x[path
>> > > =]/maven-core </developerConnection>
>> > >
>> > > with such scm url format, we have the structure we like without POM
>> format
>> > > change, and module value inheritance by adding artifact-id to the
>> url
>> > > stays
>> > > simple and consistent
>> > >
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Chris Graham <ch...@gmail.com>.
On Sun, Sep 1, 2013 at 8:21 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> if I read Jazz SCM url format [1], in a multi-module build, scm info
> automatically calculated from root to modules (ie appending artifact-id)
> will
> give wrong scm info, no?
> did you try it?
>
>
All of my testing was for multi module projects. Nested ones. So it was
never a problem.
There is an ugly work around/hack (that automatically happens) for non-nest
projects. So add a dummy path to the end of the Component name, and it
seems to work out.
As the SCM section is only in the root pom, it does not seem to be effected.
A tag (in maven SCM terms) is the equivalent of a snapshot of a component
(in Jazz SCM terms). Technically, it is a collection of Change Sets, but
effectively works out to be a "tag" for a given component.
So I think of all modules as a part of the same component (just like all
modules under a trank/branch in svn). so it tends to work nicely.
> there are 2 other parts:
> - m-release-p: did you add any logic to deal with plugin scm info
> modification
> when tagging a version?
>
I didn't, but I think that Robert had to add some logic in there that
applied to Jazz (and I think some others as well). I'd have to go back and
look.
> - m-pir-p: when you do a checkout (or clone, or view, I don't know the
> exact
> term for Jazz), IIUC, you get a repository copy: did you write some
> instructions in the generated page to cd to module base directory? (again
> for
> multi-module builds)
>
You're the first to ask about this.
I just quickly run a site build, and the generated URL's in the Source
Repository pages are wrong, as they assume the ability to check out just
one module of a multi module project (eg SVN terms, a svn checkout of
.../trunk/Module). This shows the CVS/SVN embedded thinking that is pretty
much implicit across much of the SCM and Release modules.
I do not believe that it is possible to check out (via the command line, I
think that you _may_ be able to via the GUI) one sub dir (ie Module) of a
Jazz SCM Component.
A checkout in Jazz SCM terms is a "Load". :-)
See:
http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-jazz/index.html
[1] http://maven.apache.org/scm/jazz.html
>
> Le dimanche 1 septembre 2013 09:54:39 Chris Graham a écrit :
> > I did something similar in the Jazz provider. It's a complex URL, or can
> be
> > if it needs to be, but it's still a single line.
> >
> > It's just a matter of making the parser smarted. And that's local to the
> > provider, so go nuts. I also put lots of unit tests in there to
> illustrate
> > the correct and incorrect usage.
> >
> > -Chris
> >
> > On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY <herve.boutemy@free.fr
> >wrote:
> > > Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit :
> > > > I agree that a single SCM line doesn't really match anymore with
> systems
> > > > like DSCM (git, Mercurial)
> > > > It would have been better if we could think of a better way to define
> > >
> > > this
> > >
> > > > in a newer POM-model.
> > >
> > > it was overkill at the time Maven was done, and even today, splitting
> scm
> > > developerConnection into 3 parts seems overkill for classical SCMs,
> even
> > > if
> > > doable
> > >
> > > notice that even with "single SCM line", we can have multiple fields,
> like
> > > we
> > > already have for example with git to distinguish fetch and push urls:
> > > <developerConnection>scm:git:
> > > [fetch=]
> > >
> http://mywebserver.org/path_to_repository[push=]ssh://username@otherserver
> > > :8898/~/repopath.git </developerConnection>
> > >
> > > in the same spirit, we could support a branch and a path parts
> > > <developerConnection>scm:git:
> > >
> https://git-wip-us.apache.org/repos/asf/maven.git[branch=]maven-3.0.x[path
> > > =]/maven-core </developerConnection>
> > >
> > > with such scm url format, we have the structure we like without POM
> format
> > > change, and module value inheritance by adding artifact-id to the url
> > > stays
> > > simple and consistent
> > >
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: What is the correct Git SCM URL for a branch?
Posted by Hervé BOUTEMY <he...@free.fr>.
if I read Jazz SCM url format [1], in a multi-module build, scm info
automatically calculated from root to modules (ie appending artifact-id) will
give wrong scm info, no?
did you try it?
there are 2 other parts:
- m-release-p: did you add any logic to deal with plugin scm info modification
when tagging a version?
- m-pir-p: when you do a checkout (or clone, or view, I don't know the exact
term for Jazz), IIUC, you get a repository copy: did you write some
instructions in the generated page to cd to module base directory? (again for
multi-module builds)
Regards,
Hervé
[1] http://maven.apache.org/scm/jazz.html
Le dimanche 1 septembre 2013 09:54:39 Chris Graham a écrit :
> I did something similar in the Jazz provider. It's a complex URL, or can be
> if it needs to be, but it's still a single line.
>
> It's just a matter of making the parser smarted. And that's local to the
> provider, so go nuts. I also put lots of unit tests in there to illustrate
> the correct and incorrect usage.
>
> -Chris
>
> On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY <he...@free.fr>wrote:
> > Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit :
> > > I agree that a single SCM line doesn't really match anymore with systems
> > > like DSCM (git, Mercurial)
> > > It would have been better if we could think of a better way to define
> >
> > this
> >
> > > in a newer POM-model.
> >
> > it was overkill at the time Maven was done, and even today, splitting scm
> > developerConnection into 3 parts seems overkill for classical SCMs, even
> > if
> > doable
> >
> > notice that even with "single SCM line", we can have multiple fields, like
> > we
> > already have for example with git to distinguish fetch and push urls:
> > <developerConnection>scm:git:
> > [fetch=]
> > http://mywebserver.org/path_to_repository[push=]ssh://username@otherserver
> > :8898/~/repopath.git </developerConnection>
> >
> > in the same spirit, we could support a branch and a path parts
> > <developerConnection>scm:git:
> > https://git-wip-us.apache.org/repos/asf/maven.git[branch=]maven-3.0.x[path
> > =]/maven-core </developerConnection>
> >
> > with such scm url format, we have the structure we like without POM format
> > change, and module value inheritance by adding artifact-id to the url
> > stays
> > simple and consistent
> >
> >
> > Regards,
> >
> > Hervé
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Chris Graham <ch...@gmail.com>.
I did something similar in the Jazz provider. It's a complex URL, or can be
if it needs to be, but it's still a single line.
It's just a matter of making the parser smarted. And that's local to the
provider, so go nuts. I also put lots of unit tests in there to illustrate
the correct and incorrect usage.
-Chris
On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY <he...@free.fr>wrote:
> Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit :
> > I agree that a single SCM line doesn't really match anymore with systems
> > like DSCM (git, Mercurial)
> > It would have been better if we could think of a better way to define
> this
> > in a newer POM-model.
> it was overkill at the time Maven was done, and even today, splitting scm
> developerConnection into 3 parts seems overkill for classical SCMs, even if
> doable
>
> notice that even with "single SCM line", we can have multiple fields, like
> we
> already have for example with git to distinguish fetch and push urls:
> <developerConnection>scm:git:
> [fetch=]
> http://mywebserver.org/path_to_repository[push=]ssh://username@otherserver:8898/~/repopath.git
> </developerConnection>
>
> in the same spirit, we could support a branch and a path parts
> <developerConnection>scm:git:
> https://git-wip-us.apache.org/repos/asf/maven.git[branch=]maven-3.0.x[path=]/maven-core
> </developerConnection>
>
> with such scm url format, we have the structure we like without POM format
> change, and module value inheritance by adding artifact-id to the url stays
> simple and consistent
>
>
> Regards,
>
> Hervé
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: What is the correct Git SCM URL for a branch?
Posted by Hervé BOUTEMY <he...@free.fr>.
Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit :
> I agree that a single SCM line doesn't really match anymore with systems
> like DSCM (git, Mercurial)
> It would have been better if we could think of a better way to define this
> in a newer POM-model.
it was overkill at the time Maven was done, and even today, splitting scm
developerConnection into 3 parts seems overkill for classical SCMs, even if
doable
notice that even with "single SCM line", we can have multiple fields, like we
already have for example with git to distinguish fetch and push urls:
<developerConnection>scm:git:
[fetch=]http://mywebserver.org/path_to_repository[push=]ssh://username@otherserver:8898/~/repopath.git</developerConnection>
in the same spirit, we could support a branch and a path parts
<developerConnection>scm:git:https://git-wip-us.apache.org/repos/asf/maven.git[branch=]maven-3.0.x[path=]/maven-core</developerConnection>
with such scm url format, we have the structure we like without POM format
change, and module value inheritance by adding artifact-id to the url stays
simple and consistent
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Robert Scholte <rf...@apache.org>.
I agree that a single SCM line doesn't really match anymore with systems
like DSCM (git, Mercurial)
It would have been better if we could think of a better way to define this
in a newer POM-model.
In fact, when talking about this (like in the other thread[1]) if we're
going to divide the pom (build-time, dep-time), we might wonder if this
info is still required, because:
- there's some kind of redundancy in it. During build-time it is not
interesting. On the other hand, during packaging it is super interesting:
How nice would it be if the URL, branch/tag (DSCM) or path (non-DSCM) and
revision were added to the pom. This also solves the chicken/egg problem
when talking about including the revision in the pom.xml. During
build-time this is impossible to add this to the pom.xml, but when using
it as a dependency it is great if you had the exact SCM coordinates.
- In all cases you'd like to refer to the trunk/master, since contributers
should check out that part of a repository instead of a tag.
Robert
[1] http://markmail.org/message/af5odr62vxmlpubc
Op Sat, 24 Aug 2013 18:54:06 +0200 schreef Hervé BOUTEMY
<he...@free.fr>:
> Le samedi 24 août 2013 17:12:20 Fred Cooke a écrit :
>> Apologies, however as Herve noted, the web URL is variable across
>> different
>> web implementations so it too should likely be left as is, being a human
>> chosen URL for human use. The previous SVN butchering of such fields
>> doesn't necessarily apply to other systems like HG or Git. My 2c.
> "butchering" = immediate negative judgement, which does not help working
> together
>
> there is no butchering: just a common assumption done in pom inheritence
> that
> scm web view module path would be equal to parent web view path + '/' +
> artifact id
>
> this is true for most commons ways of navigating in a web browser to
> something
> that is like a directory structure
> so whatever SCM you're using, if it provides a web view tool, having
> such a
> simple algorithm should be sufficient to deduce module web view url from
> parent's one: it does not seem crazy to consider web view tool
> developers have
> applied this convention. Then with this simple algorithm, Maven can avoid
> explicit configuration in module pom
>
> I'm here talking about web view
>
> And let's start generalization to other SCM parameters, since this
> extends
> quite naturally now
>
> For SCM connection and developerConnection urls, however, I admit that
> this
> algorithm might be too simplistic, but assumed sufficient since CVS and
> svn
> checkout urls have such properties
> But even there, such assumption is not crazy (going from parent SCM
> location
> to module should be like doing "cd artifact-id") and should be feasible
> if SCM
> format is explicitely defined by convention to behave like this (such
> convention has not yet been defined).
> And since SCM parameter in Maven pom is a Maven SCM component url
> (scm:*),
> which contains a native SCM repository url (in SCM-specific format), but
> is not
> limited to this info, nothing prevents us to extend Maven SCM url to add
> information for SCM types that do not define branch or directory from
> repository root in their native url format (like every DVCS, some
> commercial
> SCMs)
>
> Then Maven SCM API should be changed to improve ScmRepository API:
> actually,
> ScmRepository is told to represent a SCM repository, but in fact, IMHO,
> it
> represents a repository + a branch + a directory
>
> Does it sound reasonable?
>
> Regards,
>
> Hervé
>
>>
>> On Sat, Aug 24, 2013 at 5:08 PM, Baptiste Mathus <ml...@batmat.net> wrote:
>> > See http://maven.apache.org/pom.html#SCM Hervé is talking about
>> > xpath:/SCM/url which is indeed a scm web ui and said
>> (developer)Connection
>> > would be discussed in another thread.
>> >
>> > Cheers
>> >
>> > Le 24 août 2013 16:57, "Fred Cooke" <fr...@gmail.com> a écrit :
>> > > I understood that the purpose of the SCM *URL* was to be able to
>> *use*
>> > > it with a tool (where browser != tool), as such, there is only one
>> > > correct URL, the rest are paths for browsing on a file system or
>> > > web-front end. I did this knowing it would fail to illustrate the
>> > > point:
>> > >
>> > > fred@cheetah:~/workspaces$ git clone
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
>> > > Cloning into 'maven-2.2.x'...
>> >
>> > > fatal:
>> >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x/i
>> > nfo/refs>
>> > > not found: did you run git update-server-info on the server?
>> > >
>> > > On Sat, Aug 24, 2013 at 4:49 PM, Hervé BOUTEMY
>> <he...@free.fr>
>> > >
>> > > wrote:
>> > > > I made some research and tests and here are my findings
>> > > >
>> > > > for the scm url, ie. web access like we have ViewVC url for svn,
>> git
>> > >
>> > > provides
>> > >
>> > > > GitWeb equivalent to ViewVC (even if a lot of other solutions
>> exist
>> >
>> > [1]),
>> >
>> > > > which is what is configured on Apache git http
>> > > > Then the GitWeb url format is in the git documentation [2]
>> > > >
>> > > > With this format, you can refer to branches, tags and revisions,
>> like
>> > > > following examples:
>> > > >
>> > > > branches:
>> > > > HEAD:
>> > > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD
>> > > >
>> > > > maven-3.0.x:
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-3.0.x
>> > >
>> > > > maven-2.2.x:
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
>> > >
>> > > > tags:
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.1.0
>> > >
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.0.5
>> > >
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-2.2.1
>> > >
>> > > > revisions: (same examples as previous tags)
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/5a0e6574404b4964522
>> > d90c3438e25574a95466c
>> >
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/fbdd91ba01387485598
>> > 935fe7d340261239e6a31
>> >
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/238f83f8230b1e0ad32
>> > 39ca7e4f849591331c801>
>> > > > From the GitWeb url format documentation [2], we should be able to
>> > >
>> > > navigate
>> > >
>> > > > into the reporitory directories by ading ":/<path>", but it fails
>> on
>> > >
>> > > Apache
>> > >
>> > > > GitWeb installation:
>> > >
>> https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD:/maven-core
>> > >
>> > > > it works on Git's GitWeb installation
>> > > >
>> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
>> > > >
>> > > > I don't know why Apache GitWeb is failing: previous version? some
>> > > > configuration?
>> > > > I know that even if the feature worked, this wouldn't permit us
>> to let
>> > >
>> > > Maven
>> > >
>> > > > calculate automatically child scm url from parent, since the
>> format
>> > >
>> > > requires
>> > >
>> > > > ':/' to be added for the first directory:
>> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2
>> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
>> > > >
>> > > > For actuel Maven to correctly calculate the second from the
>> first, we
>> > >
>> > > would
>> > >
>> > > > need to write
>> > > >
>> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:
>> > > > or http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/
>> > > > which are both unsupported by GitWeb actually
>> > > >
>> > > > Notice GitHub's url format works like a charm:
>> > > > https://github.com/apache/maven/tree/maven-3.1.0
>> > > > https://github.com/apache/maven/tree/maven-3.1.0/maven-core
>> > > > https://github.com/apache/maven/tree/maven-3.0.x
>> > > > https://github.com/apache/maven/tree/maven-3.0.x/maven-core
>> > > >
>> > > >
>> > > > Should we configure scm url to point to GitHub mirror instead of
>> > > > Apache
>> > > > canonical repo?
>> > > >
>> > > > I still didn't had a look at the way release plugin can transform
>> >
>> > branch
>> >
>> > > url
>> > >
>> > > > to release url during pom.xml modification: I wanted to share
>> these
>> > >
>> > > findings
>> > >
>> > > > first
>> > > >
>> > > > I had some thought about scm connection and developerConnection,
>> but
>> >
>> > it's
>> >
>> > > > another story and this mail is already quite long: we'll see it
>> after
>> >
>> > we
>> >
>> > > > improve web access support.
>> > > >
>> > > > Regards,
>> > > >
>> > > > Hervé
>> > > >
>> > > >
>> > > > [1]
>> >
>> >
>> https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Web_Inte
>> > rfaces>
>> > > > [2] http://git-scm.com/docs/gitweb.html#_actions,_and_urls
>> > > >
>> > > > Le samedi 10 août 2013 13:12:00 Dennis Lundberg a écrit :
>> > > >> 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
>> > >
>> > > </conn
>> > >
>> > > >> ection>
>> > >
>> > > >> <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
>> > >
>> > > </conn
>> > >
>> > > >> ection>
>> > >
>> > > >> <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.
>> > > >
>> > > >
>> ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > > For additional commands, e-mail: dev-help@maven.apache.org
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Hervé BOUTEMY <he...@free.fr>.
Le samedi 24 août 2013 17:12:20 Fred Cooke a écrit :
> Apologies, however as Herve noted, the web URL is variable across different
> web implementations so it too should likely be left as is, being a human
> chosen URL for human use. The previous SVN butchering of such fields
> doesn't necessarily apply to other systems like HG or Git. My 2c.
"butchering" = immediate negative judgement, which does not help working
together
there is no butchering: just a common assumption done in pom inheritence that
scm web view module path would be equal to parent web view path + '/' +
artifact id
this is true for most commons ways of navigating in a web browser to something
that is like a directory structure
so whatever SCM you're using, if it provides a web view tool, having such a
simple algorithm should be sufficient to deduce module web view url from
parent's one: it does not seem crazy to consider web view tool developers have
applied this convention. Then with this simple algorithm, Maven can avoid
explicit configuration in module pom
I'm here talking about web view
And let's start generalization to other SCM parameters, since this extends
quite naturally now
For SCM connection and developerConnection urls, however, I admit that this
algorithm might be too simplistic, but assumed sufficient since CVS and svn
checkout urls have such properties
But even there, such assumption is not crazy (going from parent SCM location
to module should be like doing "cd artifact-id") and should be feasible if SCM
format is explicitely defined by convention to behave like this (such
convention has not yet been defined).
And since SCM parameter in Maven pom is a Maven SCM component url (scm:*),
which contains a native SCM repository url (in SCM-specific format), but is not
limited to this info, nothing prevents us to extend Maven SCM url to add
information for SCM types that do not define branch or directory from
repository root in their native url format (like every DVCS, some commercial
SCMs)
Then Maven SCM API should be changed to improve ScmRepository API: actually,
ScmRepository is told to represent a SCM repository, but in fact, IMHO, it
represents a repository + a branch + a directory
Does it sound reasonable?
Regards,
Hervé
>
> On Sat, Aug 24, 2013 at 5:08 PM, Baptiste Mathus <ml...@batmat.net> wrote:
> > See http://maven.apache.org/pom.html#SCM Hervé is talking about
> > xpath:/SCM/url which is indeed a scm web ui and said (developer)Connection
> > would be discussed in another thread.
> >
> > Cheers
> >
> > Le 24 août 2013 16:57, "Fred Cooke" <fr...@gmail.com> a écrit :
> > > I understood that the purpose of the SCM *URL* was to be able to *use*
> > > it with a tool (where browser != tool), as such, there is only one
> > > correct URL, the rest are paths for browsing on a file system or
> > > web-front end. I did this knowing it would fail to illustrate the
> > > point:
> > >
> > > fred@cheetah:~/workspaces$ git clone
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
> > > Cloning into 'maven-2.2.x'...
> >
> > > fatal:
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x/i
> > nfo/refs>
> > > not found: did you run git update-server-info on the server?
> > >
> > > On Sat, Aug 24, 2013 at 4:49 PM, Hervé BOUTEMY <he...@free.fr>
> > >
> > > wrote:
> > > > I made some research and tests and here are my findings
> > > >
> > > > for the scm url, ie. web access like we have ViewVC url for svn, git
> > >
> > > provides
> > >
> > > > GitWeb equivalent to ViewVC (even if a lot of other solutions exist
> >
> > [1]),
> >
> > > > which is what is configured on Apache git http
> > > > Then the GitWeb url format is in the git documentation [2]
> > > >
> > > > With this format, you can refer to branches, tags and revisions, like
> > > > following examples:
> > > >
> > > > branches:
> > > > HEAD:
> > > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD
> > > >
> > > > maven-3.0.x:
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-3.0.x
> > >
> > > > maven-2.2.x:
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
> > >
> > > > tags:
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.1.0
> > >
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.0.5
> > >
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-2.2.1
> > >
> > > > revisions: (same examples as previous tags)
> >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/5a0e6574404b4964522
> > d90c3438e25574a95466c
> >
> >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/fbdd91ba01387485598
> > 935fe7d340261239e6a31
> >
> >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/238f83f8230b1e0ad32
> > 39ca7e4f849591331c801>
> > > > From the GitWeb url format documentation [2], we should be able to
> > >
> > > navigate
> > >
> > > > into the reporitory directories by ading ":/<path>", but it fails on
> > >
> > > Apache
> > >
> > > > GitWeb installation:
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD:/maven-core
> > >
> > > > it works on Git's GitWeb installation
> > > >
> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
> > > >
> > > > I don't know why Apache GitWeb is failing: previous version? some
> > > > configuration?
> > > > I know that even if the feature worked, this wouldn't permit us to let
> > >
> > > Maven
> > >
> > > > calculate automatically child scm url from parent, since the format
> > >
> > > requires
> > >
> > > > ':/' to be added for the first directory:
> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2
> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
> > > >
> > > > For actuel Maven to correctly calculate the second from the first, we
> > >
> > > would
> > >
> > > > need to write
> > > >
> > > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:
> > > > or http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/
> > > > which are both unsupported by GitWeb actually
> > > >
> > > > Notice GitHub's url format works like a charm:
> > > > https://github.com/apache/maven/tree/maven-3.1.0
> > > > https://github.com/apache/maven/tree/maven-3.1.0/maven-core
> > > > https://github.com/apache/maven/tree/maven-3.0.x
> > > > https://github.com/apache/maven/tree/maven-3.0.x/maven-core
> > > >
> > > >
> > > > Should we configure scm url to point to GitHub mirror instead of
> > > > Apache
> > > > canonical repo?
> > > >
> > > > I still didn't had a look at the way release plugin can transform
> >
> > branch
> >
> > > url
> > >
> > > > to release url during pom.xml modification: I wanted to share these
> > >
> > > findings
> > >
> > > > first
> > > >
> > > > I had some thought about scm connection and developerConnection, but
> >
> > it's
> >
> > > > another story and this mail is already quite long: we'll see it after
> >
> > we
> >
> > > > improve web access support.
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > >
> > > > [1]
> >
> > https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Web_Inte
> > rfaces>
> > > > [2] http://git-scm.com/docs/gitweb.html#_actions,_and_urls
> > > >
> > > > Le samedi 10 août 2013 13:12:00 Dennis Lundberg a écrit :
> > > >> 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
> > >
> > > </conn
> > >
> > > >> ection>
> > >
> > > >> <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
> > >
> > > </conn
> > >
> > > >> ection>
> > >
> > > >> <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.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Fred Cooke <fr...@gmail.com>.
Apologies, however as Herve noted, the web URL is variable across different
web implementations so it too should likely be left as is, being a human
chosen URL for human use. The previous SVN butchering of such fields
doesn't necessarily apply to other systems like HG or Git. My 2c.
On Sat, Aug 24, 2013 at 5:08 PM, Baptiste Mathus <ml...@batmat.net> wrote:
> See http://maven.apache.org/pom.html#SCM Hervé is talking about
> xpath:/SCM/url which is indeed a scm web ui and said (developer)Connection
> would be discussed in another thread.
>
> Cheers
> Le 24 août 2013 16:57, "Fred Cooke" <fr...@gmail.com> a écrit :
>
> > I understood that the purpose of the SCM *URL* was to be able to *use*
> > it with a tool (where browser != tool), as such, there is only one
> > correct URL, the rest are paths for browsing on a file system or
> > web-front end. I did this knowing it would fail to illustrate the
> > point:
> >
> > fred@cheetah:~/workspaces$ git clone
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
> > Cloning into 'maven-2.2.x'...
> > fatal:
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x/info/refs
> > not found: did you run git update-server-info on the server?
> >
> > On Sat, Aug 24, 2013 at 4:49 PM, Hervé BOUTEMY <he...@free.fr>
> > wrote:
> > > I made some research and tests and here are my findings
> > >
> > > for the scm url, ie. web access like we have ViewVC url for svn, git
> > provides
> > > GitWeb equivalent to ViewVC (even if a lot of other solutions exist
> [1]),
> > > which is what is configured on Apache git http
> > > Then the GitWeb url format is in the git documentation [2]
> > >
> > > With this format, you can refer to branches, tags and revisions, like
> > > following examples:
> > >
> > > branches:
> > > HEAD:
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD
> > > maven-3.0.x:
> > >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-3.0.x
> > > maven-2.2.x:
> > >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
> > >
> > > tags:
> > >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.1.0
> > >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.0.5
> > >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-2.2.1
> > >
> > > revisions: (same examples as previous tags)
> > >
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/5a0e6574404b4964522d90c3438e25574a95466c
> > >
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/fbdd91ba01387485598935fe7d340261239e6a31
> > >
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/238f83f8230b1e0ad3239ca7e4f849591331c801
> > >
> > >
> > > From the GitWeb url format documentation [2], we should be able to
> > navigate
> > > into the reporitory directories by ading ":/<path>", but it fails on
> > Apache
> > > GitWeb installation:
> > >
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD:/maven-core
> > > it works on Git's GitWeb installation
> > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
> > >
> > > I don't know why Apache GitWeb is failing: previous version? some
> > > configuration?
> > > I know that even if the feature worked, this wouldn't permit us to let
> > Maven
> > > calculate automatically child scm url from parent, since the format
> > requires
> > > ':/' to be added for the first directory:
> > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2
> > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
> > > For actuel Maven to correctly calculate the second from the first, we
> > would
> > > need to write
> > > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:
> > > or http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/
> > > which are both unsupported by GitWeb actually
> > >
> > > Notice GitHub's url format works like a charm:
> > > https://github.com/apache/maven/tree/maven-3.1.0
> > > https://github.com/apache/maven/tree/maven-3.1.0/maven-core
> > > https://github.com/apache/maven/tree/maven-3.0.x
> > > https://github.com/apache/maven/tree/maven-3.0.x/maven-core
> > >
> > >
> > > Should we configure scm url to point to GitHub mirror instead of Apache
> > > canonical repo?
> > >
> > > I still didn't had a look at the way release plugin can transform
> branch
> > url
> > > to release url during pom.xml modification: I wanted to share these
> > findings
> > > first
> > >
> > > I had some thought about scm connection and developerConnection, but
> it's
> > > another story and this mail is already quite long: we'll see it after
> we
> > > improve web access support.
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > >
> > > [1]
> > >
> >
> https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Web_Interfaces
> > >
> > > [2] http://git-scm.com/docs/gitweb.html#_actions,_and_urls
> > >
> > > Le samedi 10 août 2013 13:12:00 Dennis Lundberg a écrit :
> > >> 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
> > </conn
> > >> ection>
> > >> <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
> > </conn
> > >> ection>
> > >> <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.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: What is the correct Git SCM URL for a branch?
Posted by Baptiste Mathus <ml...@batmat.net>.
See http://maven.apache.org/pom.html#SCM Hervé is talking about
xpath:/SCM/url which is indeed a scm web ui and said (developer)Connection
would be discussed in another thread.
Cheers
Le 24 août 2013 16:57, "Fred Cooke" <fr...@gmail.com> a écrit :
> I understood that the purpose of the SCM *URL* was to be able to *use*
> it with a tool (where browser != tool), as such, there is only one
> correct URL, the rest are paths for browsing on a file system or
> web-front end. I did this knowing it would fail to illustrate the
> point:
>
> fred@cheetah:~/workspaces$ git clone
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
> Cloning into 'maven-2.2.x'...
> fatal:
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x/info/refs
> not found: did you run git update-server-info on the server?
>
> On Sat, Aug 24, 2013 at 4:49 PM, Hervé BOUTEMY <he...@free.fr>
> wrote:
> > I made some research and tests and here are my findings
> >
> > for the scm url, ie. web access like we have ViewVC url for svn, git
> provides
> > GitWeb equivalent to ViewVC (even if a lot of other solutions exist [1]),
> > which is what is configured on Apache git http
> > Then the GitWeb url format is in the git documentation [2]
> >
> > With this format, you can refer to branches, tags and revisions, like
> > following examples:
> >
> > branches:
> > HEAD:
> > https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD
> > maven-3.0.x:
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-3.0.x
> > maven-2.2.x:
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
> >
> > tags:
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.1.0
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.0.5
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-2.2.1
> >
> > revisions: (same examples as previous tags)
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/5a0e6574404b4964522d90c3438e25574a95466c
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/fbdd91ba01387485598935fe7d340261239e6a31
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/238f83f8230b1e0ad3239ca7e4f849591331c801
> >
> >
> > From the GitWeb url format documentation [2], we should be able to
> navigate
> > into the reporitory directories by ading ":/<path>", but it fails on
> Apache
> > GitWeb installation:
> >
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD:/maven-core
> > it works on Git's GitWeb installation
> > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
> >
> > I don't know why Apache GitWeb is failing: previous version? some
> > configuration?
> > I know that even if the feature worked, this wouldn't permit us to let
> Maven
> > calculate automatically child scm url from parent, since the format
> requires
> > ':/' to be added for the first directory:
> > http://repo.or.cz/w/git.git/tree/tags/v1.8.2
> > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
> > For actuel Maven to correctly calculate the second from the first, we
> would
> > need to write
> > http://repo.or.cz/w/git.git/tree/tags/v1.8.2:
> > or http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/
> > which are both unsupported by GitWeb actually
> >
> > Notice GitHub's url format works like a charm:
> > https://github.com/apache/maven/tree/maven-3.1.0
> > https://github.com/apache/maven/tree/maven-3.1.0/maven-core
> > https://github.com/apache/maven/tree/maven-3.0.x
> > https://github.com/apache/maven/tree/maven-3.0.x/maven-core
> >
> >
> > Should we configure scm url to point to GitHub mirror instead of Apache
> > canonical repo?
> >
> > I still didn't had a look at the way release plugin can transform branch
> url
> > to release url during pom.xml modification: I wanted to share these
> findings
> > first
> >
> > I had some thought about scm connection and developerConnection, but it's
> > another story and this mail is already quite long: we'll see it after we
> > improve web access support.
> >
> > Regards,
> >
> > Hervé
> >
> >
> > [1]
> >
> https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Web_Interfaces
> >
> > [2] http://git-scm.com/docs/gitweb.html#_actions,_and_urls
> >
> > Le samedi 10 août 2013 13:12:00 Dennis Lundberg a écrit :
> >> 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
> </conn
> >> ection>
> >> <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
> </conn
> >> ection>
> >> <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.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: What is the correct Git SCM URL for a branch?
Posted by Fred Cooke <fr...@gmail.com>.
I understood that the purpose of the SCM *URL* was to be able to *use*
it with a tool (where browser != tool), as such, there is only one
correct URL, the rest are paths for browsing on a file system or
web-front end. I did this knowing it would fail to illustrate the
point:
fred@cheetah:~/workspaces$ git clone
https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
Cloning into 'maven-2.2.x'...
fatal: https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x/info/refs
not found: did you run git update-server-info on the server?
On Sat, Aug 24, 2013 at 4:49 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> I made some research and tests and here are my findings
>
> for the scm url, ie. web access like we have ViewVC url for svn, git provides
> GitWeb equivalent to ViewVC (even if a lot of other solutions exist [1]),
> which is what is configured on Apache git http
> Then the GitWeb url format is in the git documentation [2]
>
> With this format, you can refer to branches, tags and revisions, like
> following examples:
>
> branches:
> HEAD:
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD
> maven-3.0.x:
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-3.0.x
> maven-2.2.x:
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
>
> tags:
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.1.0
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.0.5
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-2.2.1
>
> revisions: (same examples as previous tags)
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/5a0e6574404b4964522d90c3438e25574a95466c
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/fbdd91ba01387485598935fe7d340261239e6a31
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/238f83f8230b1e0ad3239ca7e4f849591331c801
>
>
> From the GitWeb url format documentation [2], we should be able to navigate
> into the reporitory directories by ading ":/<path>", but it fails on Apache
> GitWeb installation:
> https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD:/maven-core
> it works on Git's GitWeb installation
> http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
>
> I don't know why Apache GitWeb is failing: previous version? some
> configuration?
> I know that even if the feature worked, this wouldn't permit us to let Maven
> calculate automatically child scm url from parent, since the format requires
> ':/' to be added for the first directory:
> http://repo.or.cz/w/git.git/tree/tags/v1.8.2
> http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
> For actuel Maven to correctly calculate the second from the first, we would
> need to write
> http://repo.or.cz/w/git.git/tree/tags/v1.8.2:
> or http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/
> which are both unsupported by GitWeb actually
>
> Notice GitHub's url format works like a charm:
> https://github.com/apache/maven/tree/maven-3.1.0
> https://github.com/apache/maven/tree/maven-3.1.0/maven-core
> https://github.com/apache/maven/tree/maven-3.0.x
> https://github.com/apache/maven/tree/maven-3.0.x/maven-core
>
>
> Should we configure scm url to point to GitHub mirror instead of Apache
> canonical repo?
>
> I still didn't had a look at the way release plugin can transform branch url
> to release url during pom.xml modification: I wanted to share these findings
> first
>
> I had some thought about scm connection and developerConnection, but it's
> another story and this mail is already quite long: we'll see it after we
> improve web access support.
>
> Regards,
>
> Hervé
>
>
> [1]
> https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Web_Interfaces
>
> [2] http://git-scm.com/docs/gitweb.html#_actions,_and_urls
>
> Le samedi 10 août 2013 13:12:00 Dennis Lundberg a écrit :
>> 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</conn
>> ection>
>> <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</conn
>> ection>
>> <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.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Hervé BOUTEMY <he...@free.fr>.
I made some research and tests and here are my findings
for the scm url, ie. web access like we have ViewVC url for svn, git provides
GitWeb equivalent to ViewVC (even if a lot of other solutions exist [1]),
which is what is configured on Apache git http
Then the GitWeb url format is in the git documentation [2]
With this format, you can refer to branches, tags and revisions, like
following examples:
branches:
HEAD:
https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD
maven-3.0.x:
https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-3.0.x
maven-2.2.x:
https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
tags:
https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.1.0
https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-3.0.5
https://git-wip-us.apache.org/repos/asf/maven.git/tree/tags/maven-2.2.1
revisions: (same examples as previous tags)
https://git-wip-us.apache.org/repos/asf/maven.git/tree/5a0e6574404b4964522d90c3438e25574a95466c
https://git-wip-us.apache.org/repos/asf/maven.git/tree/fbdd91ba01387485598935fe7d340261239e6a31
https://git-wip-us.apache.org/repos/asf/maven.git/tree/238f83f8230b1e0ad3239ca7e4f849591331c801
>From the GitWeb url format documentation [2], we should be able to navigate
into the reporitory directories by ading ":/<path>", but it fails on Apache
GitWeb installation:
https://git-wip-us.apache.org/repos/asf/maven.git/tree/HEAD:/maven-core
it works on Git's GitWeb installation
http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
I don't know why Apache GitWeb is failing: previous version? some
configuration?
I know that even if the feature worked, this wouldn't permit us to let Maven
calculate automatically child scm url from parent, since the format requires
':/' to be added for the first directory:
http://repo.or.cz/w/git.git/tree/tags/v1.8.2
http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/gitweb
For actuel Maven to correctly calculate the second from the first, we would
need to write
http://repo.or.cz/w/git.git/tree/tags/v1.8.2:
or http://repo.or.cz/w/git.git/tree/tags/v1.8.2:/
which are both unsupported by GitWeb actually
Notice GitHub's url format works like a charm:
https://github.com/apache/maven/tree/maven-3.1.0
https://github.com/apache/maven/tree/maven-3.1.0/maven-core
https://github.com/apache/maven/tree/maven-3.0.x
https://github.com/apache/maven/tree/maven-3.0.x/maven-core
Should we configure scm url to point to GitHub mirror instead of Apache
canonical repo?
I still didn't had a look at the way release plugin can transform branch url
to release url during pom.xml modification: I wanted to share these findings
first
I had some thought about scm connection and developerConnection, but it's
another story and this mail is already quite long: we'll see it after we
improve web access support.
Regards,
Hervé
[1]
https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Web_Interfaces
[2] http://git-scm.com/docs/gitweb.html#_actions,_and_urls
Le samedi 10 août 2013 13:12:00 Dennis Lundberg a écrit :
> 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</conn
> ection>
> <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</conn
> ection>
> <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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Arnaud Héritier <ah...@gmail.com>.
You give me a doubt ;) I think there were 2 features :
* the one to download sources of deps to browse the code
* another one to materialize in your workspace a project/dep (it was a
checkout of it) to allow for example to patch it.
---------
Arnaud
Le 10 août 2013 à 21:24, Fred Cooke <fr...@gmail.com> a écrit :
> Are you sure it's not using the src package uploaded in parallel with the
> binary jar? This was my understanding. Doing it from SCM would be a mine
> field at best. I know it gets javadocs this way, assumed source was the
> same.
>
> On Sat, Aug 10, 2013 at 9:20 PM, Arnaud Héritier <ah...@gmail.com>wrote:
>
>> 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 <st...@yahoo.de> 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 <fr...@gmail.com>
>>>> To: Maven Developers List <de...@maven.apache.org>
>>>> 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 <ol...@apache.org> wrote:
>>>>
>>>>> On 10 August 2013 23:06, Fred Cooke <fr...@gmail.com> 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 <ol...@apache.org>
>>>> wrote:
>>>>>>
>>>>>>> On 10 August 2013 21:12, Dennis Lundberg
>>>> <de...@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-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Olivier Lamy
>>>>>>> Ecetera: http://ecetera.com.au
>>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> Ecetera: http://ecetera.com.au
>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Fred Cooke <fr...@gmail.com>.
Are you sure it's not using the src package uploaded in parallel with the
binary jar? This was my understanding. Doing it from SCM would be a mine
field at best. I know it gets javadocs this way, assumed source was the
same.
On Sat, Aug 10, 2013 at 9:20 PM, Arnaud Héritier <ah...@gmail.com>wrote:
> 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 <st...@yahoo.de> 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 <fr...@gmail.com>
> >> To: Maven Developers List <de...@maven.apache.org>
> >> 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 <ol...@apache.org> wrote:
> >>
> >>> On 10 August 2013 23:06, Fred Cooke <fr...@gmail.com> 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 <ol...@apache.org>
> >> wrote:
> >>>>
> >>>>> On 10 August 2013 21:12, Dennis Lundberg
> >> <de...@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-unsubscribe@maven.apache.org
> >>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Olivier Lamy
> >>>>> Ecetera: http://ecetera.com.au
> >>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> >>>
> >>> --
> >>> Olivier Lamy
> >>> Ecetera: http://ecetera.com.au
> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: What is the correct Git SCM URL for a branch?
Posted by Arnaud Héritier <ah...@gmail.com>.
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 <st...@yahoo.de> 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 <fr...@gmail.com>
>> To: Maven Developers List <de...@maven.apache.org>
>> 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 <ol...@apache.org> wrote:
>>
>>> On 10 August 2013 23:06, Fred Cooke <fr...@gmail.com> 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 <ol...@apache.org>
>> wrote:
>>>>
>>>>> On 10 August 2013 21:12, Dennis Lundberg
>> <de...@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-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> Ecetera: http://ecetera.com.au
>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Ecetera: http://ecetera.com.au
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Mark Struberg <st...@yahoo.de>.
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 <fr...@gmail.com>
> To: Maven Developers List <de...@maven.apache.org>
> 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 <ol...@apache.org> wrote:
>
>> On 10 August 2013 23:06, Fred Cooke <fr...@gmail.com> 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 <ol...@apache.org>
> wrote:
>> >
>> >> On 10 August 2013 21:12, Dennis Lundberg
> <de...@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-unsubscribe@maven.apache.org
>> >> > For additional commands, e-mail: dev-help@maven.apache.org
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Olivier Lamy
>> >> Ecetera: http://ecetera.com.au
>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>
>> >>
> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: dev-help@maven.apache.org
>> >>
>> >>
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Fred Cooke <fr...@gmail.com>.
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 <ol...@apache.org> wrote:
> On 10 August 2013 23:06, Fred Cooke <fr...@gmail.com> 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 <ol...@apache.org> wrote:
> >
> >> On 10 August 2013 21:12, Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: dev-help@maven.apache.org
> >> >
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Ecetera: http://ecetera.com.au
> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: What is the correct Git SCM URL for a branch?
Posted by Olivier Lamy <ol...@apache.org>.
On 10 August 2013 23:06, Fred Cooke <fr...@gmail.com> 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 <ol...@apache.org> wrote:
>
>> On 10 August 2013 21:12, Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Fred Cooke <fr...@gmail.com>.
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. 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 <ol...@apache.org> wrote:
> On 10 August 2013 21:12, Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: What is the correct Git SCM URL for a branch?
Posted by Dennis Lundberg <de...@apache.org>.
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 <de...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: What is the correct Git SCM URL for a branch?
Posted by Olivier Lamy <ol...@apache.org>.
On 10 August 2013 21:12, Dennis Lundberg <de...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org