jastrachan | 5 Oct 17:34 2004
Picon

http://groovy.codehaus.org/Installing+Groovy

Agreed - we're just waiting on a classworlds release AFAIK.

On 5 Oct 2004, at 09:03, Laforge Guillaume wrote:
> Marc,
>
> As far as I remember, the bug was fixed in CVS HEAD (of classworlds), 
> but there were no released versions that we could depend on (defined 
> the right dependency). Thus I didn't re-enabled per default this 
> config param, to avoid this nasty NPE when the directory was not 
> created.
> I'll double check that.
> But once you have created the directory, it's fairly easy to change 
> the configuration file :-P
> It's not that a critical bug :-)))
>
>
> --
> Guillaume Laforge
> http://glaforge.free.fr/weblog
>
>
> -----Message d'origine-----
> De : Marc Hedlund [mailto:marc@...]
> Envoyé : mardi 5 octobre 2004 09:05
> À : user@...
> Objet : Re: [groovy-user] Should we add "~/.groovy/..." to
> http://groovy.codehaus.org/Installing+Groovy
>
> I've never understood why the bug is still open.  Can't whatever 
> mechanism
> creates the ~/.groovy dir also create the ~/.groovy/lib dir?  I realize
> you'd get an NPE if the user manually deleted the directory or if the
> directory couldn't be created, but isn't that currently true of the
> ~/.groovy dir itself?
>
>

James
-------
http://radio.weblogs.com/0112098/


Gmane