Bug #3080
very long Groovy compilation time when launching import modules for the first time in a session
Status: | New | Start date: | 01/16/2020 | |
---|---|---|---|---|
Priority: | Urgent | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | Macros | Spent time: | - | |
Target version: | TXM 0.8.4 |
Description
Currently there is a long compilation time before running any Groovy script (at first run or after editing a script).
Solution 0¶
- resolve TXM plugin dependencies to only keep the necessary plugin loaders (e.g the "org.txm.rcp.*" plugins usually include "org.txm.rcp" plugin)
Solution A¶
Do not compile the import modules scripts if sources are not newer than the class files. Hence :
- ship the import modules Groovy classes with TXM
- generalize to all Groovy scripts if possible
- compare the class file compilations date with the last source modifications date
Find a way to:
- pre-compile Groovy scripts published by TXM plugins (org.txm.groovy.core, etc.)
- and ensure the pre-compiled classes are overriden by the TXMHOME/scripts/groovy/user Groovy scripts
Solution B¶
- restore the Groovy class files build by the RCP build
- if necessary, force the GroovyScriptEngine to recompile the import module files (importer, annotate, compiler, pager) and their dependencies (Groovy classes)
Related issues
History
#1 Updated by Matthieu Decorde over 2 years ago
- Description updated (diff)