René Gröschke wrote: > > Hi tinca, > I think the easiest way to get the groovy-all-1.6-RC-1.jar resolved in > your setup, is to add a second pattern like this: > > http://our.www.server/librepo/[organisation]/[revision]/[module]-[revision].[ext] > > > this adds the revision to the jar file name. > > This adds the revision to the jar file name. Now you should be able to > resolve groovy via groovy:groovy-all:1.6-RC-1 > ... >
Hello René, Yes, I can do it. What to do, however, when some of the jars has revision info and some not at the same time? Is there a regexp-like feature for defining that mix? Nevertheless, it is not that big problem. If nothing else, when no revision info is available an "unknown" revision tag can be used. Thanks! Zsolt -- View this message in context: http://old.nabble.com/How-to-define-custom-remote-repo-for-client-dependency--tp27255683p27303164.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
