Re: [ jEdit-devel ] Another 4.2 plugin question

[Dale A. <da...@ge...>]

I was under the impression that the jEdit classloader recursed through 
subdirectories in the ${user.home)/.jedit.jars directory. It seems to me 
that this was the behaviour some time ago, like maybe in 3.x versions of 
jEdit. Apparently that's not true any longer (if it ever was, maybe I 
don't recall correctly), but it might be a nice behaviour for situations 
like this. In fact, it might be nice to have a subdirectory per plugin, 
with  a classloader per subdirectory. That would allow, for example, 
plugin A to use a different version of xalan.jar than plugin B, or even 
better, two different versions of the SAME plugin to be loaded at the 
same time.

Also, it turns out that all those jars aren't really necessary for Ant 
1.6. Just ant.jar and either optional.jar or ant-launcher.jar. It may 
happen that neither of the last two will be required by the time Ant 1.6 
is final.

Dale


Slava Pestov wrote:

>jEdit ignores JAR manifests... however putting the JAR files in the jars
>directory should not cause any problems except visual clutter.
>
>On Sun, 2003-09-28 at 22:07, Dave Landers wrote:
>  
>
>>On Sunday 28 September 2003 1:52 pm, Dale Anson wrote:
>>    
>>
>>>Ant 1.6 has split the base distribution from just 2 jar files (ant.jar
>>>and optional.jar) to about 30. In the past, on Linux I've make soft
>>>links to these 2 files in ${user.home}/.jedit/jars and on Windows I've
>>>copied the 2 file into the jars directory so I can use ant from within
>>>jEdit. Any recommendations on how to deal with this situation now that
>>>there are 30+ jar files for ant?
>>>      
>>>
>>Maybe you can make one (empty) jar which lists those 30 in it's manifest 
>>Class-Path.
>>    
>>