You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ra...@apache.org on 2019/12/02 13:39:09 UTC
[sling-org-apache-sling-scripting-javascript] branch master
updated: SLING-8695 - Make sure that the Sling modules' pom files provide a
name value that's consistent with the JIRA releases
This is an automated email from the ASF dual-hosted git repository.
radu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-javascript.git
The following commit(s) were added to refs/heads/master by this push:
new c1be305 SLING-8695 - Make sure that the Sling modules' pom files provide a name value that's consistent with the JIRA releases
c1be305 is described below
commit c1be305ff823b3a3fd0028d7815d219bdf834b2f
Author: Radu Cotescu <ra...@apache.org>
AuthorDate: Mon Dec 2 14:38:57 2019 +0100
SLING-8695 - Make sure that the Sling modules' pom files provide a name value that's consistent with the JIRA releases
---
pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pom.xml b/pom.xml
index 1e1676d..5985e69 100644
--- a/pom.xml
+++ b/pom.xml
@@ -32,7 +32,7 @@
<version>3.0.5-SNAPSHOT</version>
<packaging>bundle</packaging>
- <name>Apache Sling Scripting JavaScript Support</name>
+ <name>Apache Sling Scripting JavaScript</name>
<description>Support for JavaScript scripting</description>
<scm>