I am trying to adopt Gradle for builds and Artifactory for dependency
management (using the plugin). It seems like I am really close to getting
it working but am stuck (again).
I am using the standard libs-release virtual repository for dependency
resolution, and the remote dependencies resolved through it seem to be in
Maven form - directories without dots and a POM. For my local repositories
I am trying to use the Ivy form since I have no investment in or desire to
embrace Maven.
Is this possible and reasonable? It seems that when if I include an ivy
definition for the repository in the plugin it does not find the Maven
artifacts.
resolve {
repository {
repoKey = 'libs-release'
ivy {
ivyLayout = '[organization]/[module]/ivy-[revision].xml'
artifactLayout =
'[organization]/[module]/[revision]/[module]-[revision](-[classifier]).[ext]'
mavenCompatible = false (or true)
}
}
}
If I remove the ivy closure then I find the Maven artifacts but not the
artifacts in my local repositories.
Thanks for any help.
-Andy
"How *reliable* [is he]? How shallow is the ocean? How cold is the sun?"
-Douglas Adams (Arthur Dent) ------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
