tag:blogger.com,1999:blog-7369917695391880645.post5370183648113334338..comments2024-03-27T09:23:56.205-07:00Comments on Online Village: Production Groovy Part I: The trouble with GrapeGeoff Flarityhttp://www.blogger.com/profile/01239564240519036467noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7369917695391880645.post-52124254696343587392009-12-17T05:54:54.222-08:002009-12-17T05:54:54.222-08:00This comment has been removed by the author.Geoff Flarityhttps://www.blogger.com/profile/01239564240519036467noreply@blogger.comtag:blogger.com,1999:blog-7369917695391880645.post-49327259256412174652009-12-17T05:54:53.759-08:002009-12-17T05:54:53.759-08:00The problem with just modifying the grapeConfig.xm...The problem with just modifying the grapeConfig.xml in the ~/.groovy directory is that it only affects the one user. If there are say 5 users who can each utilize groovy then on deploymeny their environments all need to be modified. <br /><br />I wasn't aware of GrabResolver though. Very handy.<br /><br />Thanks!Geoff Flarityhttps://www.blogger.com/profile/01239564240519036467noreply@blogger.comtag:blogger.com,1999:blog-7369917695391880645.post-23650949318103616782009-12-17T02:13:17.735-08:002009-12-17T02:13:17.735-08:00In Groovy 1.7, you'll be able to use the @Grab...In Groovy 1.7, you'll be able to use the @GrabResolver annotation as well to explicitely search a repository.<br /><br />Also, you don't need rebuilding Groovy at all, you just need to update your user home 's ./groovy/grapeConfig.xml file to specify the repos you want to contact. <br /><br />Some examples of the configuration changes are also available in the <a href="http://groovy.codehaus.org/Grape" rel="nofollow">grape documentation</a>, near the middle.Guillaume Laforgehttps://www.blogger.com/profile/03993980328127368671noreply@blogger.com