Re: [platform-ant-dev] Cannot define custom ant task using xlalan/xerce

[Darin Swanson <Darin_Swanson@xxxxxxxxxx>]

Gabriele,

Eclipse requires the Ant integration to use the Xerces classes / JARs provided within the Xerces plugin.
This is indicated in the Eclipse release notes known issues:
        Explicitly adding the Xerces JARs to the runtime Ant classpath is no longer required and can cause problems. The Xerces classes are loaded from         the org.apache.xerces plug-in provided with Eclipse. For most Ant distributions, the Xerces JARs cannot even be in the same physical location as                 the ant.jar and optional.jar. This results from the Ant JARs containing manifest files which contain classpath entries pointing to the Xerces JARs. (see         bugs 33664, 33117, 34151).
This is what results in the VerifyError.
What I would recommend is add the Xalan JAR to the Ant runtime classpath and ensure that the Xerces JARs are not on the runtime classpath.

HTH
Darins

Gabriele Garuglieri <gabriele.garuglieri@xxxxxxxxxx> Sent by: platform-ant-dev-admin@xxxxxxxxxxx 04/10/03 02:31 AM Please respond to platform-ant-dev

To:        platform-ant-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-ant-dev] Cannot define custom ant task using  xlalan/xerces

eclipse 2.1
java (build 1.4.1_02-b06)

I'm tring to use use an ant build.xml where there's defined an ant task 
that uses xalan/xerces to parse an xml file.
When used outside of eclipse with xalan 2.4.1 and xerces 2.2.0 
everything works ok.
When i try to use the same build.xml from within eclipse the task blows 
off with the following message:
BUILD FAILED: file:C:/home/dev/XMLiv/build/build.xml:247: Unable to 
parse xml file:dependencies.xml

If i try to put those xalan/xerces jars earlier in the classpath now 
there is an eclipse ant task that blows off:
  +User task: eclipse.refreshLocal 
org.eclipse.core.resources.ant.RefreshLocalTask
BUILD FAILED: java.lang.VerifyError: (class: 
org/apache/xerces/parsers/IntegratedParserConfiguration, method: 
configurePipeline signature: ()V) Incompatible type for getting or 
setting field.

The same happens if, following the doc, i try to use an external ant 
implementation defining ANT_HOME from External tools panel.

In my opinion, the ant support should allow users to have a complete 
control on the ant classpath and tasks like jbuilder8 does where in fact 
this same build.xml works ok.
I should be able to completely exclude or selectively include any 
eclipse library or plugin from the build without loosing the possibility 
to launch ant targets from the ant view.

In a few words i think that there should be the possibility to unselect 
from the External tools panel the task, types and properties defined in 
the general ant runtime, for a specific run.

Regards,  Gabriele

Disclaimer: before anybody says "stop doing nasty things with ant and do 
it the eclipse way" like someone did once, i have to say that we develop 
on W2k but the application deployment build is done in strictly 
controlled environment on Solaris servers using ant, so we must ensure 
that the build works the same in all the platforms.

_______________________________________________
platform-ant-dev mailing list
platform-ant-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ant-dev