[
https://issues.apache.org/jira/browse/BEAM-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813662#comment-16813662
]
Reuven Lax commented on BEAM-7042:
----------------------------------
The current design of schemas is for them to be a type system for Beam, which
means they are the core of Beam now, not a layer on top. This was the design
that was agreed upon, and over the past year+ schemas have been tightly
integrated into the core. This can of course be reevaluated on the dev list,
but is off topic for this Jira issue.
Dependency conflicts can (and sadly) do happen due to any and all of our
dependencies, so there's nothing special about Antlr here. Likely the right
answer is to vendor Antlr. Is there documentation anywhere about how to go
about the vendoring process?
> [regression] org.apache.beam:beam-sdks-java-core:jar:2.12.0 dependencies are
> way fatter and conflicting than before
> -------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-7042
> URL: https://issues.apache.org/jira/browse/BEAM-7042
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Romain Manni-Bucau
> Priority: Major
> Fix For: 2.12.0
>
>
> Hi guys,
> seems current sdk brings antlr and its transitive deps which is quite
> unlikely and has a huge probability to conflict (antlt, jsonp in an outdated
> version at least for the one breaking my apps)
> can it be cleaned up for the 2.12 to avoid to break application please?
> Thanks,
> Romain
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
