You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2005/05/23 03:51:33 UTC
adding to
Ref: http://jira.codehaus.org/browse/MNG-223
I would like to add <tag/> to the scmManagement section to facilitate
this. It's default if omitted would be HEAD, and would be used to
specify the CVS branch name during development. At release time, it
would be rewritten with the CVS tag used to release it.
For other SCMs, HEAD and the meaning of the tag balue would equate to
the equivalent for that SCM.
For Subversion, tag would be ignored, and instead the connection string
rewritten at release time.
This means that the deployed POM in the repository has the SCM URL + tag
required to get that version of the code from SCM. In conjunction with a
repo search for all versions for a given group/artifactId this
completely replaces <versions/> from M1.
Thoughts?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: adding to
Posted by Jason van Zyl <ja...@maven.org>.
On Mon, 2005-05-23 at 11:51 +1000, Brett Porter wrote:
> Ref: http://jira.codehaus.org/browse/MNG-223
>
> I would like to add <tag/> to the scmManagement section to facilitate
> this. It's default if omitted would be HEAD, and would be used to
> specify the CVS branch name during development. At release time, it
> would be rewritten with the CVS tag used to release it.
>
> For other SCMs, HEAD and the meaning of the tag balue would equate to
> the equivalent for that SCM.
>
> For Subversion, tag would be ignored, and instead the connection string
> rewritten at release time.
>
> This means that the deployed POM in the repository has the SCM URL + tag
> required to get that version of the code from SCM. In conjunction with a
> repo search for all versions for a given group/artifactId this
> completely replaces <versions/> from M1.
>
> Thoughts?
+1
Definitely required for reproducibility but lets do a quick survey of
the SCMs and make sure the notion of a tag works in all cases. In all
probability it does but I'm only familiar with CVS and SVN.
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: adding to
Posted by Eric Pugh <ep...@upstate.com>.
Seems good.. I guess pretty much all SCM systems have the concept of
a tag.. And not having to manage the <versions/> section would be
nice!
+1
Eric
On May 22, 2005, at 9:51 PM, Brett Porter wrote:
> Ref: http://jira.codehaus.org/browse/MNG-223
>
> I would like to add <tag/> to the scmManagement section to facilitate
> this. It's default if omitted would be HEAD, and would be used to
> specify the CVS branch name during development. At release time, it
> would be rewritten with the CVS tag used to release it.
>
> For other SCMs, HEAD and the meaning of the tag balue would equate to
> the equivalent for that SCM.
>
> For Subversion, tag would be ignored, and instead the connection string
> rewritten at release time.
>
> This means that the deployed POM in the repository has the SCM URL +
> tag
> required to get that version of the code from SCM. In conjunction with
> a
> repo search for all versions for a given group/artifactId this
> completely replaces <versions/> from M1.
>
> Thoughts?
>
> - Brett
>
> ---------------------------------------------------------------------
> 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: adding to
Posted by Emmanuel Venisse <em...@venisse.net>.
+1
Emmanuel
Brett Porter wrote:
> Ref: http://jira.codehaus.org/browse/MNG-223
>
> I would like to add <tag/> to the scmManagement section to facilitate
> this. It's default if omitted would be HEAD, and would be used to
> specify the CVS branch name during development. At release time, it
> would be rewritten with the CVS tag used to release it.
>
> For other SCMs, HEAD and the meaning of the tag balue would equate to
> the equivalent for that SCM.
>
> For Subversion, tag would be ignored, and instead the connection string
> rewritten at release time.
>
> This means that the deployed POM in the repository has the SCM URL + tag
> required to get that version of the code from SCM. In conjunction with a
> repo search for all versions for a given group/artifactId this
> completely replaces <versions/> from M1.
>
> Thoughts?
>
> - Brett
>
> ---------------------------------------------------------------------
> 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: adding to
Posted by Eric Pugh <ep...@opensourceconnections.com>.
Seems good.. I guess pretty much all SCM systems have the concept of
a tag.. And not having to manage the <versions/> section would be
nice!
+1
Eric
On May 22, 2005, at 9:51 PM, Brett Porter wrote:
> Ref: http://jira.codehaus.org/browse/MNG-223
>
> I would like to add <tag/> to the scmManagement section to facilitate
> this. It's default if omitted would be HEAD, and would be used to
> specify the CVS branch name during development. At release time, it
> would be rewritten with the CVS tag used to release it.
>
> For other SCMs, HEAD and the meaning of the tag balue would equate to
> the equivalent for that SCM.
>
> For Subversion, tag would be ignored, and instead the connection string
> rewritten at release time.
>
> This means that the deployed POM in the repository has the SCM URL +
> tag
> required to get that version of the code from SCM. In conjunction with
> a
> repo search for all versions for a given group/artifactId this
> completely replaces <versions/> from M1.
>
> Thoughts?
>
> - Brett
>
> ---------------------------------------------------------------------
> 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