[
https://issues.apache.org/jira/browse/BEAM-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754219#comment-16754219
]
Kenneth Knowles edited comment on BEAM-6519 at 1/28/19 6:22 PM:
----------------------------------------------------------------
[~romain.manni-bucau] can you add some more detail? You mean that there are
"split jars" as they call them, where the same namespace is used in another jar?
I know that we have some of those, and I agree it is a very bad practice. I did
not know it was a blocker, so that would be a good reason to prioritize fixing
them and adding a check. (I know proguard checks for this)
was (Author: kenn):
[~romain.manni-bucau] can you add some more detail?
> java extension must not use org.apache.beam.sdk.util
> ----------------------------------------------------
>
> Key: BEAM-6519
> URL: https://issues.apache.org/jira/browse/BEAM-6519
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Affects Versions: 2.9.0
> Reporter: Romain Manni-Bucau
> Assignee: Romain Manni-Bucau
> Priority: Blocker
>
> Some shades of beam reuse sdk java core packages (the util one in particular)
> This is preventing to use beam in several environments (OSGi, classloader
> isolation, java 11/jpms etc), please fix it asap.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)