You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by vm...@apache.org on 2004/07/08 17:50:06 UTC
cvs commit: maven-plugins/changes project.xml
vmassol 2004/07/08 08:50:06
Modified: changes project.xml
Log:
manually remove the HEAD <version> tag that was not removed by the scm plugin (see http://jira.codehaus.org/browse/MPSCM-17)
Revision Changes Path
1.33 +0 -5 maven-plugins/changes/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/maven-plugins/changes/project.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- project.xml 8 Jul 2004 15:49:03 -0000 1.32
+++ project.xml 8 Jul 2004 15:50:06 -0000 1.33
@@ -47,11 +47,6 @@
<version>
<id>1.5</id>
<name>1.5</name>
- <tag>HEAD</tag>
- </version>
- <version>
- <id>1.5</id>
- <name>1.5</name>
<tag>MAVEN_CHANGES_1_5</tag>
</version>
</versions>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: cvs commit: maven-plugins/changes project.xml
Posted by Dion Gillard <di...@gmail.com>.
If the assumption is the currentVersion is always HEAD, how does that
affect branches?
On Fri, 9 Jul 2004 13:45:19 +0200, Vincent Massol <vm...@pivolis.com> wrote:
>
>
> > -----Original Message-----
> > From: Dion Gillard [mailto:dion.gillard@gmail.com]
> > Sent: vendredi 9 juillet 2004 13:32
> > To: Maven Developers List
> > Subject: Re: cvs commit: maven-plugins/changes project.xml
> >
> > What about branches?
>
> What about them? :-)
>
> -Vincent
>
>
>
> >
> > On Fri, 9 Jul 2004 11:15:36 +0200, Vincent Massol <vm...@pivolis.com>
> > wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: Brett Porter [mailto:brett@apache.org]
> > > > Sent: vendredi 9 juillet 2004 01:33
> > > > To: Maven Developers List
> > > > Subject: Re: cvs commit: maven-plugins/changes project.xml
> > > >
> > > > I don't see any reason to add the HEAD tag in the first place. What is
> > the
> > > > use
> > > > case for it?
> > >
> > > You're probably right (I can't find a good use case from the top of my
> > > head). As we've been doing it since day one, I've kept doing it. For me
> > it
> > > was about listing all the versions, thus including the current. I guess
> > any
> > > plugin who acts on this information could also add the currentVersion
> > > information should it wishes to.
> > >
> > > Thus I'm fine to <versions> as *released* versions only. We just need to
> > say
> > > it I guess...
> > >
> > > >
> > > > prepare-release adds to the end, or overwrites an identical tag. It
> > should
> > > > probably also overwrite an identical version ID.
> > >
> > > That would cater for all use cases.
> > >
> > > -Vincent
> > >
> > >
> > >
> > > >
> > > > - Brett
> > > >
> > > > Quoting vmassol@apache.org:
> > > >
> > > > > vmassol 2004/07/08 08:50:06
> > > > >
> > > > > Modified: changes project.xml
> > > > > Log:
> > > > > manually remove the HEAD <version> tag that was not removed by the
> > scm
> > > > > plugin (see http://jira.codehaus.org/browse/MPSCM-17)
> > > > >
> > > > > Revision Changes Path
> > > > > 1.33 +0 -5 maven-plugins/changes/project.xml
> > > > >
> > > > > Index: project.xml
> > > > >
> > ===================================================================
> > > > > RCS file: /home/cvs/maven-plugins/changes/project.xml,v
> > > > > retrieving revision 1.32
> > > > > retrieving revision 1.33
> > > > > diff -u -r1.32 -r1.33
> > > > > --- project.xml 8 Jul 2004 15:49:03 -0000 1.32
> > > > > +++ project.xml 8 Jul 2004 15:50:06 -0000 1.33
> > > > > @@ -47,11 +47,6 @@
> > > > > <version>
> > > > > <id>1.5</id>
> > > > > <name>1.5</name>
> > > > > - <tag>HEAD</tag>
> > > > > - </version>
> > > > > - <version>
> > > > > - <id>1.5</id>
> > > > > - <name>1.5</name>
> > > > > <tag>MAVEN_CHANGES_1_5</tag>
> > > > > </version>
> > > > > </versions>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --------------------------------------------------------------------
> > -
> > > > > 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
> > >
> > >
> >
> >
> > --
> > http://www.multitask.com.au/people/dion/
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: cvs commit: maven-plugins/changes project.xml
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Dion Gillard [mailto:dion.gillard@gmail.com]
> Sent: vendredi 9 juillet 2004 13:32
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/changes project.xml
>
> What about branches?
What about them? :-)
-Vincent
>
> On Fri, 9 Jul 2004 11:15:36 +0200, Vincent Massol <vm...@pivolis.com>
> wrote:
> >
> >
> > > -----Original Message-----
> > > From: Brett Porter [mailto:brett@apache.org]
> > > Sent: vendredi 9 juillet 2004 01:33
> > > To: Maven Developers List
> > > Subject: Re: cvs commit: maven-plugins/changes project.xml
> > >
> > > I don't see any reason to add the HEAD tag in the first place. What is
> the
> > > use
> > > case for it?
> >
> > You're probably right (I can't find a good use case from the top of my
> > head). As we've been doing it since day one, I've kept doing it. For me
> it
> > was about listing all the versions, thus including the current. I guess
> any
> > plugin who acts on this information could also add the currentVersion
> > information should it wishes to.
> >
> > Thus I'm fine to <versions> as *released* versions only. We just need to
> say
> > it I guess...
> >
> > >
> > > prepare-release adds to the end, or overwrites an identical tag. It
> should
> > > probably also overwrite an identical version ID.
> >
> > That would cater for all use cases.
> >
> > -Vincent
> >
> >
> >
> > >
> > > - Brett
> > >
> > > Quoting vmassol@apache.org:
> > >
> > > > vmassol 2004/07/08 08:50:06
> > > >
> > > > Modified: changes project.xml
> > > > Log:
> > > > manually remove the HEAD <version> tag that was not removed by the
> scm
> > > > plugin (see http://jira.codehaus.org/browse/MPSCM-17)
> > > >
> > > > Revision Changes Path
> > > > 1.33 +0 -5 maven-plugins/changes/project.xml
> > > >
> > > > Index: project.xml
> > > >
> ===================================================================
> > > > RCS file: /home/cvs/maven-plugins/changes/project.xml,v
> > > > retrieving revision 1.32
> > > > retrieving revision 1.33
> > > > diff -u -r1.32 -r1.33
> > > > --- project.xml 8 Jul 2004 15:49:03 -0000 1.32
> > > > +++ project.xml 8 Jul 2004 15:50:06 -0000 1.33
> > > > @@ -47,11 +47,6 @@
> > > > <version>
> > > > <id>1.5</id>
> > > > <name>1.5</name>
> > > > - <tag>HEAD</tag>
> > > > - </version>
> > > > - <version>
> > > > - <id>1.5</id>
> > > > - <name>1.5</name>
> > > > <tag>MAVEN_CHANGES_1_5</tag>
> > > > </version>
> > > > </versions>
> > > >
> > > >
> > > >
> > > >
> > > > --------------------------------------------------------------------
> -
> > > > 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
> >
> >
>
>
> --
> http://www.multitask.com.au/people/dion/
>
> ---------------------------------------------------------------------
> 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: cvs commit: maven-plugins/changes project.xml
Posted by Dion Gillard <di...@gmail.com>.
What about branches?
On Fri, 9 Jul 2004 11:15:36 +0200, Vincent Massol <vm...@pivolis.com> wrote:
>
>
> > -----Original Message-----
> > From: Brett Porter [mailto:brett@apache.org]
> > Sent: vendredi 9 juillet 2004 01:33
> > To: Maven Developers List
> > Subject: Re: cvs commit: maven-plugins/changes project.xml
> >
> > I don't see any reason to add the HEAD tag in the first place. What is the
> > use
> > case for it?
>
> You're probably right (I can't find a good use case from the top of my
> head). As we've been doing it since day one, I've kept doing it. For me it
> was about listing all the versions, thus including the current. I guess any
> plugin who acts on this information could also add the currentVersion
> information should it wishes to.
>
> Thus I'm fine to <versions> as *released* versions only. We just need to say
> it I guess...
>
> >
> > prepare-release adds to the end, or overwrites an identical tag. It should
> > probably also overwrite an identical version ID.
>
> That would cater for all use cases.
>
> -Vincent
>
>
>
> >
> > - Brett
> >
> > Quoting vmassol@apache.org:
> >
> > > vmassol 2004/07/08 08:50:06
> > >
> > > Modified: changes project.xml
> > > Log:
> > > manually remove the HEAD <version> tag that was not removed by the scm
> > > plugin (see http://jira.codehaus.org/browse/MPSCM-17)
> > >
> > > Revision Changes Path
> > > 1.33 +0 -5 maven-plugins/changes/project.xml
> > >
> > > Index: project.xml
> > > ===================================================================
> > > RCS file: /home/cvs/maven-plugins/changes/project.xml,v
> > > retrieving revision 1.32
> > > retrieving revision 1.33
> > > diff -u -r1.32 -r1.33
> > > --- project.xml 8 Jul 2004 15:49:03 -0000 1.32
> > > +++ project.xml 8 Jul 2004 15:50:06 -0000 1.33
> > > @@ -47,11 +47,6 @@
> > > <version>
> > > <id>1.5</id>
> > > <name>1.5</name>
> > > - <tag>HEAD</tag>
> > > - </version>
> > > - <version>
> > > - <id>1.5</id>
> > > - <name>1.5</name>
> > > <tag>MAVEN_CHANGES_1_5</tag>
> > > </version>
> > > </versions>
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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
>
>
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: cvs commit: maven-plugins/changes project.xml
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: vendredi 9 juillet 2004 01:33
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/changes project.xml
>
> I don't see any reason to add the HEAD tag in the first place. What is the
> use
> case for it?
You're probably right (I can't find a good use case from the top of my
head). As we've been doing it since day one, I've kept doing it. For me it
was about listing all the versions, thus including the current. I guess any
plugin who acts on this information could also add the currentVersion
information should it wishes to.
Thus I'm fine to <versions> as *released* versions only. We just need to say
it I guess...
>
> prepare-release adds to the end, or overwrites an identical tag. It should
> probably also overwrite an identical version ID.
That would cater for all use cases.
-Vincent
>
> - Brett
>
> Quoting vmassol@apache.org:
>
> > vmassol 2004/07/08 08:50:06
> >
> > Modified: changes project.xml
> > Log:
> > manually remove the HEAD <version> tag that was not removed by the scm
> > plugin (see http://jira.codehaus.org/browse/MPSCM-17)
> >
> > Revision Changes Path
> > 1.33 +0 -5 maven-plugins/changes/project.xml
> >
> > Index: project.xml
> > ===================================================================
> > RCS file: /home/cvs/maven-plugins/changes/project.xml,v
> > retrieving revision 1.32
> > retrieving revision 1.33
> > diff -u -r1.32 -r1.33
> > --- project.xml 8 Jul 2004 15:49:03 -0000 1.32
> > +++ project.xml 8 Jul 2004 15:50:06 -0000 1.33
> > @@ -47,11 +47,6 @@
> > <version>
> > <id>1.5</id>
> > <name>1.5</name>
> > - <tag>HEAD</tag>
> > - </version>
> > - <version>
> > - <id>1.5</id>
> > - <name>1.5</name>
> > <tag>MAVEN_CHANGES_1_5</tag>
> > </version>
> > </versions>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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: cvs commit: maven-plugins/changes project.xml
Posted by Brett Porter <br...@apache.org>.
I don't see any reason to add the HEAD tag in the first place. What is the use
case for it?
prepare-release adds to the end, or overwrites an identical tag. It should
probably also overwrite an identical version ID.
- Brett
Quoting vmassol@apache.org:
> vmassol 2004/07/08 08:50:06
>
> Modified: changes project.xml
> Log:
> manually remove the HEAD <version> tag that was not removed by the scm
> plugin (see http://jira.codehaus.org/browse/MPSCM-17)
>
> Revision Changes Path
> 1.33 +0 -5 maven-plugins/changes/project.xml
>
> Index: project.xml
> ===================================================================
> RCS file: /home/cvs/maven-plugins/changes/project.xml,v
> retrieving revision 1.32
> retrieving revision 1.33
> diff -u -r1.32 -r1.33
> --- project.xml 8 Jul 2004 15:49:03 -0000 1.32
> +++ project.xml 8 Jul 2004 15:50:06 -0000 1.33
> @@ -47,11 +47,6 @@
> <version>
> <id>1.5</id>
> <name>1.5</name>
> - <tag>HEAD</tag>
> - </version>
> - <version>
> - <id>1.5</id>
> - <name>1.5</name>
> <tag>MAVEN_CHANGES_1_5</tag>
> </version>
> </versions>
>
>
>
>
> ---------------------------------------------------------------------
> 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