[
https://issues.apache.org/jira/browse/BEAM-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758005#comment-16758005
]
Romain Manni-Bucau commented on BEAM-6519:
------------------------------------------
Well, beam project setup doesnt respect very common java basis of modularity
and gradle setup with vendoring made it even worse. Also there is no real test
except for flat classpath launches, this is why it occurred and disnt in most
other asf projects. Fix that and no automotion will be needed, build is already
very slow so if you add a global project check like that it will be even worse
for contributors who already need to go through a huge step to fix a typo in a
javadoc. If not set in default build it will be missed. This is why i think it
is better to respect the minimal rule of modularity in java rather than looking
for an automotion adding to the customizations and specificities beam has in
its build for no dev gain.
> 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
> Fix For: 2.11.0
>
>
> 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)
