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 17:25:40 UTC
[jira] [Comment Edited] (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=15089447#comment-15089447 ]
Radu Cotescu edited comment on SLING-5409 at 1/8/16 4:24 PM:
-------------------------------------------------------------
It seems that while the compiler doesn't impose a certain package name, its handling of the package name changes the alignment of the code so that the debugging of a Use object becomes difficult.
The replacement of the package name should be done in-place.
was (Author: radu.cotescu):
It seems that while the compiler doesn't impose a certain package name, its handling of the package name changes the alignment of the code so that debugging of a Use object becomes difficult.
The replacement of the package name should be done in-place.
> 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.8
>
>
> 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)