You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2017/06/01 02:20:04 UTC

[jira] [Commented] (SLING-6925) Make JSPC plugin useful to validation and analysys

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

Tobias Bocanegra commented on SLING-6925:
-----------------------------------------

I will provide a patch....

> Make JSPC plugin useful to validation and analysys
> --------------------------------------------------
>
>                 Key: SLING-6925
>                 URL: https://issues.apache.org/jira/browse/SLING-6925
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Maven JSPC Plugin 2.0.8
>            Reporter: Tobias Bocanegra
>            Priority: Minor
>
> the JSPs plugin is very useful to validate the JSPs before they get packaged into the artifact. but the deployment unit might not need to class files but there is currently no way to disable their attachment. further it might be valuable to know which dependencies in the project are really used by the JSPs. this helps developers to optimize the runtime dependencies of their code.
> suggest:
> - add new flag: {{attachClasses}} (default true)
> - analyze the java packages of the class path used to compile the JSPs and report which dependencies are not used.
> - add new flag: {{reportUnusedDependencies}} (default true)
> - add new flag: {{dumpClassPathUsage}} (default false)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)