[
https://issues.apache.org/jira/browse/APEXCORE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517068#comment-15517068
]
Thomas Weise commented on APEXCORE-540:
---------------------------------------
The solution is to alert the user of such problematic dependencies by default.
It is ultimately the user that has to decide what is needed, but the default
behavior of the application archetype should be to avoid silent inclusion that
leads to mysterious and for newcomers hard to diagnose errors.
I played with exclusion in copy-dependencies but realized that this is not
correct. It may be the users intent to bundle a patch for a hadoop jar etc. and
the build should not make silent assumptions. The better and more flexible
approach is the enforcer rule.
> Exclude hadoop dependencies from app packages
> ---------------------------------------------
>
> Key: APEXCORE-540
> URL: https://issues.apache.org/jira/browse/APEXCORE-540
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Thomas Weise
> Assignee: Thomas Weise
>
> Often users run into problems when running their applications on the cluster
> because there are bundled dependencies that conflict with what the cluster
> provides, especially Hadoop. This happens because other dependencies may
> introduce a transient dependency on older versions of Hadoop that unknowingly
> get bundled.
> https://lists.apache.org/thread.html/1e7cb53e75212e175ea2704663defea7bf10b65f3a6d02304141c4a9@%3Cdev.apex.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
