[GRADLE-3496] Maven POM conversion dependency de-duplication should choose the higher version when multiple versions have the same priority Created: 05/Jul/16 Updated: 07/Jul/16 Resolved: 07/Jul/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | 2.14.1-rc-2 |
| Type: | Bug | ||
| Reporter: | Paul Merlin | Assignee: | Paul Merlin |
| Resolution: | Fixed | Votes: | 0 |
| Known Issue Of: |
| Description |
|
When two dependencies with differeent versions are declared with the same configuration/priority, mapping to Maven POM use the first declared dependency. e.g.
dependencies {
compile 'com.acme.example:1.0'
compile 'com.acme.example:2.0'
}
This snippet will produce a POM with a dependency on 'com.acme:example:1.0'. It should elect the one with the higher version instead: 'com.acme:example:2.0'. |