{{{ TEI 1.4
Source: Source code is at https://github.com/Conal-Tuohy/jEdit-TEIPlugin.git with tag 1.4
Announcement: Initial Plugin Central release
Requires Java 1.6
Requires jEdit 05.00.99.00
Required plugins:
EclipseIcons 1.0 (eclipseicons.EclipseIconsPlugin)
SaxonPlugin 9.5.1.1 (saxon.SaxonPlugin)
SideKick 1.8 (sidekick.SideKickPlugin)
XML 3.0.6 (xml.XmlPlugin)
Optional plugins:
BufferTabs 1.2.4 (buffertabs.BufferTabsPlugin)
Short Description: This plugin provides tooling for working with Text Encoding for Interchange (TEI) XML. Development of the initial version of the plugin was funded by DARIAH-EU in 2018/2019. Long Description: <html>
This plugin provides tools for text encoding using TEI XML
Thanks for the plugin! It seems to work nicely.
It can't be released because it doesn't use the plugin-build.xml defined task from build-support, resulting in missing package task (that produces binary only and full (with source code) archives that are then uploaded to plugin central).
Also, if you don't mind bumping to jdk 1.8 and jEdit 5.5, it would be great (jEdit 5.0 / java 1.6 looks too old to me and I have no means to test it).
It's quite a mouthful to take in the build-support infrastructure, but have a look at the XML plugin for inspiration and don't hesitate to ask for help.
Hi Eric,
As far as I know, it's not a requirement to use plugin-build.xml. The build
file just has to produce a complete jar file by running "ant dist". There
are a lot of plugins that were written before plugin-build.xml was written,
and there are some since that don't use it. I know the jEdit docs don't say
that anymore, but I think that is still the minimum requirement for a build
file.
Also, Java 11 is the minimum now, yes?
Dale
On Sun, May 31, 2020 at 7:59 PM Eric Le Lay via jEdit-devel jedit-devel@lists.sourceforge.net wrote:
Related
Plugin Central Submission:
#1055Thanks Dale!
Earlier I had used the build-support infrastructure but then later I
eliminated it in order to reduce the complexity of the build process. Right
now, the plugin can simply be cloned from the git repo, and built,
requiring nothing but Ant. The build.xml file is quite small and simple
since it isn't coupled with build-support at all. The reason I did this is
because I want to make the plugin maximally accessible to multiple
developers in the TEI community, almost none of whom know anything about
jEdit. I'd like to make it as easy as possible for these developers to
contribute small changes and additions to the plugin without knowing much
about jEdit or its custom build tools. Especially so because I hope and
expect that the plugin will grow to include more functionality which may be
implemented in XPath, XSLT, XQuery, etc, which are common programming
languages in the TEI community (more so than Java), and I don't want
potential contributors to be excluded by a steep learning curve.
So if I can meet the practical requirements for deployment to Plugin
Central without build-support, I'd like to continue with that approach
I take it from Eric's comment that I need to implement another target to
package a source distribution as well. I will have a look at this and if
it's obvious I'll add it. If anyone can give me some practical advice
quickly though, that would be much appreciated! Is there anything else the
build needs to do?
Conal
On Mon, 1 Jun 2020 at 10:22, Dale Anson dale@daleanson.com wrote:
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
Related
Plugin Central Submission:
#1055Hi Conal, Dale,
here is what I need to release, taking the small Geo plugin as an example:
Any way to produce them automatically would be nice
Last edit: Eric Le Lay 2020-06-01
Hi Eric!
I've tried to follow the point of your example.
I am assuming that the actual requirements for deployment to Plugin Central are:
I only put only 1 jar file (i.e. TEI.jar) into the binary packages, since the only jars which the TEI jar depends on are themselves jEdit plugins which the TEI plugin is marked as depending on.
To generate the four package files, I have added a 'package' target to the TEI plugin's build.xml file which writes the 4 archive files into a 'dist' directory.
Do I have that right?
I also took your advice to update the required jEdit version to 5.5, and the required Java version to 8.
Yes: I can release it now (tried your latest master).
Just make a tag (doesn't have to be = to the the version)...
Thanks,
Last edit: Eric Le Lay 2020-06-17
Thanks Eric!
I've added the tag
1.4.1
Thanks,
released to plugin central (will show up soon in jEdit plugin manager).
It'll be in the HTML&XML category.
http://plugins.jedit.org/plugins/?TEI
Last edit: Conal Tuohy 2020-06-19