Thanks Frederic, but I am still not getting what I expect.

Just to be sure I am following your suggestion, you intended that I go 
into the Admin tab, Repositories, and edit the libs-release virtual 
repository changing the advanced setting "Repository Layout" to 
"gradle-default", correct?

When I do this the remote repositories do not seem to bring down the POMs 
and so it seems I lose the dependencies indicated therein. It also puts 
"!" in front of all of the "Resolved Repositories" for libs-release 
indicating "not all tokens can be mapped between the layout of this 
virtual repository and the marked repository. Path translations may not 
work as expected."

Thanks again.



Frederic Simon <[email protected]> 
07/17/2011 05:47 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: [Artifactory-users] Mixing Ivy and Maven repositories with  Gradle






What you are trying to do is perfectly reasonable and a good practice :)
I think the part you are missing is a good configuration of repository 
layouts in Artifactory.
It looks like the layout you are using for libs-release is the gradle 
default. Just set this on the virtual repo configuration and it should 
work.
You'll need to make sure your local repositories have also the good layout 
configured.

On Thu, Jul 14, 2011 at 6:52 PM, Andy Goodspeed <[email protected]> 
wrote:
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) 

------------------------------------------------------------------------------
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that
has been used successfully in hundreds of IBM storage optimization engage-
ments, worldwide.  Store less, Store more with what you own, Move data to 
the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to