Community
Participate
Working Groups
I created a plugin with a custom ant data-type (taken from the tests - AntTestPath). When I ran a script that used the type, I got the following error: Buildfile: d:\eclipse2.1 \plugins\org.eclipse.ant.tests.core\testscripts\CustomType.xml BUILD FAILED: file:d:/eclipse2.1/plugins/org.eclipse.ant.tests.core/testscripts/CustomType.xml :3: Could not create datatype of type: anttestpath due to java.lang.NoSuchMethodException: <init> Total time: 221 milliseconds For some reason, when using the extesion point, we require the type to have a default constructor. When using a <typedef> or runtime classpath and type preference, the default consturctor is not required. Not sure why there is a difference
Deferred. Not critical.
The only way I could reproduce your problem was to have the types.jar added as a runtime library in the plugin.xml of the plugin: <runtime> <library name=types.jar"/> </runtime> This causes the type to be loaded by the plugin classloader instead of the Ant classloader. This should be another README entry. Can you verify that this is what you were doing Darin?
<<ping>> Have you had a chance to look at this Darin?
<<pong>> I'll look at this today
Yes - when I have the type in a jar that is not part of the plug-in, it works as expected. How do you want to mark this one?
Falls under the known issues section of the currnet Eclipse release notes. See "Custom Ant tasks and Ant types must be separate from plug-in library JARs Closing.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.