Ivy has a specific URL resolver (https://ant.apache.org/ivy/history/latest-milestone/resolver/url.html). Each URL resolver can have its own pattern and even multiple patterns. Ivy is a very powerful dependency management, way more powerful, imo, than maven, but as such it can be confusing. I setup a custom set of build scripts in ant/ivy that we use cross project that basically do everything we need to do and allow us to have a common process. You can even make ivy deploy maven compatible poms, so that you get both maven and ivy support in your dependency repo. If you wanted to use ivy for publishing or retrieving dependencies, I would be glad to help/provide advice.
On Monday, October 20, 2014 6:50:13 AM UTC-7, Jens wrote: > > kind of a shame when you're bragging that you can adapt to any situation >> and use any kind of dependencies from file() to Maven and Ivy… just not >> plain HTTP URLs. >> > > Well Gradle allows you to set a custom repository pattern as it is based > on ivy. See section "51.6.9. More about Ivy resolvers" in > http://www.gradle.org/docs/current/userguide/dependency_management.html . > > Although the doc does not show it but maybe these patterns can be defined > per repository. That way we might be able to use the direct download links > of the svn repo at code.google.com. > > -- J. > > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/19c222f5-4439-4a52-aeeb-1eac3df795e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
