You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by cz...@apache.org on 2022/03/29 05:52:20 UTC

[sling-org-apache-sling-scripting-sightly] branch master updated: [maven-release-plugin] prepare for next development iteration

This is an automated email from the ASF dual-hosted git repository.

cziegeler pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-sightly.git


The following commit(s) were added to refs/heads/master by this push:
     new f279fd5  [maven-release-plugin] prepare for next development iteration
f279fd5 is described below

commit f279fd5c71d5eb0f4c722fd05488d37e90413597
Author: Carsten Ziegeler <cz...@apache.org>
AuthorDate: Tue Mar 29 07:52:16 2022 +0200

    [maven-release-plugin] prepare for next development iteration
---
 pom.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pom.xml b/pom.xml
index ef6722d..ff289a4 100644
--- a/pom.xml
+++ b/pom.xml
@@ -37,7 +37,7 @@
         The versioning scheme defined here corresponds to SLING-7406 (<module_version>-<htl_specification_version>). Take care when
         releasing to only increase the first part, unless the module provides support for a newer version of the HTL specification.
     -->
-    <version>1.4.18-1.4.0</version>
+    <version>1.4.19-1.4.0-SNAPSHOT</version>
     <name>Apache Sling Scripting HTL Engine</name>
 
     <description>
@@ -49,7 +49,7 @@
         <connection>scm:git:https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-sightly.git</connection>
         <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-sightly.git</developerConnection>
         <url>https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-scripting-sightly.git</url>
-      <tag>org.apache.sling.scripting.sightly-1.4.18-1.4.0</tag>
+      <tag>HEAD</tag>
   </scm>
 
     <properties>
@@ -57,7 +57,7 @@
         <!-- There is significant difference between the locale data provided in JDK8 and starting with JDK9. In order to achieve
         compatibility between newer versions of the JDK and JDK8, we use COMPAT as the default locale data provider for tests. -->
         <java.locale.providers>COMPAT,JRE,SPI</java.locale.providers>
-        <project.build.outputTimestamp>2022-03-29T05:50:32Z</project.build.outputTimestamp>
+        <project.build.outputTimestamp>2022-03-29T05:52:15Z</project.build.outputTimestamp>
     </properties>
 
     <!-- ======================================================================= -->