Wednesday, June 11, 2008

Well, that's so NOT groovy

So, I was working on my summer of code project, and I have groovy code along side my java code. I needed to add the groovyc ant task. While i assumed that groovy-all-1.5.6.jar, (note the all) contained everything that was needed, guess what folks, it doesn't! I spent the greater part of the evening tracking down this problem, and then i added the ant-1.7.0.jar and ant-launcher.jar jars, after that suddenly everything worked. That begs the question though, why isn't everything included in the groovy jar?

The problem: NoClassDefFoundError on MatchingTask class.


I figured I would put this out there for others in case they too experience what I did.

2 comments:

Artur Karazniewicz said...

Rob,

Ain't *all* in groovy means - all You need at runtime, not necessarily *all* You need at compile time????

I would be completely disgusted if groovy developers put half of the ant in it...

Artur

Robert O'Connor said...

They appear to have done so.

I expected when i create the taskdef, for it to work, not crap out. Oddly enough, I didn't have to do anything else, just include the ant-*.jar and ant-launcher jar :)

No hard feelings to the groovy devs :)

They *DID* create an awesome language :D