Hi David. I'm currently investigating a similar issue, and this definitely sounds like a bug.

Can you please:

• Check if this error persists with Gradle 1.11
• Send the output when running the build with '--debug' (use Gist)

That would help a lot in tracking this down.

Hi,

I have the same issue since Gradle 1.10. I tested today with the new 1.12-RC1 and it still exists.

In my case it always occurs if I use ClientModule in combination with '1.+' version syntax.

The following build.gradle file will run into this issue (the project contains the file dependency lib/commons-email-1.2.jar). Gist containing debug output: [1]https://gist.github.com/samstgt/10927441

apply plugin: 'java'

repositories {
flatDir name: 'localRepository', dirs: "$projectDir/lib"
}

dependencies {
compile module(":commons-email:1.+") {}
}

Replacing
compile module(":commons-email:1.+") {}
with
compile ":commons-email:1.+"
results in a successful build. Gist containing debug output: [2]https://gist.github.com/samstgt/10927863

Also replacing
compile module(":commons-email:1.+") {}
with
compile module(":commons-email:1.2") {}
results in a successful build. Gist containing debug output: [3]https://gist.github.com/samstgt/10928457

I hope this will help fixing the problem.
----------------------------------------------------------------------------------------
[1] https://gist.github.com/samstgt/10927441
[2] https://gist.github.com/samstgt/10927863
[3] https://gist.github.com/samstgt/10928457

Thanks for creating this simple reproducable sample. Does the problem still exists when running with --refresh-dependencies. I'll try to reproduce this on my local box later and come back to you

cheers,
rene

Tested with --refresh-dependencies and the problem still exists.
[1]https://gist.github.com/samstgt/10959231

If you need me to test something else, let me know.
----------------------------------------------------------------------------------------
[1] https://gist.github.com/samstgt/10959231

Retested with 1.12-rc2 and problem still exists.

[1]https://gist.github.com/samstgt/11259324
----------------------------------------------------------------------------------------
[1] https://gist.github.com/samstgt/11259324

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.