[SLING-6925] Make JSPC plugin useful to validation and analysis

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Maven JSPC Plugin 2.0.8
• Fix Version/s: Maven JSPC Plugin 2.1.0
• Component/s: Maven Plugins and Archetypes
• Assignee: Carsten Ziegeler
• Reporter: Tobias Bocanegra
• Created: 01/Jun/17 02:19
• Updated: 15/Jun/17 13:22
• Resolved: 02/Jun/17 12:24

Description

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)

Issue Links

• relates to: SLING-6936 JSPC plugin should save compilation report
• links to: GitHub Pull Request #240