On Mon, 30 Jan 2023 at 20:08, Matthias Bläsing <mblaes...@doppel-helix.eu.invalid> wrote: > yes, I know how I can sign JARs/NBMs, the point is: This was not > necessary for multiple NetBeans releases. I'm missing the explanation > why something, that was fine for at least 5, releases is now a problem. > > That communication did not happen and was not discussed here.
Welcome to the "verification process isn't working" side of the conversation! :-) Yes, this doesn't seem right. These things should be discussed on dev@ We're about to switch to the NB17 plugin portal for 17-rc3 (as agreed with plugin portal verifiers off-list - so far we kept NB16 portal). The more existing plugins that are verified the better. It's one way of checking if we've introduced inadvertent changes in the IDE since the last release. IMO there are two main reasons a plugin that was verified for the last release shouldn't be in this one. The plugin was using implementation versions, in which case it shouldn't have been verified in the first place. Or we broke backwards compatibility, deliberately or inadvertently, and should consider the problem. Other than that, if it was verified fine for 16 I don't see a reason to apply different rules to 17?! Best wishes, Neil --------------------------------------------------------------------- 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
