I see, thanks for that Adam. That worked perfectly.
The only issue left now is that it's not resolving when I set
latest.lastSuccessful as the version attribute. It is fine with a valid
version number in there.
Dependency config is:
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
compile group: "org", name: "bt521", version: "latest.lastSuccessful"
}
And in the logs:
10:35:55.361 [DEBUG]
[org.gradle.api.internal.artifacts.ivyservice.IvyLoggingAdaper] ivy: no
namespace defined: using system
10:35:55.361 [DEBUG]
[org.gradle.api.internal.artifacts.ivyservice.IvyLoggingAdaper]
tried
http://cmbuilddev/guestAuth/repository/download/bt521/[revision]/teamcity-ivy.xml
If I manually try
cmbuilddev/guestAuth/repository/download/bt521/latest.lastSuccessful/teamcity-ivy.xml
in a browser there is an ivy xml:
<ivy-module version="1.4">
<info organisation="org" module="bt521" revision="88192.lastSuccessful"/>
<publications>
<artifact name="JavaAppCommon-88192" type="jar" ext="jar"/>
<artifact name="reports" type="zip" ext="zip"/>
</publications>
</ivy-module>
And also a jar at
cmbuilddev/guestAuth/repository/download/bt521/latest.lastSuccessful/JavaAppCommon-88192.jar
Looking at the gradle logs it looks like it maybe isn't setting the revison
when its set to "latest.lastSuccessful" but does if its set to e.g. "88192".
I did see a jira on this issue but it was marked as resolved in a previous
milestone.
Any thoughts on this?
Thanks
Glyn
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Issues-using-TeamCity-Ivy-Repo-tp5134627p5136540.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
