jpackage current status
mik3hall at gmail.com
Sat Feb 22 18:04:31 UTC 2020
> On Feb 22, 2020, at 11:10 AM, Michael Hall <mik3hall at gmail.com> wrote:
>> On Feb 22, 2020, at 10:14 AM, Tom Schindl <tom.schindl at bestsolution.at <mailto:tom.schindl at bestsolution.at>> wrote:
>> At Eclipse it is tracked as https://bugs.eclipse.org/bugs/show_bug.cgi?id=559482 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=559482>
> Not quite sure what would of triggered it yesterday.
OK. So I think what the deal was is that the jpackage development branch, that I’ve been using for some time, dodged the bullet on this bug. It picked it up when it merged in with the main stream. And I picked it up when I installed that.
Unfortunately I didn’t save a prior jdk14 jpackage jre. So to launch Eclipse I had to remove all JDK 14 JRE’s. Then Eclipse wanted a jdk14. So I renamed an old jdk13 jpackage one to jdk14. Eclipse than launched.
To make this a little easier to work with I changed the default installed jre to jdk-13, the eclipse.ini vm to jdk-13 and renamed the jpackage one back to jdk-13.jdk.
I think now I should be able to re-install a jdk14 to test that and current jpackage. Just for now eclipse will use a slightly older, jpackage specific, one.
More information about the core-libs-dev