Menu
▾
▴
[ jEdit-devel ] [ jedit-Bugs-1314739 ] jEdit clashes with bsh.jar when installed in extensions.
|
From: SourceForge.net <no...@so...> - 2007-09-22 21:43:47
|
Bugs item #1314739, was opened at 2005-10-06 11:56 Message generated for change (Comment added) made by kpouer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1314739&group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: editor core Group: normal bug >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Matthieu Casanova (kpouer) Summary: jEdit clashes with bsh.jar when installed in extensions. Initial Comment: Moved file "bsh-2.0b4.jar" (BeanShell) to java extension folder. jEdit does not start up correctly anymore. Splash screen flashes up and dies. Want to use BeanShell in that way. It should be possible to have the BeanShell jar in the extension folder. Best wishes Thomas ---------------------------------------------------------------------- >Comment By: Matthieu Casanova (kpouer) Date: 2007-09-22 23:43 Message: Logged In: YES user_id=285591 Originator: NO Dupe of http://sourceforge.net/tracker/index.php?func=detail&aid=893349&group_id=588&atid=100588 ---------------------------------------------------------------------- Comment By: Blackwell (blackweli) Date: 2006-08-01 12:12 Message: Logged In: YES user_id=971109 Maybe the extensions mechanism should be "deactivated" for jEdit to avoid such screw ups. It may cause confusion by more advanced users that the stuff in lib/ext is not being available to jEdit, but it may be preferable to give jEdit its own "extensions" folder anyway. It says here (http://java.sun.com/j2se/1.5.0/docs/guide/extensions/spec.html): "Other locations for installed optional packages can be specified through the system property java.ext.dirs. This property specifies one or more directories to search for installed optional packages, each separated by File.pathSeparatorChar. The default setting for this property is the standard directory for installed optional packages indicated above." Maybe jEdit's commandline could be extended by -Djava.ext.dirs= by default, thus achieving the "deactivation" of the standard extension folder(s)? The lack of versioning makes the central extensions folder as bad a choice as the environment CLASSPATH when set globally. ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2006-08-01 11:58 Message: Logged In: YES user_id=285591 yes I did not read carefuly ---------------------------------------------------------------------- Comment By: Björn Kautler (vampire0) Date: 2006-08-01 11:23 Message: Logged In: YES user_id=918212 Who should put it in the plugins directory? I'm 99% sure he put it in his JAVA_HOME/lib/ext directory, I assume you know about it. At least that is the place where I would put it in. And he said he put it in his Java extensions folder, not in his plugins dir. ;-) ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2006-08-01 11:20 Message: Logged In: YES user_id=285591 I don't know if it can be fixed with priority in the classpath. But there is no reason to add it to the plugin directory. The better thing to do would be to use a standard beanshell distribution, but I don't know if it is possible. ---------------------------------------------------------------------- Comment By: Björn Kautler (vampire0) Date: 2006-08-01 10:24 Message: Logged In: YES user_id=918212 Even if it would solve the problem for him I don't think the bug should get closed. It is still inacceptable that jEdit wont start if BeanShell is somewhere in your class-path, because some ppl want to use BeanShell from other applications maybe, or from their own or whatever and want BeanShell in their classpath. ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2006-07-31 18:21 Message: Logged In: YES user_id=285591 Hi, this is impossible because beanshell has little modifications required by jEdit. But the next release 4.3pre6 will include Beanshell 2.0b4 You already can get the source and compile them from Subversion repository maybe it should fix your problem ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1314739&group_id=588 |