On Wed, 3 Nov 2021 at 16:37, Matthias Bläsing <mblaes...@doppel-helix.eu> wrote: > Am Mittwoch, dem 03.11.2021 um 16:23 +0000 schrieb Neil C Smith: > > On Tue, 2 Nov 2021 at 16:30, Laszlo Kishalmi <laszlo.kisha...@gmail.com> > > wrote: > > > > > > https://github.com/apache/netbeans/blob/4078eeb7c3ab73c21ce669f1a81b8477332afac1/ide/web.common/nbproject/project.xml#L197 > > > > Wow, that is a friendly module! :-) > > > > I'm still in favour of getting rid of all friend APIs. At least I > > think they're the wrong choice for in-development modules. At least, > > this is better - > > https://netbeans.apache.org/wiki/APIDevelopment.asciidoc#Support_for_Early_Adoption > > > > I'm ok with graduating APIs from friend to public, BUT we need to be > able to break compatibility if it does not make sense anymore and be > willing to bump the major version of a module (i.e. break all users).
Absolutely! That's discussed in that link btw. > This still needs to be a planned process. It is never a "oh, just > remove the friend flag", but a "I had a look at the API, thought about > the potential issues, suggest the following changes and then lets make > it public" process. It will be painful. I remain of the view that's painful anyway as soon as the API has been exposed, whether via the friends mechanism or not. And anyway, one of the best ways to get feedback on the potential issues is to make them public?! So, yes, I'm very much in the "oh, just remove the friend flag" camp - much prefer JDK's concept of preview features. 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
