[
https://issues.apache.org/jira/browse/GROOVY-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523555#comment-16523555
]
Josef Härtl commented on GROOVY-8666:
-------------------------------------
Regarding Java 9: Considering your posts above and the reference
implementations oracle itself suggests in JEP-320, maybe java 9 on classpath is
indeed more relaxed about split-packages (as long they do not overlap with a
module). So i'm dropping that point for now: Can't say for sure. Perhaps
someone can.
Regarding OSGi: It eludes me why this is a minor bug. For OSGi-users this is
quite a blocker. I see that it could be rather hard to fix without breaking
structure and maintaining the split for java9. Perhaps version 3 will also help
OSGi, but i guess version 3 isn't to be expected soon?
Would it be an intermediary option to release the "fat" jar under a different
name, e.g. "-all-osgi"? That would relax things for OSGi quite a bit while
clearly stating what it is for.
> 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
> Affects Versions: 2.5.0
> Reporter: Josef Härtl
> Priority: Minor
>
> 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)
