Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-3118

Defined dependency artifact not used when resolving a module with no metadata file

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1-rc-1
    • Known Issue Of:
      2.0

      Description

      This is a regression in dependency resolution in Gradle 2.0. The issue occurs when there is no ivy.xml for a module, and the dependency declares and artifact where the artifact name does not match the module name.

      When trying to locate the module metadata, Gradle 2.0 will search first for the ivy.xml file for the module, then the default 'jar' artifact. Instead Gradle should be searching for the declared artifact if the ivy.xml file is not found.

        Attachments

          Activity

            People

            Assignee:
            daz Daz DeBoer
            Reporter:
            forums Gradle Forums
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: