[GRADLE-3041] Request is issued for jar artifact when Maven dependency has packaging of type POM Created: 05/Mar/14 Updated: 06/Apr/14 Resolved: 06/Apr/14 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.11 |
| Fix Version/s: | 1.12-rc-1 |
| Type: | Bug | ||
| Reporter: | Luke Daley | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Description |
|
This can be problematic when the jar artifact does not exist, depending on the configuration of the server. For example, artifactory can be configured to “hide the existence of non existing artifacts” for password protected repositories. In this case, the server will return a HTTP 403 when Gradle requests the jar, which will fail the build. |
| Comments |
| Comment by Santoash Cuddalore Rajaram [ 28/Mar/14 ] |
|
http://forums.gradle.org/gradle/topics/gradle_throws_an_error_trying_to_find_a_jar_for_a_parent_pom |
| Comment by Adam Murdoch [ 06/Apr/14 ] |
|
This is by design, and exactly what Maven does. For this issue we changed the implementation to avoid checking for the jar when the pom is used as a parent pom, but not when the module is used as a dependency. |