sure. at least for CORE plugins that is. it saves adding addMainMenuPlugin()
and friends to the initialize() method and makes clear that default-plugins.xml
is authorative, meaning it can even completely disable a plugin installation.
not saying to change our old plugins, but use it when adding new ones, as you
are doing already!
for Extensions it makes no sense, as they exist outside of CORE, so we may add
a override there (eg. i did it for the Printing plugins) but they must install
fine without as well, as CORE not necessarily knows about every plugin out
there.
..ede
---
** [bugs:#504] TODO: OJ2.x**
**Status:** open
**Milestone:** OJ_2.x
**Created:** Mon Sep 14, 2020 11:44 AM UTC by ede
**Last Updated:** Sun Oct 18, 2020 01:30 PM UTC
**Owner:** nobody
this is not actually a bug ticket, but a notepad for backward compatible
breaking things to do in OJ2.x
FeatureInstaller
privatize Constructor
replace new FeatureInstaller() with FeatureInstaller.getInstance() projectwide
rework I18N, see extra ticket https://sourceforge.net/p/jump-pilot/bugs/501/
---
Sent from sourceforge.net because jump-pilot-devel@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/jump-pilot/bugs/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/jump-pilot/admin/bugs/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
