I personally think its ok if we use the artifact name in jira, like in this case - especially as the name might change. Whatever we decide, it needs to be consistent across a module- meaning if we start to rename with version 1.4.0 then we also need to rename all previous versions.
Now from a customer perspective, if someone wants to file a bug against the slingfeature-maven-plugin (which is what is used and what is visable in the error from maven), I think someone finds slingfeature-maven-plugin-1.4.0 much easier than 'OSGi Feature Maven Plugin 1.4.0' which is nowhere visible in maven output.
Regards Carsten Am 22.09.2020 um 17:07 schrieb Robert Munteanu:
Hi, I am in a middle of a release (and using the committer cli [1]) and I got stuck due to an unexpected (for the tool) version: java.lang.IllegalArgumentException: No releases found in 'slingfeature-maven-plugin-1.4.0' To go for the quick fix, I renamed that version to 'OSGi Feature Maven Plugin 1.4.0', matching the module name. This is quickly reversible so I just did the change. Of course, the tool can be changed, but there is some value IMO in having module names and Jira version names aligned, namely: - it is clear for users and tools what release maps to which module - we don't have to invent a second name for the same thing :-) I'm open to saying that version names can be arbitrary, but then we can simplify our life by having matching names. Thanks, Robert [1]: https://github.com/apache/sling-org-apache-sling-committer-cli/
-- -- Carsten Ziegeler Adobe Research Switzerland [email protected]
