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

[Darin Swanson <Darin_Swanson@xxxxxxxxxx>]

I would have to know a little more of the layout of your project etc but the difference is likely do to the layout differences between running outside of Eclipse and running within Eclipse.  
I believe this is one of those cases where the "location" variant of the property task should be used.

Darins

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

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

Hi Darin,
thanks for your kind response (and thanks to Sasha too), as ususal the 
support we get from IBM is always superb, and i know what i'm talking 
about since i worked for IBM for 22 years.
Now on the bad part, shame on me, it turned out that the problem was not 
what i supposed.
The problem is that in the build.xml the dependencies.xml file was 
declared as follows:
  <property name="app.dependencies" value="dependencies.xml"/>
since it is in the same directory of build.xml.
Now, when i run ant outside of eclipse the file is found, but when ant 
is run from eclipse the file is not found.
If i declare:
  <property name="app.dependencies" value="${basedir}/dependencies.xml"/>
where ${basedir} is equal to ".",  the directory where build.xml is, 
then everything works ok, also using xalan/xerces from eclipse plugin.
Any idea why?

Thanks,  Gabriele.

Darin Swanson wrote:

>
> 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
>

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