[jira] [Comment Edited] (GROOVY-8666) New partial groovy 2.5 causes split-packages itself

["Paul King (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GROOVY-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523384#comment-16523384 ] 

Paul King edited comment on GROOVY-8666 at 6/26/18 8:08 AM:
------------------------------------------------------------

Are you placing the Groovy 2.5 jars on your classpath or modulepath. Groovy 2.5 supports JDK9+ using the former approach but not the latter. You'll have to wait for Groovy 3 if you want to do the latter. Is there any particular reason why you want the latter at this point? Or are you just trying to be fully modular in one step?


was (Author: paulk):
Are you placing the Groovy 2.5 jars on your classpath or modulepath. Groovy 2.5 supports JDK9+ using the former approach but not the latter. You'll have to wait for Groovy 3 if you want to do the later. Is there any particular reason why you want the latter at this point? Or are you just trying to be fully modular in one step?

> New partial groovy 2.5 causes split-packages itself
> ---------------------------------------------------
>
>                 Key: GROOVY-8666
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8666
>             Project: Groovy
>          Issue Type: Bug
>          Components: release, XML Processing
>    Affects Versions: 2.5.0
>            Reporter: Josef Härtl
>            Priority: Blocker
>
> The splitting of groovy into smaller causes another, very major, problem:
> First, consider the "main" groovy jar: It contains the package groovy.util with numerous classes.
> Secondly, consider the groovy-xml jar. It contains the package groovy.util and therein the classes XMLParser etc.
> Regardless whether you use OSGi (like in our case) or Java 9 (what we are migrating to): This presents a split-package itself: As we already reproduced in our build: Whatever jar of these is loaded first wins the groovy.util package and "overrides" the other.
> As a result, it's become random whether our users can use XMLParser or not. Sometimes it is found, sometimes it's not. I consider this a very major problem and a blocker as it makes execution unreliable and randomish. I did not check but somewhat guess that this is not the only collision of this sort.
> Therefore, the splitting of groovy 2.5 into smaller pieces introduced split-packages to itself. If one wants to split groovy, the split will have to follow package borders.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)