[GRADLE-2839] Wildcard configuration mapping in Ivy dependency definition mapped to private configuration of target module Created: 16/Jul/13  Updated: 18/Jul/13  Resolved: 18/Jul/13

Status: Resolved
Project: Gradle
Affects Version/s: 1.7-rc-1
Fix Version/s: 1.7-rc-2

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Fixed Votes: 0

Attachments: Zip Archive repro.zip    


See the attached sample project. The resolution yields different results with Gradle 1.7-rc-1 (fails) and 1.6 (passes).

It appears that when ivy descriptor defines the test dependencies this way:

<dependency conf="test-&gt;runtime(*),master(*)" force="true" name="mockito-core" org="org.mockito" rev="1.8.5" />

then those are recursed during resolution. In 1.6- they were not recursed (it's somewhat expected because those are test dependencies.

This might be a bug (needs fixing) or a feature (needs documentation, user-oriented justification and steps to fix the problem if it happens in user's build).

Comment by Adam Murdoch [ 18/Jul/13 ]

In 1.6, the wildcard configuration mapping is mapped to all public configurations of the target module. In 1.7-rc-1, the wildcard configuration mapping is mapped to all configurations of the target module, including private configurations.

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