You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Josef Härtl (JIRA)" <ji...@apache.org> on 2018/06/26 05:59:00 UTC
[jira] [Updated] (GROOVY-8666) New partial groovy 2.5 causes
split-packages itself
[ https://issues.apache.org/jira/browse/GROOVY-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josef Härtl updated GROOVY-8666:
--------------------------------
Description:
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.
Therefore, the splitting of groovy 2.5 into smaller pieces introduced split-packages to itself.
was:
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) 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.
Therefore, the splitting of groovy 2.5 into smaller pieces introduced split-packages to itself.
> 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.
> Therefore, the splitting of groovy 2.5 into smaller pieces introduced split-packages to itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)