Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Not really familiar with the usage or code, but don't suppose BasicFileChooserUI which is in java.desktop serves a similar purpose does it? Eric Bresie ebre...@gmail.com On Fri, Jan 14, 2022 at 2:49 PM antonio wrote: > Of course not. Otherwise we'd be using the java.desktop APIs :-). > > I

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Of course not. Otherwise we'd be using the java.desktop APIs :-). I believe this dependency with sun.swing and sun.awt internals was something that was added to NetBeans long ago [1], possibly to solve some bugs in JFileChooser in Windows back then. Cheers, Antonio [1]

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

I'm sure some of this is a repeat but... Eric Bresie ebre...@gmail.com On Fri, Jan 14, 2022 at 1:26 AM antonio wrote: > Regarding the adoption of JDK 11 and the future stragety we want to > follow, I have several questions: > > 1. Question I: "sun.awt/sun.swing" classes. > > We're using

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

i would always vote for remove/replace if it causes so much dependency trouble (its "just" a file chooser, right?). reducing complexity is important, esp for old projects. -mbien On 14.01.22 08:26, antonio wrote: Hi all, Regarding the adoption of JDK 11 and the future stragety we want to

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Unfortunately due to https://issues.apache.org/jira/browse/NETBEANS-6273 we still need to start NetBeans 12.3 and above on JDK 1.8 due to keyboard mapping issues. With 12.2 and lower this issue is not present. On Fri, 1 Oct 2021 at 16:28, Jaroslav Tulach wrote: > JDK17 is out and Geertjan told

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Hi all, Regarding the adoption of JDK 11 and the future stragety we want to follow, I have several questions: 1. Question I: "sun.awt/sun.swing" classes. We're using sun.awt and sun.swing classes in one "dlight" module we're receiving in the 4th/5th donation. This is because there is an

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On 12.10.21 09:15, Jaroslav Tulach wrote: Hello Matthias. so 9. 10. 2021 v 17:56 odesílatel Matthias Bläsing < mblaes...@doppel-helix.eu> napsal: Am Samstag, dem 09.10.2021 um 10:38 -0500 schrieb Eric Bresie: Frgaal (1) does seem an interesting beast. IMHO2: we only gain syntactic sugar.

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

> On Oct 12, 2021, at 3:15 AM, Jaroslav Tulach > wrote: > > Hello Matthias. > > so 9. 10. 2021 v 17:56 odesílatel Matthias Bläsing < > mblaes...@doppel-helix.eu> napsal: > >> Am Samstag, dem 09.10.2021 um 10:38 -0500 schrieb Eric Bresie: >>> Frgaal (1) does seem an interesting beast. > >

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Hello Matthias. so 9. 10. 2021 v 17:56 odesílatel Matthias Bläsing < mblaes...@doppel-helix.eu> napsal: > Am Samstag, dem 09.10.2021 um 10:38 -0500 schrieb Eric Bresie: > > Frgaal (1) does seem an interesting beast. > IMHO2: we only gain syntactic sugar. No, not at all. We'd get the ability

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Really wasn’t expecting the frgaal comment to provide so much discussion. I was more concerned about other aspects of my comments (target/source/release, multi jars, deprecated/removed apis). On Sat, Oct 9, 2021 at 12:00 PM Jeremy Cavanagh wrote: > Hi, > > Just felt I wanted to add my two

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Hi, Just felt I wanted to add my two pence worth, hopefully, without upsetting anyone. As far as I can see frgaal doesn't offer anything to us. It's main purpose appears to be allowing users who are, for want of a better term, *stuck* with JDK1.8 but would like to try some newer language

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On 09.10.21 17:38, Eric Bresie wrote: Frgaal (1) does seem an interesting beast. How would that work? Netbeans would be compiled using frgaal to support newer features to be still usable on Java 8? its not the java syntax which lets you upgrade to a newer JDKs, its just a bonus on top of

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Brought up fraagl to allow "any/all jdk-11 language features" NOT APIs; fraagl can compile new language features to only JDK 8 bytecodes. Then the ubiquitous JDK 8 runtime can still be used. The issues around APIs are discussed in the "[LAZY CONSENSUS] Drop support for building (and

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Am Samstag, dem 09.10.2021 um 10:38 -0500 schrieb Eric Bresie: > Frgaal (1) does seem an interesting beast. How would that work? Netbeans > would be compiled using frgaal to support newer features to be still usable > on Java 8? Would that in someway have to be targeted (i.e. compiled to a >

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Frgaal (1) does seem an interesting beast. How would that work? Netbeans would be compiled using frgaal to support newer features to be still usable on Java 8? Would that in someway have to be targeted (i.e. compiled to a specific release target) which would adapter for use on java 8? Does

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

Dne sobota 2. října 2021 1:38:20 CEST, Ernie Rael napsal(a): > frgaal? > > How about allowing any/all jdk-11 language features and if a developer > needs to run on jdk8 they must use frgaal to compile NB for jdk8? Frgaal, that'd be fantastic! As far as I know the latest version supports all

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On 04.10.21 15:59, Neil C Smith wrote: On Mon, 4 Oct 2021 at 13:31, Michael Bien wrote: On 04.10.21 12:38, Neil C Smith wrote: On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote: My proposal would be that 12.6 is the last release of Apache NetBeans that supports building on JDK 8, ... Also, I

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On Mon, 4 Oct 2021 at 13:31, Michael Bien wrote: > On 04.10.21 12:38, Neil C Smith wrote: > > On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote: > >> My proposal would be that 12.6 is the last release of Apache NetBeans > >> that supports building on JDK 8, ... > > Also, I realise the other thing

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On 04.10.21 12:38, Neil C Smith wrote: On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote: My proposal would be that 12.6 is the last release of Apache NetBeans that supports building on JDK 8, ... Also, I realise the other thing that needs to be considered there if we're going to do this ..

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote: > My proposal would be that 12.6 is the last release of Apache NetBeans > that supports building on JDK 8, ... Also, I realise the other thing that needs to be considered there if we're going to do this .. 12.6 is the first release to drop all

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On Sat, 2 Oct 2021, 21:02 Will Hartung, wrote: > This will probably be heresy, but any reason to not bump up to v13 so that > it's blatantly obvious something dramatic has changed? (Base JDK is kind of > dramatic) > We're planning a lazy consensus thread (or two) on a bunch of 12.6+ release

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

This will probably be heresy, but any reason to not bump up to v13 so that it's blatantly obvious something dramatic has changed? (Base JDK is kind of dramatic)

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

frgaal? How about allowing any/all jdk-11 language features and if a developer needs to run on jdk8 they must use frgaal to compile NB for jdk8? -ernie On 9/30/2021 11:27 PM, Jaroslav Tulach wrote: JDK17 is out and Geertjan told me the old request is going to appear again. Let me thus

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On Fri, 1 Oct 2021 at 15:58, Jaroslav Tulach wrote: > My proposal would be that 12.6 is the last release of Apache NetBeans > > that supports building on JDK 8, and that *officially* supports > > running on JDK 8. > > I think me and my colleagues may need ability to run the NetBeans core code >

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On 01.10.21 16:44, Jaroslav Tulach wrote: I like this proposal in principle. In case i am missing something - what module would be a candidate for java.target=11 (as example)? I see the applemenu module as a really nice example:

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

My proposal would be that 12.6 is the last release of Apache NetBeans > that supports building on JDK 8, and that *officially* supports > running on JDK 8. I think me and my colleagues may need ability to run the NetBeans core code on JDK 8 for another year. > Because we release sources, it

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

> I like this proposal in principle. > > In case i am missing something - what module would be a candidate for > java.target=11 (as example)? > I see the applemenu module as a really nice example: https://github.com/apache/netbeans/blob/master/platform/applemenu/build.xml#L26 it has two

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

1. In support of this sometime back, I raised this ticket intending to link up related tickets. Figure I would bring it up in case it helps here 2. 3. NETBEANS-5349 Update Netbeans Codebase to Account for deprecated/removed API in

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On 01.10.21 08:29, Jaroslav Tulach wrote: It is obviously possible to do that with reflection the way you describe below. However my preferred way is to use http://wiki.apidesign.org/wiki/AlternativeImplementation E.g. slowly start introducing `org.netbeans.modules.xyz.jdk11` modules that

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

On Fri, 1 Oct 2021 at 07:29, Jaroslav Tulach wrote: > yes, using JDK-11 APIs is obviously one of the next steps: > > > We should just be prepared, when the > > first version bumps for release to 11 are requested :-). > > It is obviously possible to do that with reflection the way you describe >

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

The next message I found in the February thread is this reply to Matthias. I have even written a [blog post]( http://wiki.apidesign.org/wiki/AlternativeImplementation) at that time! Thanks Matthias, yes, using JDK-11 APIs is obviously one of the next steps: > We should just be prepared,

[DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

JDK17 is out and Geertjan told me the old request is going to appear again. Let me thus review an old thread from November/February... -- Forwarded message - From: Jaroslav Tulach Date: Feb 9 2021 Hi. I knew the time for a discussion like this is going to come when I wrote my