> On 6 Jan 2014, at 23:44, Rene Groeschke <gra...@breskeby.com> wrote: > > Hello Pawel, > > I think all current core developer use idea for working on the gradle > codebase. > It should be enough to run "./gradlew idea" on the commandline in your gradle > repo and then import the project in idea. We noticed issues with Idea13, but > it definitely works out of the box with Idea12. If you really want to use > Idea13 to work on the gradle you should import it via the IDEA gradle support.
Really? Does this work? I'd be surprised given that we customise the mapping. > > cheers, > René > > >> <postbox-contact.jpg> Paweł Stawicki 6 Jan 2014 23:45 >> Hello, >> >> I found some bug in gradle >> (http://forums.gradle.org/gradle/topics/gradle_still_tries_to_figure_out_version_of_dependency_even_if_its_excluded >> and >> http://stackoverflow.com/questions/20935891/gradle-cannot-resolve-dependency) >> and thought that maybe I'll be able to fix it myself. >> >> So I cloned gradle repository, run "gradle idea" and tried to run >> "Gradle" Run Configuration in IDEA. Without luck. I spent few hours >> setting module dependencies to exported, added library for core >> subproject testFixtures, and now it all fails with Groovyc: Internal >> groovyc error: code 1 >> >> Anybody here using IDEA for gradle development? Or what most of you >> guys use for it? >> >> Best regards >> -- >> Paweł Stawicki >> http://pawelstawicki.blogspot.com >> http://szczecin.jug.pl >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email
