+1 to removing the idea plugin and the eclipse plugin as well. There is an eclipse plugin <https://projects.eclipse.org/projects/tools.buildship> that lets you import gradle projects similar to the intellij one. I think that is what our eclipse developers are using now.
I still think the intellij import interacts with the idea plugin in some way, but maybe we no longer need to configure the import. This is what the gradle docs say about the intellij import: If you simply want to load a Gradle project into IntelliJ IDEA, then use the IDE’s import facility <https://www.jetbrains.com/help/idea/gradle.html#gradle_import>. You do not need to apply this plugin to import your project into IDEA, although if you do, the import will take account of any extra IDEA configuration you have that doesn’t directly modify the generated files — see the Configuration <https://docs.gradle.org/current/userguide/idea_plugin.html#sec:idea_configuration> section for more details. -Dan On Fri, Apr 5, 2019 at 9:23 AM Robert Houghton <rhough...@pivotal.io> wrote: > @upthewaterspout The plugin generates .iml, .ipr files used by old versions > of IntelliJ. The plugin does not give a way to create or modify the > currently-used XML files that live inside of the <root>/.idea directory. > > +1 to removal of the idea plugin. > > On Wed, Apr 3, 2019 at 3:22 PM Dan Smith <dsm...@pivotal.io> wrote: > > > I was under the impression that intellij's import actually used some of > the > > information in the idea{} blocks in the build. See > > https://docs.gradle.org/current/userguide/idea_plugin.html. > > > > But if the import works well without that extra configuration, I think we > > should get rid of it. > > > > -Dan > > > > On Wed, Apr 3, 2019 at 2:32 PM Michael Oleske <mole...@pivotal.io> > wrote: > > > > > I tend to import into Intellij the way you have described. I've never > > > used ./gradlew > > > idea to configure. > > > > > > -michael > > > > > > On Wed, Apr 3, 2019 at 2:24 PM Patrick Rhomberg <prhomb...@apache.org> > > > wrote: > > > > > > > I'm eyeballing the ide.gradle file we have and am wondering if it is > > > cruft > > > > from many iterations of both Gradle and IntelliJ/Eclipse ago. > > > > > > > > In my own IntelliJ workflow, I have always just asked IntelliJ to > open > > > the > > > > gradle project via the build.gradle itself, and it's easy to import > > other > > > > modules into my workspace via Import Module from Existing Sources... > > > I've > > > > never had to deal with running ./gradlew idea to configure a project > > IML > > > > which I needed to merge against another project file. > > > > > > > > Is this the workflow others are using? Or is the idea plugin here a > > > > hanger-on that should be removed as no longer necessary? > > > > > > > > Also, as an IntelliJ user, I have zero experience on how the workflow > > for > > > > Eclipse is similar or different. The closures in our ide.gradle > appear > > > to > > > > be similar, but I don't have the Eclipse-side context to confirm or > > deny > > > > that. > > > > > > > > Thanks in advance for any additional insight. > > > > > > > > Imagination is Change. > > > > ~Patrick > > > > > > > > > >
