Done, and since the conflict was ANTLR 2 vs ANTLR 3 it might be much
simpler to resolve as there is no conflict ;)
-
https://discourse.hibernate.org/t/hibernate-in-weblogic-has-a-conflicting-antlr-version-what-to-do/189/5
Thanks,
Sanne
On 6 February 2018 at 13:46, Vlad Mihalcea wrote:
> Thaks
Thaks Sanne,
Can you add your response to the Hibernate forum?
Maybe the forum question will be indexed by Google and other people will
benefit from your answer.
Vlad
On Tue, Feb 6, 2018 at 3:36 PM, Steve Ebersole wrote:
> I started writing the same response but I'll simply +1 Sanne's excelle
I started writing the same response but I'll simply +1 Sanne's excellent
reply
On Tue, Feb 6, 2018, 7:35 AM Sanne Grinovero wrote:
> Repackaging, shading, etc.. are all a nightmare for supporting the
> library down the road so we'd strongly prefer against doing such
> things.
> For users it's a
Repackaging, shading, etc.. are all a nightmare for supporting the
library down the road so we'd strongly prefer against doing such
things.
For users it's a nightmare as well when it comes to debug things, as
it breaks all tools such as having your IDE download the matching
sources for stacktraces,
Hi,
This Hibernate forum question provides a good point:
https://discourse.hibernate.org/t/hibernate-in-weblogic-has-a-conflicting-antlr-version-what-to-do/189
Frameworks like EclipseLink and Spring (
https://twitter.com/starbuxman/status/960854907854249986 ) repackage
dependencies to avoid the
