Radu Cotescu created SLING-8695:
-----------------------------------
Summary: Make sure that the Sling modules' pom files provide name
value that's consistent with the JIRA releases
Key: SLING-8695
URL: https://issues.apache.org/jira/browse/SLING-8695
Project: Sling
Issue Type: Task
Reporter: Radu Cotescu
In order to easier map a Sling module to a JIRA release we should make sure
that the value provided in the pom in the {{<name>}} tag corresponds to the
JIRA release naming scheme.
Current status (taking Apache Sling Scripting Core as an example):
{code:java|title=Apache Sling Scripting Core pom.xml}
<artifactId>org.apache.sling.scripting.core</artifactId>
<version>2.0.59-SNAPSHOT</version>
<name>Apache Sling Scripting Core implementation</name>
<description>
Sling Scripting core functionality
</description>
{code}
JIRA:
[https://issues.apache.org/jira/projects/SLING/versions/12345580] - "Scripting
Core 2.0.60"
Ideally the mapping should be something like:
{code:java|title=Apache Sling Module Name pom.xml}
<artifactId>org.apache.sling.artifactId</artifactId>
<version>0.0.1-SNAPSHOT</version>
<name>Apache Sling Module Name</name>
<description>
...
</description>
{code}
whereas the JIRA version name corresponding to the module should be "Module
Name 0.0.1-SNAPSHOT".
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
