Michael Osipov opened MRELEASE-1089 and commented
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.
Remote Links:
Michael Osipov opened MRELEASE-1089 and commented
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.
Remote Links: