Recent changes to 1924: XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory

#1924 XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory

Alan Ezust — Sat, 02 Sep 2023 19:16:02 -0000

TemplatesPlugin.getTemplateDir() gives me undefined variable or classname.
templates.TemplatesPlugin.getTemplateDir() gives me the right thing at the moment:
/home/ezust/.jedit/templates/

#1924 XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory

Eric Le Lay — Sat, 02 Sep 2023 13:44:45 -0000

These are the templates, not schema info.
This happens if for whatever reason TemplatesPlugin.getTemplateDir() returns null or empty string.
Please can you check in beanshell? I've modified the code already[1] to not install templates when the Templates directory looks bad.

[1] https://gitlab.com/jedit/plugins/xml/-/merge_requests/2

#1924 XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory

Eric Le Lay — Sat, 02 Sep 2023 13:28:44 -0000

assigned_to: Eric Le Lay

#1924 XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory

Alan Ezust — Tue, 08 Aug 2023 15:50:07 -0000

summary: XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's startup folder --> XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory
Description has changed:

Diff:

--- old
+++ new
@@ -1,4 +1,3 @@
-
 I use XMLPlugin to edit docbook files, such as jEdit&#39;s documentation. Editing a file means that schema info is cached in an XMLPlugin directory in whichever directory I started jedit from. So I got lots of directories that look like this:

 /home/ezust/XMLPlugin/docbook-article-4.4.vm

Group: -->

XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's startup folder

Alan Ezust — Tue, 08 Aug 2023 15:47:47 -0000

I use XMLPlugin to edit docbook files, such as jEdit's documentation. Editing a file means that schema info is cached in an XMLPlugin directory in whichever directory I started jedit from. So I got lots of directories that look like this:

/home/ezust/XMLPlugin/docbook-article-4.4.vm
/home/ezust/XMLPlugin/html-frameset.vm
/home/ezust/XMLPlugin/html-strict.vm
/home/ezust/XMLPlugin/html-transitional.vm
/home/ezust/XMLPlugin/schema-relax-ng.vm
/home/ezust/XMLPlugin/schema-xsd.vm
/home/ezust/XMLPlugin/xhtml-frameset.vm
/home/ezust/XMLPlugin/xhtml-strict.vm
/home/ezust/XMLPlugin/xhtml-transitional.vm
/home/ezust/XMLPlugin/xslt-1.0.vm
/home/ezust/XMLPlugin/xslt-2.0.vm

jEdit 5.6.0
XMLPlugin 3.0.8
OpenJdk19, Ubuntu Linux 23.04

XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory

Alan Ezust — Tue, 08 Aug 2023 15:47:47 -0000

Ticket 1924 has been modified: XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory
Edited By: Alan Ezust (ezust)
Summary updated: 'XMLPlugin leaves behind an "XMLPlugin" directory in jEdit\'s startup folder' => 'XMLPlugin leaves behind an "XMLPlugin" directory in jEdit\'s working directory'
Description updated:
--- description-old

+++ description-new

@@ -1,4 +1,3 @@

-
I use XMLPlugin to edit docbook files, such as jEdit's documentation. Editing a file means that schema info is cached in an XMLPlugin directory in whichever directory I started jedit from. So I got lots of directories that look like this:

/home/ezust/XMLPlugin/docbook-article-4.4.vm

XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory

Alan Ezust — Tue, 08 Aug 2023 15:47:47 -0000

Ticket 1924 has been modified: XMLPlugin leaves behind an "XMLPlugin" directory in jEdit's working directory
Edited By: Eric Le Lay (kerik-sf)
Owner updated: None => 'kerik-sf'