From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Classpath -- move out from staging?
Date: Wed, 18 Oct 2023 10:34:10 +0200 [thread overview]
Message-ID: <CABDcavYDnenM1GdAaALRe=0JNQEfc_PovrG8bM6du1+GJpseqw@mail.gmail.com> (raw)
In-Reply-To: <ZS90a2y4F1IjihL8@pengutronix.de>
Hi Michael,
El mié, 18 oct 2023 a las 8:00, Michael Olbrich
(<m.olbrich@pengutronix.de>) escribió:
>
> Hi,
>
> On Sat, Oct 14, 2023 at 04:49:12PM +0200, Guillermo Rodriguez Garcia wrote:
> > I see that the classpath package was moved to staging in commit
> > f2afdd541d3dc1cbac965ddaf899009780de2aae, with a note stating that it
> > could not be built with any current (Java) distribution.
> >
> > My team and I are still using this actively, and it can be built with
> > OpenJDK 8 which is still supported and is expected to be be supported
> > for a while (for example Adoptium states it will be supported "At
> > least until Nov 2026").
> >
> > Can we move this out of staging? If so I will prepare a patch.
>
> No. In fakt, I should have removed it entirely some time ago. I just missed
> it. And I will remove it soon. The problem is, that I cannot even
> build-test it any more and that's the minimum requirement for having it
> upstream.
It should build fine with OpenJDK 8 which is still fully supported and
widely available.
Are you having problems with this?
Can you share the details?
Thanks,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
next prev parent reply other threads:[~2023-10-18 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 14:49 Guillermo Rodriguez Garcia
2023-10-18 6:00 ` Michael Olbrich
2023-10-18 8:34 ` Guillermo Rodriguez Garcia [this message]
2023-10-20 8:06 ` Michael Olbrich
2023-10-20 8:46 ` Guillermo Rodriguez Garcia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABDcavYDnenM1GdAaALRe=0JNQEfc_PovrG8bM6du1+GJpseqw@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox