[ 
https://issues.apache.org/jira/browse/MRELEASE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MRELEASE-1089:
-------------------------------------
    Fix Version/s:     (was: 3.0.0-M6)

> Reduce the default tag format to the project version only
> ---------------------------------------------------------
>
>                 Key: MRELEASE-1089
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-1089
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: scm
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>
> Back in the days when this plugin was written and all ASF Maven-based 
> projects used the ASF Subversion repo, the common practice was to have one 
> trunk/branches/tags for all component groups instead of the common sense to 
> have one dir per project with distinct trunk/branches/tags. This resulted 
> that the ASF diverged from the common practice and basically imposed 
> {{{{}project.artifactId}-{project.version{}}}} tag format to the entire Java 
> world. With the emerge of Git one can have one project per repo where this 
> approach was pointless anyway.
> Proposal: since this is an overhauled practice, it is neither fruitful for 
> Subversion, Git or Mercurial and a prefix which is appended to every tag is 
> redudant, replace this format with the version only like many others do now.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to