[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Troubles with IDEA setup

An even less constructive response - you are very wrong, IMHO. :)

I always use Gradle's idea plugin on my projects because it gives me far better control on how the IntelliJ project looks like and what it does then if I "natively imported" it, as Cedric calls it. I find native imports very selective and constraining, e.g. using Gradle's idea plugin allows me to easily specify additional source sets which are then recognised as a source set by IntelliJ and not just a bunch of files in a directory. And I don't share your view that it got harder over time - it's hardly changed since I started to use it and in the end it's just a bit of xml generation, how hard can it be.  

I know it's just a build tool and the expectation is that everything should just work no matter how much people abuse it. But I've learned that by spending some time to dig deeper and learn Gradle a bit better one can do themselves a favour. Especially when it comes to having consistent and working setup of the project in IntelliJ for everybody on the team.


On Wed, May 23, 2018 at 10:26 AM, Russel Winder <russel@xxxxxxxxxxxxx> wrote:
On Wed, 2018-05-23 at 08:22 +0200, Cédric Champeau wrote:
> I managed to do something using the IDE native import (instead of using
> ./gradlew idea) and delegating all actions to Gradle. It's slower feedback,
> but at least I can work.

Not a constructive response per se, more a data point. The Gradle IDEA stuff
got so hard to get right I gave up on it long ago. IntelliJ IDEA seems to have
a far better idea (!) of how to handle Gradle projects than Gradle has of
generating IntelliJ IDEA projects.
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: