This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to annotated tag
org.apache.sling.scripting.sightly.compiler.java-1.0.10
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-sightly-compiler.git.
at db2d68f (tag)
tagging e274547986e96e7572bae345393641cdcb495df1 (commit)
by Radu Cotescu
on Fri May 5 12:32:50 2017 +0000
- Log -----------------------------------------------------------------
org.apache.sling.scripting.sightly.compiler.java-1.0.10
-----------------------------------------------------------------------
This annotated tag includes the following new commits:
new 490f8a3 SLING-5787 - Modularise the Sightly script engine
new 7a31e4a trivial: added scm info + updated readme for sightly modules
new 422fb82 svn:ignore
new 8dd902a SLING-5825 - Add support for implicit conversion of Enum to
String
new b9a7109 SLING-6028 - Replace Sightly references with HTL in both code
and documentation
new 8ab06b0 SLING-6033 - Update Sightly bundles to parent pom 28
new 5df0559 trivial: corrected JavaDoc
new 363c9e2 trivial: configured javadoc plugin
new e4dbb3f releng: updated dependency
new 69734bc [maven-release-plugin] prepare release
org.apache.sling.scripting.sightly.compiler.java-1.0.0
new d30cb15 [maven-release-plugin] prepare for next development iteration
new 3219779 releng: updated dependencies
new 8ba6830 SLING-6094 - HTL can generate invalid Java code by using
user-supplied input
new 6d1dbb1 SLING-6094 - HTL can generate invalid Java code by using
user-supplied input
new 2e0d8a0 SLING-6094 - HTL can generate invalid Java code by using
user-supplied input
new abb0b89 SLING-6125 - Switch HTL to OSGi R6 annotations
new a27ca29 [maven-release-plugin] prepare release
org.apache.sling.scripting.sightly.compiler.java-1.0.2
new d5f84d0 [maven-release-plugin] prepare for next development iteration
new 9ded7aa SLING-6146 - SourceIdentifier should not mangle underscore
characters
new 92461e4 [maven-release-plugin] prepare release
org.apache.sling.scripting.sightly.compiler.java-1.0.4
new e1cb43d [maven-release-plugin] prepare for next development iteration
new 2742eb1 SLING-6186 - Add support for checking code coverage with
jacoco
new c969cf7 SLING-6186 - Add support for checking code coverage with
jacoco
new ef52d60 cosmetic: remove empty folders
new d6dd5e7 SLING-6399 - Implement support for date and number formatting
for HTL
new 0b5d5dd SLING-6399 - Implement support for date and number formatting
for HTL
new 6d04096 releng: updated o.a.s.scripting.sightly.compiler dependency
to 1.0.4
new 144ba5c [maven-release-plugin] prepare release
org.apache.sling.scripting.sightly.compiler.java-1.0.6
new 48e5a93 [maven-release-plugin] prepare for next development iteration
new 23eb377 update to next snapshot version until releases are available
on maven central
new 4902b93 SLING-6428 - DateFormat is printed when date-value is empty
new f6e44b3 SLING-6450 - [HTL] Cannot retrieve "length" property for
arrays of primitive types
new a0dd961 [maven-release-plugin] prepare release
org.apache.sling.scripting.sightly.compiler.java-1.0.8
new 0f3e304 [maven-release-plugin] prepare for next development iteration
new ff466dc use Sling Parent 30
new d317aad SLING-6633 - [HTL] NumberFormat should support
String-properties with number value
new 7025655 SLING-6633 - [HTL] NumberFormat should support
String-properties with number value
new 2a401ec SLING-6639 - Avoid split packages in the HTL Engine and HTL
Java Compiler bundles
new bbca405 SLING-6639 - Avoid split packages in the HTL Engine and HTL
Java Compiler bundles
new c89c3f5 [maven-release-plugin] prepare release
org.apache.sling.scripting.sightly.compiler.java-1.0.10
new e274547 [maven-release-plugin] copy for tag
org.apache.sling.scripting.sightly.compiler.java-1.0.10
The 41 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
