[ http://jira.codehaus.org/browse/MNG-223?page=comments#action_39703 ] Emmanuel Venisse commented on MNG-223: --------------------------------------
<tag/> is add to scm section. The default value is HEAD for all scm provider, we need perhaps a getDefaultTagName() method in maven-scm for obtain the correct default value (HEAD, trunk,...) <tag/> is rewrite by the release plugin with the tag provides by user I need now to rewrite scm url. > consider replacement for <versions/> > ------------------------------------ > > Key: MNG-223 > URL: http://jira.codehaus.org/browse/MNG-223 > Project: Maven 2 > Type: Task > Components: design > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Fix For: 2.0-alpha-3 > > > We removed <versions/> from the POM in m2, which made sense as the POM should > be a snapshot of the current state of the project, not the history. > We can easily get old versions from the repository, however SCM tag names are > missing (so these may need to be stored in the POM at release time). > Another concern is that all project data should be available from the SCM - > so if the repository goes away it can be easily recreated. Would we need to > manually redeploy from every historical tag? Just the versions desired? Would > having another archive versions.xml in SCM help with any of the tasks? > I'm in favour of just using the repository + adding the tag at release time, > but we need to give all use cases due consideration. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
