You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Alexey Belostotskiy (JIRA)" <ji...@apache.org> on 2019/05/07 11:06:00 UTC
[jira] [Created] (GROOVY-9110) Add option to specify classLoader
used in GroovyDoc generation
Alexey Belostotskiy created GROOVY-9110:
-------------------------------------------
Summary: Add option to specify classLoader used in GroovyDoc generation
Key: GROOVY-9110
URL: https://issues.apache.org/jira/browse/GROOVY-9110
Project: Groovy
Issue Type: Improvement
Reporter: Alexey Belostotskiy
Attachments: ClassLoaderTest(1).groovy
Based on mailing list thread.
Hello,
We're generating groovydocs in runtime in our app. We use groovydoc as a library, not standalone tool.
It mostly works, but we're experiencing issues with some classes ending up unresolved. I found out that this happens because SimpleGroovyClassDoc is calling its getClass().getClassLoader() to get classloader for class resolution. But in our case, most of classes that we want to link should be loaded via different classloader.
Basically, solution that would work for us, is to replace getClass().getClassLoader() calls in SimpleGroovyClassDoc with Thread.currentThread().getContextClassLoader(), but that might be a breaking change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)