You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/05/07 17:35:00 UTC
[jira] [Updated] (MRELEASE-1089) Reduce the tag format to the project version only
[ https://issues.apache.org/jira/browse/MRELEASE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MRELEASE-1089:
-------------------------------------
Description:
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 trunk/branches/tags for all component groups instead of the common sense to have one dir per project with 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 could only 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.
was:
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 trunk/branches/tags for all component groups instead of the common sense to have one dir per project with 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 could only 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.
> Reduce the 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
> Fix For: 3.0.0-M6
>
>
> 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 trunk/branches/tags for all component groups instead of the common sense to have one dir per project with 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 could only 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)