hallo hans, thank you for the valuable feedback.
initially my plugin was implemented in groovy. i changed it to java to see how this is done in java and to have a better eclipse-support (eclipses groovy-support is still quite limited). but you are right. to implement custom-plugins in groovy has some advantages and i recommend this too. i will rollout the new gradle to the users after 0.6.1 is published. gradle 0.6 is a big step forward ... still reading through the manual ... esp. interested in the handling of configurations. gruesse hdockter wrote: > > At least not for custom plugins, except if there are performance > issues. The Gradle core does implement all plugins in Java. The reason > is that we want to have a pure Java core which can be used without > Groovy. This gives us the possibility in the future to easily add > build script engines for other languages (in particular Java). > -- View this message in context: http://www.nabble.com/trying-to-improve-my-custom-resolver-setup-tp23706699p23738524.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
