I tried the second approach, extending the Eclipse plugin and adding additional task eclipsePde. I also added similar test cases and all looked fine. I could execute the following tasks successfully
$ gradle eclipseJdt $ gradle eclipsePde However running $ gradle eclipse did fail with some wrong type exception. It seems to be that the eclipseJdt type was also used for the eclipsePde task. I could not figure out the exact problem though. It seems to be related to the new approach and how worker tasks get registered with a lifecycle task!? -----Original Message----- From: Peter Niederwieser [mailto:[email protected]] Sent: Tuesday, April 26, 2011 10:24 AM To: [email protected] Subject: [gradle-dev] Re: Gradle Eclipse Plugin Glaeser, Thomas wrote: > > The implementation could be identical to task eclipseJdt ... But how > can these additional tasks get registered with the Eclipse plugin? > There is no way to externally register tasks with a plugin. You either need to fork the plugin class, or inherit from it. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
