[
https://issues.apache.org/jira/browse/HADOOP-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863771#action_12863771
]
Steve Loughran commented on HADOOP-6468:
----------------------------------------
adding some extra diagnostics to the build fixes the location
{code}
<whichresource class="org.objectweb.asm.ClassWriter"
property="asm.location"
classpathref="classpath" />
<echo level="verbose" >asm.location=${asm.location}</echo>
{code}
this results in
{code}
[whichresource] Searching for org/objectweb/asm/ClassWriter.class
[echo]
asm.location=jar:file:/home/slo/.ivy2/cache/asm/asm/jars/asm-2.2.3.jar!/org/objectweb/asm/ClassWriter.class
{code}
Something is pulling in asm-2.2.3, this looks to be paranamer itself; yet the
versions aren't in sync. If you drop asm-3.1 into ANT_HOME/lib the build works.
Which implies the 2.2.3 version is the wrong one.
Proposed:
# insert the diagnostics code into the build.xml file,
# add an explicit reference to the asm version hadoop needs, ivy will discard
the old ones.
> compile-core-test failing with java.lang.NoSuchMethodError:
> org.objectweb.asm.ClassWriter.<init>
> ------------------------------------------------------------------------------------------------
>
> Key: HADOOP-6468
> URL: https://issues.apache.org/jira/browse/HADOOP-6468
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 0.22.0
> Environment: Ant 1.7
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Trivial
>
> I'm filing this for something for the search engines to index, so when others
> hit the problem, the solution is here.
> hadoop-common's tests arent' compiling on one machine,
> java.lang.NoSuchMethodError: org.objectweb.asm.ClassWriter.<init>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
