Jared D. Cottrell wrote: > > As best I can tell, IDEA modules get there names from the name of the .iml > file that defines them. >
This is also my understanding. Jared D. Cottrell wrote: > > Whatever generates IDEA module dependencies is not sensitive to changes to > the outputFile property even though some changes may result in module name > changes > I consider this a bug. Please submit an issue for it. The IdeaProject task gets this right. Jared D. Cottrell wrote: > > Anyone know of a solution? > Currently I can see two workarounds: 1. Make the Gradle project names unique (this can be done without changing the names of the project directories) 2. Post-process the module dependencies with the ideaModule.withXml() hook (the user guide has more information on this) Other improvements we could make: - Add an IdeaModule.moduleName property to make it unnecessary to fiddle with the outputFile property for changing the module name - Base default module name on the Gradle project path rather than on its name What do you think? -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradle Inc. http://www.gradle.biz Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Dealing-With-IDEA-Module-Name-Conflicts-tp3401692p3401830.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
