[GROOVY-5025] Add control on how Global Transforms are loaded/applied

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.2
• Fix Version/s: 1.9-beta-4
• Component/s: Compiler
• Labels: compiler customizer global security transforms
• Assignee: Cédric Champeau
• Reporter: Fabien Hulliez
• Created: 15/Sep/11 02:39
• Updated: 14/Oct/11 00:28
• Resolved: 07/Oct/11 02:16

Description

It would be nice to have more control on how the global transforms are loaded and applied. For example, there is no way to avoid the GrabAnnotationTransformation to be applied even if you forbid it through the use of a (Security) CompilerCustomizer.

According to Cédric Champeau it is not that trivial because the Global Transforms process is tightly hardwired with the compilation process. The only (ugly) workaround is to override the Groovy classloader.

It should be nice if you could specify a sort of "blacklist" of GlobalTransforms that has to be ignored during the compilation phase.

Ideally, it should be possible to do this with a Compiler Customization.

Issue Links

• is depended upon by: GROOVY-5055 Default AST transformations classes list to be set from command line and groovy-starter.conf