Ah. Got it. So there is a distinction you're concerned about. I'd think you could somehow pipe configurations.compile into configurations.archives and then use the standard install provided by the Maven plugin. Although that'll probably give you Pom files, which aren't exactly Ivy files.
~~ Robert. On Thu, Apr 26, 2012 at 2:49 PM, Roger Studner <rstud...@gmail.com> wrote: > Well, the issue is making sure the proper artifacts & all depedencies are > pulled down.. and then the correct ivys/*.xml files are created/pushed for > each artifact. > > wget (CURL!) is brilliant.. but doesn't solve the issue (even 1%) here. > > Roger > > On Apr 26, 2012, at 11:21 AM, Robert Fischer wrote: > >> Isn't this why a loving and benevolent God invented wget? Or is there >> some inconsistency that I'm not aware of? >> >> ~~ Robert. >> >> >> On Thu, Apr 26, 2012 at 11:15 AM, Roger Studner <rstud...@gmail.com> wrote: >>> I have an ivy repo and use a sort of ugly/hackish ant file to pull things >>> from maven central and then publish them to my own ivy repo >>> >>> I'd like to do this with gradle, but have no idea where to start.. >>> obviously I can pull down the dependencies/comppile etc etc with gradle.. >>> i've just never tried to make a task to "pull something down and then >>> publish it to another repo" >>> >>> anyone :)? >>> >>> Thanks, >>> Roger >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
