Proposing to move JMC 9 to JDK 17.
Marcus Hirt
marcus.hirt at datadoghq.com
Mon May 1 14:46:48 UTC 2023
Goodie! Virag is working on a PR for the change.
Kind regards,
Marcus
On Fri, Apr 28, 2023 at 6:12 PM Langer, Christoph
<christoph.langer at sap.com> wrote:
>
> Sounds fine and will make things less complicated. 😊
>
>
>
> From: jmc-dev <jmc-dev-retn at openjdk.org> On Behalf Of Brice Dutheil
> Sent: Freitag, 28. April 2023 09:11
> To: Miro Wengner <miro.wengner at gmail.com>
> Cc: Marcus Hirt <marcus.hirt at datadoghq.com>; jmc-dev at openjdk.java.net
> Subject: Re: Proposing to move JMC 9 to JDK 17.
>
>
>
> +1
>
> Non binding
>
>
>
> -- Brice
>
>
>
> On Thu 27 Apr 2023 at 20:18 Miro Wengner <miro.wengner at gmail.com> wrote:
>
> +1
> Kind Regards
> Miro
>
> > On 27. Apr 2023, at 17:29, Marcus Hirt <marcus.hirt at datadoghq.com> wrote:
> >
> > Hi all,
> >
> > I propose that we move JMC 9 to use JDK 17 for compiling all parts of
> > JMC 9, including JMC core. The reason is that we need to move to Tycho
> > 3.0 to properly support working with the project in the newer versions
> > of Eclipse.
> >
> > I also propose to require JDK 17 for running all parts of JMC 9, to
> > simplify requirements, and to allow developers to use JDK 17 features
> > when developing JMC. We already require JDK 17 to run the RCP
> > application build of JMC, since newer versions of the Eclipse platform
> > require JDK 17 to run.
> >
> > Note that it will still be possible to connect to, read and process
> > JFR recordings from, and run the other tools (e.g. JOverflow) on
> > processes running JDK 8+.
> >
> > Kind regards,
> > Marcus
>
> --
>
> Brice
More information about the jmc-dev
mailing list