[GRADLE-1113] IDE plugins should not be hardcoded in build Created: 13/Aug/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Tomek Kaczanowski Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Issue Links:
Supercedes
Superceded by GRADLE-997 Allow plugins to be applied from the ... Resolved

 Description   

One issue with IDE plugins (eclipse, idea, etc.) What I don't like about them is that they are hardcoded in build.gradle. This is annoying because it makes me modify build.gradle if I use different IDE than the author of the project. I suggest to "externalize" them so one could execute
gradle idea
or
gradle eclipse
without the need to modify build.gradle.

 Comments   
Comment by Hans Dockter [ 15/Aug/10 ]

Either GRADLE-997 will fix this issue or the future capability to support init scripts that are user and project specific.

Comment by Szczepan Faber [ 11/Mar/11 ]

Hey Tomasz

I actually find it quite nice that the IDE plugins are declared explicitly. The benefit is that when a rookie user runs 'gradle tasks' she will find out how to generate the IDE configs.

In general I find it quite cool that plugins are declared explicitly in gradle builds. This is an extra documentation nicely contributing to 'gradle tasks'. With a huge maven multi-module project we always found it hard to figure out how various devs are using various plugins. Usually teams ended up with a bunch .bat/.sh files that executed various goals/plugins (blah...)

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:47:14 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.