[GRADLE-2296] Order of Repository Declarations can cause resolution issues Created: 12/May/12  Updated: 12/Feb/16  Resolved: 12/Feb/16

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-3
Fix Version/s: None

Type: Bug
Reporter: Ken Sipe Assignee: Unassigned
Resolution: Fixed Votes: 0


When resolving a jms jar, the order of repo declaration matters. I have an example project on github with a working and failing build file checked in. the readme.md provides more detail.

In the end, the jms-1.1.jar isn't resolved if mavenCentral() is defined first. It is if the repo with jms is provided first.


Comment by Ken Sipe [ 12/May/12 ]

I should have mentioned that this could be related to http://issues.gradle.org/browse/GRADLE-2100
however this says it was resolved several versions ago, so I assume it is new or it has resurfaced.

Comment by Mark Vieira (Inactive) [ 12/Feb/16 ]

Tested the submitted example with Gradle 2.11 and dependencies (including JMS) are successfully resolved.

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