On 20.10.22 18:46, Matthias Bläsing wrote:
Hi,
Am Donnerstag, dem 20.10.2022 um 18:35 +0200 schrieb Michael Bien:
what if we leave the process as is for now but keep plugins in the
catalog if there were verified within the last 2-3 releases.
This would also fix the problem of having an empty catalog on every new
release.
I think this might improve the situation until there is a better solution.
and will break, if the plugin has a hard dependency on the target
NetBeans version. We recently had a discussion here about access to
flatlaf internals, which is required to get additional flatlaf modules
working. There is a high probability, that this will requirere updates
on every NetBeans version.
plugins with an impl dependency on something in the IDE shouldn't install.
Blacklists etc would be also an option to keep problematic plugins from
propagating up in the catalog. (e.g if a verifier sees there is a problem)
the current reality is that there are 5 plugins in the plugin manager
(at the end of the NB lifecycle!). I think that would be an upgrade even
if it creates the possibility that it breaks some unmaintained plugins.
It could even create a positive pressure from users to maintainers to
upgrade the plugins.
-mbien
greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
