[GRADLE-2794] Incorrect module version in descriptor when combining dynamic version + POM-less module Created: 13/Jun/13 Updated: 10/Nov/13 Resolved: 10/Nov/13 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | 1.10-rc-1 |
Type: | Task | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 1 |
Description |
For my example, I have 2 artifacts that I depend on for compile and I am using gradle 1.5. Both artifacts are stored in our Artifactory server but only artifactA has a POM, artifactB does not. build.gradle dependencies { task dumpResolved << { Now, when I display dependencies, only the artifact with the POM, artifactA, displays the resolved version number: $ ./gradlew dependencies Similarly, my dumpResolved task only shows the fully resolved version number for artifactA: $ ./gradlew dumpResolved Why the difference in behaviour? Is there a way to make my dumpResolved task work without POMs? |
Comments |
Comment by Gradle Forums [ 13/Jun/13 ] |
I should add that when I run a build, both dependencies are resolved as I expect: $ ./gradlew build BUILD SUCCESSFUL |
Comment by Gradle Forums [ 13/Jun/13 ] |
Hi Chris |
Comment by Daz DeBoer [ 14/Jun/13 ] |
It looks like we should be using descriptor.getResolvedModuleRevisionId() instead of descriptor.getModuleRevisionId() [here](https://github.com/gradle/gradle/blob/master/subprojects/core-impl/src/main/groovy/org/gradle/api/internal/artifacts/ivyservice/ivyresolve/DefaultBuildableModuleVersionMetaDataResolveResult.java#L46). |