Ken -Thanks for the quick response. But the questions was more of technical nature. The whole IDE workspace generation got apparently redesigned with 1.0-m-1. Therefore I was wondering what to expect and how to extend the available functionality. It should be rather simple to add another task like eclipseJdt, therefore I tried option (1) however without little success ... therefore the post to gradle-dev.../Thomas
________________________________ From: Ken Sipe [mailto:[email protected]] Sent: Monday, April 25, 2011 8:51 PM To: [email protected] Subject: Re: [gradle-dev] Additional Gradle Eclipse Plugin Tasks Thomas, I'm not sure what you mean by "get registered" with the eclipse plugin... so I hope I'm answering question correctly. There are 2 ways to get involved: 1) fork the gradle code, modify the code in question to add the functionality you desire and send a pull request to the gradle team. 2) submit a jira request (with as much detail as possible) details: http://wiki.gradle.org/display/GRADLE/How+to+contribute+a+patch+to+Gradl e Ken Sipe | [email protected] | blog: http://kensipe.blogspot.com On Apr 25, 2011, at 12:37 PM, Glaeser, Thomas wrote: Hi - I'm looking for suggestions on how to extend the Eclipse plugin? Eclipse plugin comes with an eclipseJdt task that writes file .settings/org.eclipse.jdt.core.prefs. Similarly, other prefs files need to get persisted, e.g. - .settings/org.eclipse.core.resources.prefs - .settings/org.eclipse.pde.core.prefs The implementation could be identical to task eclipseJdt ... But how can these additional tasks get registered with the Eclipse plugin? Thanks, Thomas
