gradle tooling must not always add java nature about eclipse-integration-gradle HOT 1 OPEN

Yes, indeed. It’s on our “ToDo” list for Gradle Eclipse integration.

Cheers,
Alex

On Jun 7, 2014, at 3:13, zyro [email protected] wrote:

the gradle tooling seems to always add a java nature to the project when doing a "refresh all". no matter if the gradle build actually adds a java nature or if dependency mgmt is enbaled or not.

this is not always a good approach: e.g. i got an ear project which must not have a java nature or else i am not able to deploy it to the application server. i explicitly removed that nature in my gradle build (or rather the project does not even have the java plugin applied) but refresh all keeps re-adding it.

looks like this could be the code.
https://github.com/spring-projects/eclipse-integration-gradle/blob/master/org.springsource.ide.eclipse.gradle.core/src/org/springsource/ide/eclipse/gradle/core/wizards/GradleImportOperation.java#L419

the same happens on "convert to gradle project", i think:
https://github.com/spring-projects/eclipse-integration-gradle/blob/master/org.springsource.ide.eclipse.gradle.core/src/org/springsource/ide/eclipse/gradle/core/GradleProject.java#L690

would be cool if the gradle tooling supports non-java gradle projects as well.

thanks, zyro

—
Reply to this email directly or view it on GitHub.

from eclipse-integration-gradle.