|
From: Makarius <mak...@sk...> - 2019-05-28 20:18:48
|
On 28/05/2019 21:19, Alan Ezust wrote: > > The original MacOSX plugin is still in Subversion, so I guess we should > create a new git repo for the MacOS plugin. > Importing the history from svn to git is possible using open source > tools. I recommend doing that. > You now have permissions to create the git repo and do the importing. I've had a brief look at https://sourceforge.net/p/jedit/svn/HEAD/tree/plugins -- there is an older MacOS plugin and a newer MacOSX plugin. This corresponds to the history of names for the Apple Mac Operating System. Here are some more recent names of the thing: Mac OS X 10.10 Yosemite Mac OS X 10.11 El Capitan macOS 10.12 Sierra macOS 10.13 High Sierra macOS 10.14 Mojave The plugin for Java 11 requires de-facto a relatively recent version of the OS to work really well. The last 3 called "macOS" should be fine, which is the reason for proposal to use this name for the plugin now. Is it OK to start a plugin name with lowercase? BTW, this odd confusion of plugin names and underlying Java versions will continue with the app bundle for a standalone application on macOS. A choice needs to be made if it runs on Java 8 or Java 11, and the appropriate plugin needs to be used. Now we are back to my tendency to assume that the Java version is >= 11 overall. At least on macOS that should be (almost) always the case: Mac users are usually quite up-to-date. Makarius |