Re: API change

; > > > Hi, > > > > > > > > You're welcome! That's a way of building trust :-). > > > > > > > > Some of the committers around (not me, though) use NetBeans as a > > > > platform for building applications, or to build plugins, so i

Re: API change

me, though) use NetBeans as a > > > platform for building applications, or to build plugins, so it's > > > always a good idea to ask in the mailing list when suggesting an API > > > change. > > > > > > Kind regards, > > > Antonio > > >

Re: API change

> > > > Some of the committers around (not me, though) use NetBeans as a > > platform for building applications, or to build plugins, so it's > > always a good idea to ask in the mailing list when suggesting an API > > change. > > > > Kind regards, > &

Re: API change

it's always a good idea to ask in the mailing list when suggesting an API change. Kind regards, Antonio El 10/5/22 a las 22:17, Łukasz Bownik escribió: Thank You for explaining the process and reasoning behind it. It is also good to know the community's attitude towards backward compatibility

Re: API change

Hi, You're welcome! That's a way of building trust :-). Some of the committers around (not me, though) use NetBeans as a platform for building applications, or to build plugins, so it's always a good idea to ask in the mailing list when suggesting an API change. Kind regards, Antonio El 10

Re: API change

Thank You for explaining the process and reasoning behind it. It is also good to know the community's attitude towards backward compatibility. I'll close the current PRs and try to spoon feed changes while optimising for "diff-readability" until we build some trust. On Mon, May 9, 2022 at 11:09

Re: API change

Dne 09. 05. 22 v 22:17 Łukasz Bownik napsal(a): The problem is that another method of this class *public String processPattern(String newPattern) throws IllegalArgumentException* becomes useless now. I think it should be removed. In general no API can be *ever* removed once published in a

Re: API change

Hi, Some comments below. El 9/5/22 a las 22:17, Łukasz Bownik escribió: So I suspect that the probability of any *external client *calling this method is 0. As we have explained in some other threads, NetBeans is both an IDE and a platform. We want to be as much backwards compatible as

Re: API change

I did. https://github.com/apache/netbeans/pull/4081 I was advised to ask this question using mailing list On Mon, May 9, 2022, 3:03 PM Laszlo Kishalmi wrote: > Hi Lukasz, > > Could you create a PR and discuss the code there? Of course a link to > the PR in the dev list is encouraged. > > This

Re: API change

Hi Lukasz, Could you create a PR and discuss the code there? Of course a link to the PR in the dev list is encouraged. This email format is not really suitable for such discussions especially with 78 character wrapping... On 5/9/22 13:17, Łukasz Bownik wrote: Hello. I refactored the

API change

Hello. I refactored the /platform/openide.util/src/org/openide/util/MapFormat.jav a 's *public StringBuffer format(Object pat, StringBuffer result, FieldPosition fpos) *method. The new