Robert,
thanks for your comment. One reason for older versions is that they are tested in the environment they being used. It takes a little while before newer versions can be tested. We don't just always jump on the newest shiniest versions of things. Where jEdit is concerned there is a reliance on the Java installation which also has to be tested first and in a large organization with strict test and rollout procedures this can take a VERY long time! We've seen java updates break all kinds of other business processes, particularly with respect to Oracle database connections so there is a certain paranoia about this stuff.

It turns out that there is indeed a difference between the working and the non-working setups. In the working setups, the Templates plugin version is 4.1.0 -- this isn't even available now so newer installs are getting version 3.3.0 which seems to break with jEdit 4.3pre9.

• 3.3.0 for jEdit >= 4.2pre3 (August 16, 2003)
• 4.1.1 for jEdit >= 4.3pre12 (February 12, 2008)

Normally we would have kept plugin installs available locally for just this reason and the fact that the jEdit downloads have been unavailable from time to time but this one got missed.

I finally got the Template plugin to work by first upgrading to JEDIT 4.3pre13. Even then the Plugin Manager wanted to install Templates 3.3.0. Only by manually copying in the 4.1.1 jar file did templates finally work.

The problem now is that Console (neither 4.2.6.5 nor 4.1.2) won't work -- which is an even bigger problem than Templates not working. I wonder if this relates to the Beanshell changes?

3:54:31 PM [error] ErrorListDialog$ErrorEntry: \\PARADE\GAMCLEOD$\PROFILE\.jedit\jars\Console.jar:
3:54:31 PM [error] ErrorListDialog$ErrorEntry: Cannot start: java.lang.NoSuchMethodError: org.gjt.sp.jedit.BeanShell.getNameSpace()Lbsh/NameSpace;
3:54:31 PM [error] ErrorListDialog$ErrorEntry: Try updating to a newer version of the plugin.
3:54:31 PM [debug] EditBus: PluginUpdate[what=ACTIVATED,exit=false,source=\\PARADE\GAMCLEOD$\PROFILE\.jedit\jars\Console.jar,class=console.ConsolePlugin]
3:54:31 PM [debug] PluginJAR: Opening \\PARADE\GAMCLEOD$\PROFILE\.jedit\jars\Console.jar

The error message says "Try updating to a newer version of the plugin". Why don't You do it?

I've installed Console plugin 4.3.6. So, i think, the error must be related to the Beanshell changes.

Robert

If You have a working jEdit installation with all plugins You want - it's all You need.

jEdit doesn't use the windows registry (except for the one context menu item). There are exactly two directories that jEdit is using for itself: the program directory and the settings directory (%USERPROFILE%\.jedit\).

Just copy them if You want to clone a whole jedit installation.

If You want to get a plugin from another jedit installation: Just copy the plugin's jar file and - if there are any- other jars it depends on. For the templates plugin that are:
templates.jar
velocity-??.jar
JakartaCommons.jar
(maybe other *-commons-*.jar)

Robert