You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Daniel Warneke (JIRA)" <ji...@apache.org> on 2014/07/07 21:28:35 UTC
[jira] [Commented] (FLINK-386) Duplicate dependencies in lib folder
[ https://issues.apache.org/jira/browse/FLINK-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054070#comment-14054070 ]
Daniel Warneke commented on FLINK-386:
--------------------------------------
Unfortunately, there is no easy fix for this, because the duplicate entries in the lib directory refer to libraries with different Maven group IDs, for example:
stax:stax-api:jar:1.0.1
javax.xml.stream:stax-api:jar:1.0-2
or
org.mortbay.jetty:jetty-util:jar:6.1.26
org.eclipse.jetty:jetty-util:jar:8.0.0.M1
As a result, Maven’s strategies to resolve conflicting dependency versions do not work here. I still suspect the different libraries to contain mostly similar or even identical code (maybe the artifacts have been renamed in the course of time), however there is no way to automatically derive that. Most of the duplicates originate from the hadoop-core dependency, which seems to include some rather outdated stuff.
For now, I cleaned up/upgraded the current dependency tree, so we at least get rid of some unnecessary includes and Scala warnings during the compilation process. The code can be found at:
https://github.com/warneke/incubator-flink/tree/depcleanup
> Duplicate dependencies in lib folder
> ------------------------------------
>
> Key: FLINK-386
> URL: https://issues.apache.org/jira/browse/FLINK-386
> Project: Flink
> Issue Type: Bug
> Reporter: GitHub Import
> Assignee: Daniel Warneke
> Labels: github-import
> Fix For: pre-apache
>
>
> There are some dependencies for which two different versions end up in the lib folder
> ```
> servlet-api-2.5-6.1.14.jar
> servlet-api-3.0.20100224.jar
> stax-api-1.0.1.jar
> stax-api-1.0-2.jar
> ```
> As far as I see it, these are transitive dependencies.
> Teh problem is that what classes are available at runtime depends on which jar is loaded first by the classloader. This is somewhat unpredictable and can lead to weird errors in the components that have these dependencies.
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/386
> Created by: [StephanEwen|https://github.com/StephanEwen]
> Labels:
> Created at: Thu Jan 09 19:44:07 CET 2014
> State: open
--
This message was sent by Atlassian JIRA
(v6.2#6252)