merscwog wrote: > > So, to deal with artifact location issues I utilize a couple of IVY > patterns: > > > '([organization]/)[module]/([revision]/)[type]s/[artifact](-[revision])(-[classifier]).[ext]' > > '([organization]/)[module]/([revision]/)[type]s/[artifact](-[classifier]).[ext]' > > '([organization]/)[module]/[type]s/[artifact](-[revision])(-[classifier]).[ext]' > > ... > You can utilize the recommended pattern, but that means "groovy" is the > organization, and "groovy-all" the module. Gradle contains all the > resolving power (and more) of IVY, but it tries hard to constrain its use > to Maven resolving patterns. >
Hello Spencer, That was really enlightening! I've made an item of it in Cookbook. Many thanks! Zsolt -- View this message in context: http://old.nabble.com/How-to-define-custom-remote-repo-for-client-dependency--tp27255683p27322140.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
