A while back (a few versions ago), we had an issue with projects with the
same name (last value in the path). I asked on the gradle forum and they
don't have any restriction for unique name. To get around it we did the
project renaming trick
include "someUniqueName"
project(":someUniqueName").path = path/with/nonunique/name
This worked for a time, but recently I wanted to try out android studio and
apparently android studio doesn't play nice with moved paths :/
So i tried setting them back to standard includes, with the non-unique
names. This ended up with a project that depended on a library with the
same name, and we get the "depends on libraries but is not a library" error
An example of a project structure that would run into this:
libraries/feature1/android
libraries/feature2/android
apps/simpleApp/android
The errors print out what looks like <package>.<name> when identifying
themselves instead of using the guaranteed unique path.
My best guess at the moment is that the android plugin has a data structure
somewhere which is keying off name (or <package>.<name>) instead of
path....?
Is having unique names (which maps out to unique project directories,
wherever they appear in your folder hierarchy) an intended precondition for
the android plugin?
- Ben
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
