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

rombert pushed a change to annotated tag 
org.apache.sling.scripting.sightly.repl-1.0.2
in repository 
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-sightly-repl.git.


      at 15e414a  (tag)
 tagging 553748131a52c354d0d582283a89e5b22eef0a5a (commit)
      by Radu Cotescu
      on Thu Oct 8 11:07:16 2015 +0000

- Log -----------------------------------------------------------------
org.apache.sling.scripting.sightly.repl-1.0.2
-----------------------------------------------------------------------

This annotated tag includes the following new commits:

     new 8269d6c  SLING-4704 - Move the Sightly scripting engine artifacts from 
contrib to bundles
     new 10d47b2  SLING-4713 - Update Sightly REPL to display generated Java 
source code
     new 21f30c9  svn:ignore
     new 83049ab  Update to Sling Parent 23
     new c9c95a0  Remove superflous sling.java.version=6 as it's the default now
     new 0a124b1  Added missing copyright headers
     new 34b22e6  set parent version to 24 and add empty relativePath where 
missing
     new 06d315e  Update the main reactor to parent 25
     new a0a06a6  SLING-5125 - Make Sightly REPL JavaScript and CSS 
dependencies local to allow offline use
     new 6bb0ca0  SLING-5126 - Provide information on the Sightly REPL Java tab 
on how to enable source code generation
     new 4e69695  SLING-5127 - Implement browser history support for the 
Sightly REPL tabs
     new 815b7be  trivial: removed duplicate information from the NOTICE file
     new ba9c8cb  [maven-release-plugin] prepare release 
org.apache.sling.scripting.sightly.repl-1.0.2
     new 5537481  [maven-release-plugin] copy for tag 
org.apache.sling.scripting.sightly.repl-1.0.2

The 14 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]>'].

Reply via email to