[
https://issues.apache.org/jira/browse/HBASE-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585858#comment-13585858
]
nkeywal commented on HBASE-7927:
--------------------------------
Ok, thanks to you Gustavo I understand my error.
The issue occurs only with -Dhadoop.profile=2.0, in this case we have twice
netty. With hadoop 1 it's ok. I was generating the classpath with hadoop2 and
checking the dependency with hadoop1.
And it's actually something that already burnt me in the past in HBASE-7104.
I'm gonna change the title of this jira to make this clear.
> Bad classpath generation
> ------------------------
>
> Key: HBASE-7927
> URL: https://issues.apache.org/jira/browse/HBASE-7927
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 0.96.0
> Reporter: nkeywal
>
> I don't know why, but when you do a mvn dependency:tree, everything looks
> fine. When you look at the generated target/cached_classpath.txt you see 2
> versions of netty: netty-3.2.4.Final.jar and netty-3.5.9.Final.jar.
> This is bad and can lead to unpredictable behavior.
> I haven't looked at the other dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
