Thanks!
Yes, I've since downloaded the jdk-13 version and moved to experimenting
directly with jpackage
without the ant component to reduce the number of variables.
Now the .app seems to be produced without errors (does not yet run though, need
to get my ducks in a row first).
But the custom
There have been updates since then. In particular, you can now find it
hosted here: https://jdk.java.net/jpackage/
What you download is an EA build of jdk-13 which includes jpackage. You
just use the jpackage that's in that. (You don't have to use that JDK
for anything else, just literally
Den fre. 14. des. 2018 kl. 13:47 skrev Johan Vos :
> Hi Sverre,
>
> Scene Builder 11 is built using that backported packager, but not
> everything was working yet.
> It is not the intention to make a real product based on this backported
> code -- we just did it to fill the gap until the jpackage
[including Andy]
On 12/13/2018 10:25 AM, Sverre Moe wrote:
Has anyone been able to use jpackager with bundle resources?
The jpackager says to put these on the class path
Using default package resource [menu icon] (add package/linux/app.png to
the class path to customize)
Using default package
Den ons. 19. sep. 2018 kl. 10:56 skrev Johan Vos :
> Hi,
>
> As promised, we looked into an interim solution for the packager-gap. Work
> for the new Java Packager (12?) is being done in the OpenJDK sandbox repo.
> We backported the required changes to an OpenJDK 11 mirror:
>
Johan,
has there been any new updates to jpackager in JDK12 since you backported
it?
I have found some problems with jpackager. Perhaps they might have been
fixed later.
I mentioned this to core-list-dev mailinglist on jpackager thread.
1)
The control file for debian package does not set correct
Hi,
I got jpackager working with OpenJDK11.0.1 after a bit of trial and error.
I'm now able to create a windows image like I had before with javapackager.
I thought I'd share some of the issues I've had in case it helps anyone out.
The first one was that you need to copy jdk.packager.jar not
I am having some problems accessing the jpackager from symlinks, seems it
cannot find the jdk.packager.jar
/usr/bin/jpackager -> /etc/alternatives/jpackager
/etc/alternatives/jpackager -> /usr/java/jpackager/jpackager
:/ # jpackager --help
Error occurred during initialization of boot layer
On 9/27/18 1:44 AM, Johan Vos wrote:
Hi Ty,
Apart om jdk.jlink, who else is
exporting jdk.tools.jlink.internal.packager ?
If that is the case, there must be something wrong.
The 12-sandbox version also exports that package:
Den tor. 27. sep. 2018 kl. 18:50 skrev Kevin Rushforth <
kevin.rushfo...@oracle.com>:
> You mean openjfx11, not JDK 11, right? Backporting this fix would mean an
> openjfx 11.x update release would stop building or running with JDK 10. Not
> something that would be done lightly, since it would
You mean openjfx11, not JDK 11, right? Backporting this fix would mean
an openjfx 11.x update release would stop building or running with JDK
10. Not something that would be done lightly, since it would break the
"FX N runs with JDK N-1" policy we have been discussing lately. There is
an easy
Any chance of getting the fix for JDK-8210759 backported to JDK 11? I
remember reading the OpenJDK will be patched up to 2023 (while Oracle JDK
will be patched up to 2026).
We deliver software that our customers could be running for a decade or
more. The LTS is the version we will then target when
I missed seeing the swing exception in your earlier message. Yes, the
Swing issue is a known problem in openjfx11, JDK-8210759 [1], and is
documented in the release notes [2].
It will be fixed in openjfx12 just as soon as I push the fix for
JDK-8210092 [3] later today (the review was just
Without the reliance on javafx-swing I was able to create an image, package
and execute my test application.
Is the Swing problem a known bug in JavaFX 11?
The jlink runtime image I reckon now also contains the JavaFX modules?
Seems unnecessary when they already are dependencies.
/Sverre
Den
Den tor. 27. sep. 2018 kl. 00:49 skrev Kevin Rushforth <
kevin.rushfo...@oracle.com>:
> No, jlink won't link in a non-modular application. So the steps are:
>
> 1) Run jlink to create a Java runtime image, possibly stripped down, and
> include the javafx.* modules you need
> 2) Run jpackager to
Hi Ty,
Apart om jdk.jlink, who else is exporting jdk.tools.jlink.internal.packager
?
If that is the case, there must be something wrong.
The 12-sandbox version also exports that package:
http://hg.openjdk.java.net/jdk/sandbox/file/6972c0e75e23/src/jdk.jlink/share/classes/module-info.java
- Johan
On 9/19/18 3:55 AM, Johan Vos wrote:
Hi,
As promised, we looked into an interim solution for the packager-gap. Work
for the new Java Packager (12?) is being done in the OpenJDK sandbox repo.
We backported the required changes to an OpenJDK 11 mirror:
No, jlink won't link in a non-modular application. So the steps are:
1) Run jlink to create a Java runtime image, possibly stripped down, and
include the javafx.* modules you need
2) Run jpackager to package your non-modular application with the above
Java runtime image.
-- Kevin
On
Does jlink work for non-modular stuff? The last time I tried it complained to
me too. I guess it gives up because it can’t automatically figure out module
dependencies. The error below shows jlink is what is complaining.
Scott
> On Sep 26, 2018, at 3:44 PM, Kevin Rushforth
> wrote:
>
>
jpackager should work for non-modular applications as well as modular
ones. We've tested it for simple applications with or without FX. In the
latter case, the testing I've done has been done by first using jlink to
create a Java runtime with the needed JDK modules + the openjfx11
modules
I have tried this jpackager a bit. It is working fine packaging a Java
modular project.
However it fails to package a none modular project. I modified my project
and removed the modularization and tried again to see if it would work to
package our legacy Java 8 project (though now built with JDK
21 matches
Mail list logo
