[
https://issues.apache.org/jira/browse/MAPREDUCE-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916204#action_12916204
]
Thomas Koch commented on MAPREDUCE-1283:
----------------------------------------
+1 for this issue, however your solution is not that universal. If somebody
uses Maven then there usually isn't a lib/ folder. So it would be better to
read out the classpath of the project and include whatever jars are found in
the classpath.
However this could be quite a bit and some jars may already be available on the
cluster in hadoop's classpath, so there needs to be some more configurability:
exclude jars, or include classpath entries in the manifest files if we're
certain that some jars are available on the cluster.
> Support including 3rd party jars supplied in lib/ folder of eclipse project
> in hadoop jar
> -----------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1283
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1283
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/eclipse-plugin
> Environment: Any
> Reporter: Amit Nithian
> Priority: Minor
> Attachments: jarmodule.patch
>
>
> Currently, the eclipse plugin only exports the generated class files to the
> hadoop jar but if there are any 3rd party jars specified in the lib/ folder,
> they should also get packaged in the jar for submission to the cluster.
> Currently this has to be done manually which can slow down development. I am
> working on a patch to the current plugin to support this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
