|Russel Winder||Apr 25, 2008 3:15 am|
|Jochen Theodorou||Apr 25, 2008 3:29 am|
|Russel Winder||Apr 26, 2008 12:40 am|
|Paul King||Apr 26, 2008 2:27 am|
|Paul King||Apr 26, 2008 2:47 am|
|Russel Winder||Apr 26, 2008 3:24 am|
|Jochen Theodorou||Apr 26, 2008 4:35 am|
|Russel Winder||Apr 26, 2008 4:46 am|
|Russel Winder||Apr 26, 2008 5:02 am|
|Jochen Theodorou||Apr 26, 2008 5:24 am|
|Paul King||Apr 26, 2008 5:33 pm|
|Jochen Theodorou||Apr 27, 2008 2:10 am|
|Paul King||Apr 27, 2008 4:26 am|
|Russel Winder||Apr 27, 2008 4:30 am|
|Jochen Theodorou||Apr 27, 2008 4:53 am|
|Russel Winder||Apr 27, 2008 5:55 am|
|Jochen Theodorou||Apr 27, 2008 6:24 am|
|Russel Winder||Apr 27, 2008 10:43 am|
|Jochen Theodorou||Apr 27, 2008 12:02 pm|
|Paul King||Apr 27, 2008 4:11 pm|
|Russel Winder||May 1, 2008 2:16 am|
|Jochen Theodorou||May 2, 2008 10:02 am|
|Russel Winder||May 2, 2008 12:07 pm|
|Jochen Theodorou||May 2, 2008 12:51 pm|
|Subject:||Re: [groovy-dev] [Fwd: XML class lookup problem in Gant]|
|From:||Jochen Theodorou (blac...@gmx.org)|
|Date:||Apr 27, 2008 6:24:28 am|
Russel Winder schrieb:
On Sun, 2008-04-27 at 13:54 +0200, Jochen Theodorou wrote:
I am thinking about extending the config file, to allow to place knnown trouble makers and let RootLoader load them in the way I showed in my second patch. That would let the user allow to get a little control and us providing working workarounds.
Although this would obviate the worst excesses of having to drop superfluous copies of jars into $GROOVY_HOME, but is it still a workaround rather than a solution? The problem is going to arise when people who are not high quality programmers have to deal with all this.
well.. it seems to work..I think it is a bit of a hack than a clean solution, so I call it workaround. I am just carful with what I name solution and what not ;)
as you can see from the config file, the entries for both are equal. The only thing is that $GROOVY_HOME/lib is before ~/.groovy/lib. That will also influence the order in which the jars are added. so maybe you should try switching these two. It is quite poissible, that then a different xml implementation will be taken, because thee can be only one class of a certain name in a single loader and I guess URLClassLoader still picks the wrong one... so just reverseing the order should do
I would have thought that ~/.groovy/lib should have higher priority than $GROOVY_HOME/lib.
well.. you should try that first I think. If it doesnot work, then there is no point in doing so. Also the order in which the jars are handled by the URLClassloader is not really specified. I guess most use the latest jar first, but I am not sure this is always the case, nor is there any base for assuming so. Well, none that I am aware of at last.
If this means having a specific order then I would argue the default order should ensure that jars in ~/.groovy/lib are searched before those in $GROOVY_HOME.
true... my prefered versions is that here is no need for any ordering... ah, one can dream, can't he?
jars provided on the command line should of course have even higher priority.
that's already the case
I also need to have jars in ~/.ant/lib and ~/.gant/lib included. I think they are but not in the right way to get round the XML classes problem.
extend the conf file?
The conf file is part of the Groovy installation and not a user controllable thing -- unless a config file in ~/.groovy is used if it exists and the one in $GROOVY_HOME/conf is only used if the one ~/.groovy doesn't exist.
but you can provide your own config file for grails. If the property groovy.starter.conf is set to your own configuration, then this one used and not the one installed.Ah, no wait... I am mistaken here.. the property can be used if no configuration is given at the command line, but the command line has preference. Maybe I should change that.
well the RootLoder in combination with the settings used to run a script from the command line is not the environment suitable for being used in ant, where ant provides the parent classloader... but is this even the case? I had the impression, that gant is started from the command line and not by ant. In that case the assumptions itself are not really a problem. Having two Node classes in different loaders still is a problem
Gant can be started either from the command line or from a Java or Groovy script, or via Ant.
I think the multiple classloaders is at the heart of this problem.
and in which cases is the LinkageError? All of them?
--------------------------------------------------------------------- To unsubscribe from this list, please visit: