[
https://issues.apache.org/jira/browse/GROOVY-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692296#comment-17692296
]
Ken Hu commented on GROOVY-10934:
---------------------------------
Thanks for your quick response on this issue [~emilles] . I gave your
suggestion a try and it seems to have worked.
I did have a follow-up question. One of the possible reasons we were adding
imports as part of the source is due to the flexibility it provided with our
plugin system. Our plugin system essentially allows users to dynamically add
and remove imports during a single session. Is it safe to change the
CompilerConfiguration/ImportCustomizer during a single shell session? Is it ok
to add multiple ImportCustomizers to a CompilerConfiguration?
> Performance when Resolving Import Statement
> -------------------------------------------
>
> Key: GROOVY-10934
> URL: https://issues.apache.org/jira/browse/GROOVY-10934
> Project: Groovy
> Issue Type: Question
> Components: Groovysh
> Affects Versions: 3.0.5, 2.5.17
> Reporter: Ken Hu
> Priority: Major
> Attachments: Groovy10934.groovy
>
>
> The time it takes to resolve imports for scripts seems to have increased
> substantially since fixing the issue for GROOVY-5103. This can have a major
> impact on performance when a simple script that contains many imports is
> executed because the majority of the time will be spent resolving the
> imports. Are there any workarounds for this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
