On Fri, 28 Oct 2022 at 17:14, Ernie Rael <err...@raelity.com> wrote: > This practice (what you call a bad idea) has been working for 20 years > with this plugin,
You're relying on forward compatibility. NetBeans has never offered that as a goal as far as I know, just solid backward compatibility. You might get away with it, but you'll probably need to work around it. > Given that sigtest failed, I'm surprised that there's so much surprise > that there's an issue. I'm actually amazed that > > "don't think this actually breaks compatibility in a bad away" > > seems to be a prevailing direction. Because it doesn't break backward compatibility? If it did, it would be an issue. We ran an extra RC for 15 because a backward compatibility issue had been introduced. If anyone thinks this does, please raise it so that the issue can be addressed. Introducing generics is likely to lead to things breaking when compiled against newer code. That's part of their implementation. I doubt it's the first thing in the platform that would be affected here, just the first one that's caused you an issue! ;-) > And note that with > awareness of new features, the plugin **must** be compiled on a new > release (or use reflection a lot more than the amount the plugin does). If you're going to do this, you'll need to workaround problems that might arise. So does the workaround I suggested work for you? 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
