To suppress generation of the WTP settings files, disable the corresponding tasks:
eclipseWtpComponent.enabled = false eclipseWtpFacet.enabled = false There are other things that the Eclipse plugin does for War projects: it adds build commands and natures to the .project file and some entry attributes to the .classpath file. Although you could undo this by reconfiguring the eclipseProject and EclipseClasspath tasks, it might be better to support your use case explicitly. Two solutions that come to mind are adding a configuration switch or moving the Eclipse WTP support into its own plugin. If you think this is a good idea, please submit an issue at http://issues.gradle.org. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradleware http://www.gradleware.com Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Eclipse-War-Plugin-Eclipse-without-WST-tooling-tp4345139p4345251.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
