-
Suggestion
-
Resolution: Fixed
-
None
We are currently working on renaming Maven Clover2 Plugin according to the naming convention recommended by the Apache Maven project.
Due to a fact that this is a major breaking change, forcing customers to modify their POMs, CI build plans etc, it will be done in the nearest major Clover release (currently planned for end of 2015) and appropriate migration guides will be prepared.
New plugin name will be: clover-maven-plugin
Problem reported:
According the Maven's Plugin Naming Convention, Clover's plugin artifactID violates the Apache Maven Trademark. The artifactId should be clover2-maven-plugin. I would even suggest removing the 2 from the artifactId.
Plugin Naming Convention and Apache Maven Trademark
Scope of the change:
Before release
investigate if we can use clover-maven-plugin or must use cloverX-maven-plugin - will be renamed to clover-maven-plugin
decide if major Clover release will be numbered 4.1.0
or 5.0.0 (as per Semantic Versioning)
prepare migration message in maven-clover2-plugin pom.xml for versions 4.0.x, similarly as it was done for Clover Core (com.cenqua.clover:clover:3.3.0) - message added in pom in 4.0.6
rename maven-clover2-plugin artifactId for 4.1.0 /
5.0.0 , update integration tests
prepare migration guide for Clover 4.1 /
5.0 Release Notes
update Clover's Tutorial (Moneybags bundled in clover-ant.zip) -> see also
CLOV-1827
After release
See CLOV-1828.
[CLOV-1775] Rename maven-clover2-plugin artifactId to clover-maven-plugin
Workflow | Original: JAC Suggestion Workflow [ 3341987 ] | New: JAC Suggestion Workflow 3 [ 3584541 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: New Clover Workflow [ 918278 ] | New: JAC Suggestion Workflow [ 3341987 ] |
Assignee | Original: Marek Parfianowicz [ mparfianowicz ] | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Remote Link | Original: This issue links to "Page (Extranet)" [ 113493 ] |
Comment | [ A comment with security level 'jira-users' was removed. ] |
Comment | [ A comment with security level 'jira-users' was removed. ] |
Comment | [ A comment with security level 'jira-users' was removed. ] |
Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 144345 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To be reviewed [ 10026 ] | New: Closed [ 6 ] |
Worklog Id | Original: 136890 [ 136890 ] | |
Time Spent | New: 10m [ 600 ] |
Description |
Original:
{panel:title=Decision|titleBGColor=#205081|bgColor=#59afe1}
We are currently working on renaming Maven Clover2 Plugin according to the naming convention recommended by the Apache Maven project. Due to a fact that this is a major breaking change, forcing customers to modify their POMs, CI build plans etc, it will be done in the nearest major Clover release (currently planned for end of 2015) and appropriate migration guides will be prepared. New plugin name will be: *clover-maven-plugin* {panel} *Problem reported:* According the Maven's Plugin Naming Convention, Clover's plugin artifactID violates the Apache Maven Trademark. The artifactId should be clover2-maven-plugin. I would even suggest removing the 2 from the artifactId. [Plugin Naming Convention and Apache Maven Trademark|https://maven.apache.org/guides/plugin/guide-java-plugin-development.html] *Scope of the change:* _Before release_ (/) investigate if we can use clover-maven-plugin or must use cloverX-maven-plugin - _will be renamed to clover-maven-plugin_ (/) decide if major Clover release will be numbered 4.1.0 -or 5.0.0- (as per [Semantic Versioning|http://semver.org]) (/) prepare migration message in maven-clover2-plugin pom.xml for versions 4.0.x, similarly as it was done for Clover Core (com.cenqua.clover:clover:3.3.0) - _message added in pom in 4.0.6_ (/) rename maven-clover2-plugin artifactId for 4.1.0 / -5.0.0- , update integration tests (/) prepare migration guide for Clover 4.1 / -5.0- Release Notes (/) update Clover's Tutorial (Moneybags bundled in clover-ant.zip) -> see also _After release_ (!) update documentation on confluence.atlassian.com, docs.atlassian.com, answers.atlassian.com (rename all references of maven-clover2-plugin), add comments on stackoverflow (!) update Bamboo Clover Plugin (automatic integration shall use new maven plugin) -> (!) check Hudson / Jenkins Clover Plugin if they have any references (!) update Clover Examples repository |
New:
{panel:title=Decision|titleBGColor=#205081|bgColor=#59afe1}
We are currently working on renaming Maven Clover2 Plugin according to the naming convention recommended by the Apache Maven project. Due to a fact that this is a major breaking change, forcing customers to modify their POMs, CI build plans etc, it will be done in the nearest major Clover release (currently planned for end of 2015) and appropriate migration guides will be prepared. New plugin name will be: *clover-maven-plugin* {panel} *Problem reported:* According the Maven's Plugin Naming Convention, Clover's plugin artifactID violates the Apache Maven Trademark. The artifactId should be clover2-maven-plugin. I would even suggest removing the 2 from the artifactId. [Plugin Naming Convention and Apache Maven Trademark|https://maven.apache.org/guides/plugin/guide-java-plugin-development.html] *Scope of the change:* _Before release_ (/) investigate if we can use clover-maven-plugin or must use cloverX-maven-plugin - _will be renamed to clover-maven-plugin_ (/) decide if major Clover release will be numbered 4.1.0 -or 5.0.0- (as per [Semantic Versioning|http://semver.org]) (/) prepare migration message in maven-clover2-plugin pom.xml for versions 4.0.x, similarly as it was done for Clover Core (com.cenqua.clover:clover:3.3.0) - _message added in pom in 4.0.6_ (/) rename maven-clover2-plugin artifactId for 4.1.0 / -5.0.0- , update integration tests (/) prepare migration guide for Clover 4.1 / -5.0- Release Notes (/) update Clover's Tutorial (Moneybags bundled in clover-ant.zip) -> see also _After release_ See CLOV-1828. |