You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2006/11/02 17:02:47 UTC
[jira] Updated: (MNG-2038) A mini guide covering the interplay
between SCM and maven releases
[ http://jira.codehaus.org/browse/MNG-2038?page=all ]
Kenney Westerhof updated MNG-2038:
----------------------------------
Fix Version/s: (was: 2.0.5)
2.0.6
> 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
> Issue Type: Improvement
> Components: Documentation: Guides
> Reporter: Julian Wood
> Priority: Minor
> Fix For: 2.0.6
>
> 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