On 4/11/11 12:54 AM, Felipe Carvalho wrote: > A webinar or a simple screencast would help a lot on troubleshooting.
We can't mandate using a particular IDE to develop against the project. We can make it easier to use different IDEs. > Indepent of the IDE, though, I would suggest putting the project under an > automated build tool structure (Maven, Gradle, whatever) instead of Ant, > which makes it easier for developers to choose their preferred IDE. We have discussed Gradle - given that we're in the Groovy space, that would be preferable to Maven. p > Many IDEs integrate seamless with Maven and Grails projects (NetBeans and > Intellij are great examples of this) for example, which facilitates for > developers to switch between IDEs. > > One thing I can say about Intellij (I've been working with it for the last 6 > months) is that it's got the best Groovy integration I've seen among major > IDEs -- I had tried Eclipse (STS) and NetBeans before. > > On Sun, Apr 10, 2011 at 8:11 PM, Matthew Sacks > <[email protected]>wrote: > >> Hi Folks, >> I have struggled a bit using Eclipse with Groovy projects previously >> (although for all intensive purposes it will work) , so I personally >> recommend using IntelliJ for developing kitty projects as a matter of >> preference. I'm not sure if you have to be an official committer, but I know >> Jetbrains, the company that makes IntelliJ offers a special open source use >> license to the ASF: >> http://www.jetbrains.com/eforms/openSourceRequestApache.action?licenseRequest=IIOSA >> >> That being said, I'd like to throw it out there that maybe it would help >> the new people on board if we hosted a simple webinar (and recorded it) on >> how to get all set up to be developing for Kitty and resolve problems >> getting setup. Would this be helpful? >> >> >> msacks >
signature.asc
Description: OpenPGP digital signature
