Posterous groovy bug due to bad HTTP Builder dependency.

I allow myself to post this on my posterous blog, as a follow-up to my message concerning the availability of the script.

 

2010/4/7 E*** B******* L*** <******>
>

> Hi Nicolas,

 

Hi, E***

>
> I just tried to use your script on my Ubuntu machine but it can not find the following class:

>

> unable to resolve class groovyx.net.http.URIBuilder
>
> Can you maybe tell me how I can install this class to be available in Java? I found it with Google but don’t know how to make it available for your script / the JVM.

 

Will have to dive deep in groovy internals for that, I hope you’ll understand the whole.

 

The posterous groovy script, for getting all the entries, make use of the groovy version of HTTP Builder : http://groovy.codehaus.org/modules/http-builder/

This dependency is resolved using groovy specific mechanism : grape. You can see the @Grab instruction for HTTP builder at line 289 :

 

@Grab(group=’org.codehaus.groovy.modules.http-builder’, module=’http-builder’, version=’0.5.0-RC2′)

 

I’ll make the guess you don’t know at all groovy grape. It’s a kind of « live » version of Ruby Gems : your program dependencies are expressed using annotations in the body of your program. Once run by the groovy runtime, each time one of these annotations is encountered, grape checks if the dependency is already known (that’s to say already present as ~/.groovy/grapes/ »group »/ »module »/jars/ »module.version »). If not, it is downloaded and its checksum is verified.

 

Currently, the HTTP Builder website says on its front page

 

So I had a couple people mention that they had trouble using Grape to download RC3 due to a bad checksum on the POM file. I tried re-deploying it, (thinking it was a bad upload) and now I’m getting a _bunch_ of people saying they can’t download it!

As a work-around, please add the following line to ~/.groovy/grapeConfig.xml: <property name= »ivy.checksums » value= » »/>. This should allow Grape to ignore the checksum and download the file, until I’ve got the checksum problem resolved. Stay tuned!

 

May I suggest you to do the mentionned operation ? Notice however this operation seems to disable checksum verification on all jars, not only on HTTBuilder one. So, don’t forget to remvoe that line once the application is run successfully !
>

> Greetings from Germany,
>

Thanks for the feedback !

Laisser un commentaire

Entrez vos coordonnées ci-dessous ou cliquez sur une icône pour vous connecter:

Logo WordPress.com

Vous commentez à l'aide de votre compte WordPress.com. Déconnexion / Changer )

Image Twitter

Vous commentez à l'aide de votre compte Twitter. Déconnexion / Changer )

Photo Facebook

Vous commentez à l'aide de votre compte Facebook. Déconnexion / Changer )

Photo Google+

Vous commentez à l'aide de votre compte Google+. Déconnexion / Changer )

Connexion à %s