Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Leitner <richard.leitner@skidata.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: meta-java - recent commits break foreign (MY!) builds ...
Date: Mon, 31 Aug 2015 09:33:51 +0200	[thread overview]
Message-ID: <55E4035F.6040608@skidata.com> (raw)
In-Reply-To: <CAP9ODKrJz7h9XpTrJZ-k+3nu-W=eFCb4W=91WH_JivZopb6fCg@mail.gmail.com>

On 08/28/2015 04:11 PM, Otavio Salvador wrote:
> On Fri, Aug 28, 2015 at 3:59 AM, Richard Leitner
> <richard.leitner@skidata.com> wrote:
>> I think we should keep (and UPDATE!) openjdk 6 & 7 as long as they get
>> support from RedHat and therefore IcedTea. There may be users relying on
>> the old java version for their long-term-supported products (so do we)!
>>
>> IMHO we should start with openjdk 6: remove the old versions and add the
>> latest (1.13.8)!
>>
>> What do you think? Any comments?
> 
> If you are willing to work on that, I have no problem.

As I mentioned, I will update openjdk-7 as long as I need it. If it's
okay for you I will send patches for these updates to the ml. From a
current point of view it looks like I will provide updates until end of
2016 at least.

> 
> The point is Java is complex and we have few people working on this so
> I prefer one well maintained version than 3 oddly ones.

I understand that. But currently I have no need for openjdk-8. Therefore
my focus is on keeping openjdk-7 up to date.



  reply	other threads:[~2015-08-31  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 16:48 meta-java - recent commits break foreign (MY!) builds Jens Rehsack
2015-08-27 13:28 ` Otavio Salvador
2015-08-28  6:59   ` Richard Leitner
2015-08-28 14:11     ` Otavio Salvador
2015-08-31  7:33       ` Richard Leitner [this message]
2015-08-31 13:06         ` Otavio Salvador
2015-08-31 13:39           ` Richard Leitner

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=55E4035F.6040608@skidata.com \
    --to=richard.leitner@skidata.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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