Incompatible with Android plugin?

[wjwarren]

Hey,

When I try to use a dependency with the android plugin applied, the build fails. It only fails when the dependency doesn't exist in the local Maven repo.

build.gradle snippet:

android {
    ...

    dependencies {
        compile('org.batcha:dummy-project-a:4.2').ext.git = 'https://github.com/bat-cha/dummy-java-project-a.git'
    }
}

gradle output:

FAILURE: Build failed with an exception.

What went wrong:
Could not resolve all dependencies for configuration ':compile'.
Could not find group:org.batcha, module:dummy-project-a, version:4.2.
...

I ran the build script with the --info and --stackTrace flags, but they didn't seem to provide any more information on where exactly things went wrong. I can post the output later if you want.

Cheers,

Wijnand

PS: My build script dependency is to the locally built git-dependencies-0.1.jar that has #3 fixed.

[bat-cha]

Hey,

OK I've never used android plugin so far, I'll have a look on a dummy test project

I'll notifiy if I found something....

PS: I plan to deliver a v0.2 when I have a little bit more time that could be more verbose on where things can eventually go wrong (clone/pull from git repo or mavenLocal install....) and with more options (like refresh only if not found in mavenLocal or stuff like that... any ideas more than welcome)

[wjwarren]

No worries, let me know if you need some help setting up an Android test project.

I can't think of any other features that would be nice to have in a 0.2 release. If I come up with something, I'll open a new ticket 😉

[bat-cha]

ok I had a quick look and it seems that some assumptions of the git-dependencies plugin are no longer valid if you're applying the android plugin, I will get a closer look a little bit later and I'll keep you updated if I found a way to make it compatible

Cheers

[wjwarren]

Out of curiosity, what assumptions are you talking about? The "compileJava" task to be always part of a Gradle project?

[bat-cha]

Hello,

indeed this is a piece of the problem, I've added this task dependency to make sure the git resolution would happen before the compilation phase and was not yet able to found a generic way to express that... but I ve quickly tried yesterday to just remove this dependency and call the resolution task in the project itself, i.e. for android plugin as a dependency to assemble... but still the call would not succeed properly... I think i m not familiar enough with this plugin, in your config if you call the

resolveGitDependencies

task, is it working ? could share a properly initialized android project so that I can look at it ?

[wjwarren]

When I run gradle resolveGitDependencies on a build script with the Android plugin applied and configured, I get the following output:

Download http://repo1.maven.org/maven2/org/batcha/gradle/plugins/git-dependencies/0.1/git-dependenci
es-0.1.pom
Download http://repo1.maven.org/maven2/org/batcha/gradle/plugins/git-dependencies/0.1/git-dependenci
es-0.1.jar

FAILURE: Build failed with an exception.

What went wrong:
Could not resolve all dependencies for configuration ':compile'.
Could not find group:org.batcha, module:dummy-project-a, version:4.2.
Required by:
com.tuenti:android-messenger-new-integration:1.0

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more l
og output.

BUILD FAILED

Total time: 5.162 secs

I'll try and set up a dummy Android project somewhere later today.

[wjwarren]

Added a dummy Android project with Gradle here: https://github.com/wjwarren/dummy-android-gradle-project

[bat-cha]

Hi Wijnand,

Thanks for the precision on your problem and the android project,
I've removed the implicit dependency to a java plugin usage by using groovy afterEvaluate to execute the resolve git task ... I'll try with your project to see if it solves the issue with last version of the plugin (I've released the artifact to mavenCentral too, it take some times to get refreshed)

[bat-cha]

Hi Wijnand !

my script failed with unknown target android-16 probably because I still have a wrong setup but I've checked that the dummy-java project was effectivelly installed on local maven (even if i remove it... before)
could you please confirm ? (last version of plugin is also available on mavenCentral)

[wjwarren]

Hi, apologies for that. I forgot that you'd have to install an actual android API package as well.

From your Android SDK install folder run:

• SDK Manager.exe on Windows OR
• go to [android-sdk-root]\tools on Linux/Mac and run android sdk

This will start the Android SDK Manager and from there you can install API 16.

[wjwarren]

Hmm, just came across this little nugget on the Roadmap for the Android Gradle plugin:

Ability to manipulate tasks (per variant, per flavor, per build type, ...), ability to insert steps that impact input/output of default task

Might be an idea to wait on the 0.3 release of the plugin if this issue proves particularly difficult.

[bat-cha]

Hello Wijnand,

I've correctly set-up the dummy android project and there is indeed an incompatibility.
The plugin looks for the user defined dependencies configurations but if you put them under android namespace then it cannot access it "by default". I may find a way to fix this by specifying extra property for the plugin so that it can lookup for the configurations. I may be able to deliver this maybe before 0.3 release... I'll let you know

[wjwarren]

Cool, thanks! 😄

[wjwarren]

Added a work around to a branch of my dummy project. Have a look at the readme here: https://github.com/wjwarren/dummy-android-gradle-project/tree/work-around