[GRADLE-2337] idea plugin uses javaplugin instead of javabaseplugin for Java projects Created: 05/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-3
Fix Version/s: None

Type: Bug
Reporter: Emil Sit Assignee: Unassigned
Resolution: Won't Fix Votes: 1


From http://forums.gradle.org/gradle/topics/idea_vs_eclipse_behavior_for_sourcesets

If a project does not apply the java plugin, but it does apply java-base and manually creates a sourceSet called main and manually adds a bunch of srcDirs to it...

  • gradle eclipse, Gradle generates a .classpath file that contains all the srcDirs.
  • gradle idea, Gradle generates a module file that has no source dirs.

I think this is because the Idea plugin only applies withType(JavaPlugin) whereas the Eclipse plugin uses withType(JavaBasePlugin).

It's believed that this is an inaccuracy, and should be changed to match the Eclipse plugin.

Comment by Emil Sit [ 05/Jun/12 ]

A work-around is to use "gradle eclipse" and then use IntelliJ's support importing Eclipse projects.

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 12:19:10 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.