[
https://issues.apache.org/jira/browse/HADOOP-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640986#action_12640986
]
Steve Loughran commented on HADOOP-4448:
----------------------------------------
I think in this situation, the correct action would be to halt early. Some
check that the loaded class came from the test.jar would handle that -but there
is no guarantee that other classes wouldn't clash; mixing classes with the same
name is always a disaster unless you have something like OSGi to keep things
under control.
> "hadoop jar" runs wrong jar file in case of name clash
> -------------------------------------------------------
>
> Key: HADOOP-4448
> URL: https://issues.apache.org/jira/browse/HADOOP-4448
> Project: Hadoop Core
> Issue Type: Bug
> Components: util
> Environment: RHEL Linux
> Reporter: John DeTreville
> Fix For: 0.17.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Imagine I run a command as follows:
> hadoop jar test.jar
> Let's imagine that my main module in test.jar is named Sort.
> Let's also imagine that some jar file in my CLASSPATH contains a module also
> named Sort, which also defines main.
> Hadoop will run THAT jar file, not the one I specified.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
