You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Julian Wood (JIRA)" <ji...@codehaus.org> on 2006/02/04 01:17:12 UTC
[jira] Created: (MNG-2038) A mini guide covering the interplay
between SCM and maven releases
A mini guide covering the interplay between SCM and maven releases
------------------------------------------------------------------
Key: MNG-2038
URL: http://jira.codehaus.org/browse/MNG-2038
Project: Maven 2
Type: Improvement
Components: Documentation: Guides
Reporter: Julian Wood
Priority: Minor
Attachments: project_process.apt
Emmanuel Venisse asked if I would contribute this document, so here it is. It is a step by step guide which covers releasing a project using maven, but also demonstrates some best practices when it comes to making branches, tags, and of course versions, all while touching on how maven makes these practices so much less of a headache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-2038) A mini guide covering the interplay
between SCM and maven releases
Posted by "Julian Wood (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2038?page=comments#action_57808 ]
Julian Wood commented on MNG-2038:
----------------------------------
Note that there are 2 bugs in the APT processor which make this document less useful, but I imagine will be fixed soon. One is to do with local anchors (DOXIA-47), and the other is the inability to order lists using anything other than 1,2,3 (DOXIA-48).
> A mini guide covering the interplay between SCM and maven releases
> ------------------------------------------------------------------
>
> Key: MNG-2038
> URL: http://jira.codehaus.org/browse/MNG-2038
> Project: Maven 2
> Type: Improvement
> Components: Documentation: Guides
> Reporter: Julian Wood
> Priority: Minor
> Attachments: project_process.apt
>
>
> Emmanuel Venisse asked if I would contribute this document, so here it is. It is a step by step guide which covers releasing a project using maven, but also demonstrates some best practices when it comes to making branches, tags, and of course versions, all while touching on how maven makes these practices so much less of a headache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-2038) A mini guide covering the interplay
between SCM and maven releases
Posted by "Julian Wood (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2038?page=comments#action_57809 ]
Julian Wood commented on MNG-2038:
----------------------------------
I've also noticed that it is written as if it were outside the maven website (ie there are external links to download maven, for example), and there is even a link to another document I've written on subversion. I'm not sure if this needs to be reworked.
> A mini guide covering the interplay between SCM and maven releases
> ------------------------------------------------------------------
>
> Key: MNG-2038
> URL: http://jira.codehaus.org/browse/MNG-2038
> Project: Maven 2
> Type: Improvement
> Components: Documentation: Guides
> Reporter: Julian Wood
> Priority: Minor
> Attachments: project_process.apt
>
>
> Emmanuel Venisse asked if I would contribute this document, so here it is. It is a step by step guide which covers releasing a project using maven, but also demonstrates some best practices when it comes to making branches, tags, and of course versions, all while touching on how maven makes these practices so much less of a headache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org