score:0

sadly this is a bug with gradle; see the open github issue.

score:0

one (workaround) solution is to use different groups for the subprojects:

// root/foo/build.gradle
subprojects {
    group = 'org.example.foo'
}

// root/bar/build.gradle
subprojects {
    group = 'org.example.bar'
}

score:1

so far, i've only been working with "single dir level" multiprojects; for that scenario, there are several ways to fix it:

  • if you want to fix it for eclipse only and if you're using the "import gradle project" wizard, you might want to set the "use hierarchical project names" check box. not sure how it behaves in your case (double dir level)
  • next one can hopefully help you out: how to rename the project in gradle instead of using folder name?. probably with some extra investigation for your double dir level. it will also change the gradle project names btw
  • and indeed, the eclipse plugin also provides means to change project names, haven't used it myself though...

Related Query

More Query from same tag