>From a project adaption point of view it would have silenced the one or two people on our project that use NetBeans. I know most projects adopt a single IDE but some like us say what ever tool works for you, the common build is in <ant,maven,gradle> The more places gradle works well the easier it is for people to sell to their teams.
- Peace Dave On Fri, Aug 26, 2011 at 5:01 AM, Russel Winder <[email protected]> wrote: > Peter, > > On Fri, 2011-08-26 at 01:33 -0700, Peter Niederwieser wrote: >> Are you referring to IDE project generation from Gradle or direct Gradle >> support in the IDE? In either case, I'm not aware of any current plans to >> support NetBeans. Deep IDE support for authoring Gradle builds (as currently >> under development for Eclipse and IDEA) would probably be difficult to >> achieve, given that all work on NetBeans' Groovy support was stopped years >> ago. > > I think I had in my mind when I wrote, both. If Gradle can generate > project files for Eclipse and IntelliJIDEA, then there is a case for > NetBeans being included. Also Code::Blocks given the push towards C and > C++ capability in Gradle. > > Conversely NetBeans "Just Works" given a Maven POM, and perhaps it > should be able to "Just Work" given a build.gradle? > > Despite having ditched Groovy as a supported language, NetBeans is still > quite popular in the Java community, so deserves some Gradle support? > > -- > Russel. > ============================================================================= > Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] > 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
