[GRADLE-2471] Test Dependency not resolved if Java Plugin is not applied first and the dependency is alphabetically first Created: 10/Sep/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.1, 1.2-rc-1
Fix Version/s: None

Type: Bug
Reporter: Rob Winch Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: Zip Archive gradle-testdep-bug.zip    

 Description   

I found a strange issue that may be related to GRADLE-2470 when using the following build.gradle

subprojects {
//    apply plugin: 'java'
}
configure(allprojects) {
    apply plugin: 'java'

    repositories {
        mavenCentral()
    }

    dependencies {
        testCompile "junit:junit:4.10"

        if(project.name != 'core' && project.name != project.rootProject.name) {
            testCompile project(':core').sourceSets.test.output
        }
    }
}

The test dependency is not found in a project named another, but is found in project named other. Despite the fact that project "another" is identical to "other". The error appears to be related the fact that another is alphabetically before core, but other is alphabetically after core.

Similar to GRADLE-2470 the issue can be fixed by applying the Java Plugin first as instructed in the comments of the build.gradle.

 Comments   
Comment by Benjamin Muschko [ 15/Nov/16 ]

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!

Comment by Benjamin Muschko [ 10/Feb/17 ]

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.

Generated at Wed Jun 30 12:22:49 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.