[
https://issues.apache.org/jira/browse/LUCENE-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16353164#comment-16353164
]
Robert Muir commented on LUCENE-8156:
-------------------------------------
Is there no way to avoid relying on what is in ant's classpath (e.g. like javac
includeAntRuntime=false)? If we can make the build robust, we should do it. A
clear error is one way to do that though. The patch has a typo for "correctly".
> patch-mrjar-classes fails if an old version of ASM is on the Ant classpath
> --------------------------------------------------------------------------
>
> Key: LUCENE-8156
> URL: https://issues.apache.org/jira/browse/LUCENE-8156
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Assignee: Uwe Schindler
> Priority: Major
> Attachments: LUCENE-8156.patch, image-2018-02-06-00-00-35-434.png
>
>
> If some optional tasks that depend on an old version of ASM are installed,
> patching fails with the following error:
> {{/home/jpountz/src/lucene-solr/lucene/common-build.xml:565:
> java.lang.IncompatibleClassChangeError: class
> org.objectweb.asm.commons.ClassRemapper has interface
> org.objectweb.asm.ClassVisitor as super class}}
> The reason is that ClassRemapper is loaded from the right place, but
> ClassVisitor, its parent class, is loaded from the parent classpath which may
> be a different version.
> It is easy to reproduce:
> - download and extract ant-1.10.1 (latest version)
> - run {{bin/ant -f fetch.xml -Ddest=system}}, this will add
> {{lib/asm-2.2.3.jar}} among other files
> - run {{ant clean test}} at the root of lucene-solr.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
