[
https://issues.apache.org/jira/browse/GROOVY-10404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17454302#comment-17454302
]
Trevor Flynn commented on GROOVY-10404:
---------------------------------------
Sorry, this was entirely an issue in my code.
> Unexpected class duplication in linux
> -------------------------------------
>
> Key: GROOVY-10404
> URL: https://issues.apache.org/jira/browse/GROOVY-10404
> Project: Groovy
> Issue Type: Bug
> Components: GroovyScriptEngine
> Affects Versions: 4.0.0-rc-1
> Reporter: Trevor Flynn
> Priority: Major
> Attachments: GroovyTest.zip
>
>
> Hello,
> I am not entirely sure on the technical issues behind this problem, they seem
> to stem deep into the platform dependent components of the classloader.
> On windows, when loading a class both from within groovy and from the java
> side through the GroovyClassLoader, the returned class is the same class, and
> can be checked with a simple equality check. But when the same code is run on
> linux, the two classes returned are different classes. Even running an
> `isAssignableForm` will fail between the two.
> I have only seen the behavior on classes referenced by annotations so far.
> It is difficult to describe the complex load behavior that replicates the
> issue, as such I have built a simple example instead. Please see the attached
> example project. It has prebuilt run configurations for IDEA that utilize WSL
> for testing the linux side of the issue.
> This issue is new to groovy 4, and did not exist in groovy 3. I am testing
> using JDK 17 from adoptium.
>
> Please let me know if any other additional information would be useful.
>
> Thank you,
> Trevor Flynn
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
