You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2016/01/08 18:57:39 UTC

[jira] [Commented] (SLING-5409) Enhance the SightlyJavaCompilerService to not enforce a package name for Use objects stored in the repository

    [ https://issues.apache.org/jira/browse/SLING-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089611#comment-15089611 ] 

Radu Cotescu commented on SLING-5409:
-------------------------------------

Finally fixed in [r1723769|https://svn.apache.org/viewvc?view=revision&revision=1723769].

> Enhance the SightlyJavaCompilerService to not enforce a package name for Use objects stored in the repository
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-5409
>                 URL: https://issues.apache.org/jira/browse/SLING-5409
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting Sightly Engine 1.0.6
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: Scripting Sightly Engine 1.0.10
>
>
> The {{SightlyJavaCompilerService}} currently enforces a certain package name for Use objects stored in the repository - the JCR path transformed into a valid Java package name. However, the {{SightlyJavaCompilerService}} should be more lenient and automatically define the correct package name for the Use object so that a move of said object to a different path doesn't require a refactor to adapt the class' package name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)