[
https://issues.apache.org/jira/browse/MAPREDUCE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242749#comment-13242749
]
Alejandro Abdelnur commented on MAPREDUCE-4091:
-----------------------------------------------
The generated-classpath file has a meaning for running testcases in the current
project. If downstream projects want to leverage that file, they have create it
in their project (i.e. oozie-core creates one to be able to use MiniMR).
Having the generated-classpath file bundled in the JAR is pointless, and as
MAPREDUCE-4082 stated, pollutes the classpath big time.
An alternate way to achieve not having the generated-classpath file in the JAR
is to excluded it in the maven-jar-plugin.
> tools testcases failing because of MAPREDUCE-4082
> -------------------------------------------------
>
> Key: MAPREDUCE-4091
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4091
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: build, test
> Affects Versions: 2.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 2.0.0
>
>
> MAPREDUCE-4082 moved the generated-classpath file used by MRApp from the main
> classpath to the test classpath.
> The objective of MAPREDUCE-4082 was to remove the generated-classpath file
> from the hadoop-mapreduce-client-app JAR. I've thought that moving it to the
> test-classpath would do the trick.
> This is breaking tools testcases (most likely) because of different
> classloader being used by maven for main classpath and test classpath.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
