Closed RichardGuion closed 10 years ago
thanks for your simple example and i found the pitfall. In alphabetical order upper case letter comes before of lower case letters. So your UnitTest-module was just in front and not the app-module
I also updated it here with extra tips https://github.com/nenick/android-gradle-template/wiki/Renaming-project-modules
I finally figured this out - thanks to your working example I could compare against the --debug log on gradlew.
Your project mysteriously builds the projects in order:
Included projects: [root project 'android-gradle-template', project ':AndroidSample', project ':ComponentTestsRobolectric', project ':GenerateDatabaseContent', project ':UnitTestsRobolectric']
In other words - it compiles the main AndroidSample first; the order is alphabetical!
LOL - you answered me at the same time I found the answer! Thank you for your effort!
I have learned a lot by looking at this code. I even put in some debug statements in the plugin.
good to know that you are searching by self for your issues ;)
(when you feel, your issues are not more present, then please close them)
Hi - trying to follow your pattern of sub directories with an existing project. I have tried to replicate what you have almost exactly. Yet when I build I get this error:
It thinks that the main Android application doesn't have the android plugin applied, yet it does! Any idea what I am doing wrong?
The directory structure looks like:
Settings.gradle:
My build.gradle in the top most folder has the same settings as yours, except I use build tools 19.0.1.
app/build.gradle has this at top:
UnitTestsRobolectric/build.gradle has this:
I see this code in the plugin source so I know it must have found the gradle file for the app, but I can't explain why it doesn't see the android plugin applied!