platform limitation, not the limitation of jpackage.
> >
> > [1] https://msdn.microsoft.com/en-us/library/aa370859%28v=VS.85%29.aspx
> >
> > - Alexey
> >
> > On 3/24/2022 2:04 PM, Sverre Moe wrote:
> >> Hi,
> >>
> >> This has been atte
be the best option).
> They don't have this issue.
>
> - Alexey
>
> On 3/23/2022 10:01 AM, Sverre Moe wrote:
> > Could jpackage instruct WiX when building a native application on
> Windows,
> > to support 4 digits in the version?
> >
> > 14:41:18 Detected [li
Could jpackage instruct WiX when building a native application on Windows,
to support 4 digits in the version?
14:41:18 Detected [light.exe] version [3.11.2.4516].
14:41:18 Detected [candle.exe] version [3.11.2.4516].
14:41:18 WiX 3.11.2.4516 detected. Enabling advanced cleanup action.
ular jdk.jpackage.internal.IOUtils.writableOutputDir() function is
> the same in JDK14, JDK17, and mainline.
>
> - Alexey
>
> On 2/18/2022 8:31 AM, Sverre Moe wrote:
>
> I executed our JDK11 docker image, which works fine with JDK11 and JDK14
> (for jpackage support).
>
It is only in the
Docker container that it does not work.
/Sverre
tir. 5. okt. 2021 kl. 11:55 skrev Sverre Moe :
> I ran cacls after the failed jpackage.
>
> C:\temp\my-javafx-application>cacls build
> C:\temp\my-javafx-application\build F
>
/Sverre
tir. 5. okt. 2021 kl. 10:41 skrev Alan Bateman :
> On 05/10/2021 08:54, Sverre Moe wrote:
> > With JDK 17, jpackage fails to write to the destination directory on
> > Windows.
> >
> > It worked fine with JDK 11 (with jpackage from JDK14) and Docker.
> >
With JDK 17, jpackage fails to write to the destination directory on
Windows.
It worked fine with JDK 11 (with jpackage from JDK14) and Docker.
Only happens on Windows docker. Running directly on WIndows it works with
JDK 17.
What has changed with jpackage that it no longer can write to the
Seems it was filed, and has already been fixed in JDK17
https://bugs.openjdk.java.net/browse/JDK-8261845
Strange, I searched, but could not find any issues when I filed my bug
report.
/Sverre
man. 26. apr. 2021 kl. 19:19 skrev Sverre Moe :
> There was a regression introduced in JDK
There was a regression introduced in JDK 15 of jpackage tool on Windows.
The file permission of the built EXE has changed. The file is now ReadOnly.
Both EXE and MSI was ReadWrite, now
EXE is Read-Only while MSI is still Read-Write
The EXE can no longer be signed because it cannot be modified.
I
tor. 26. mar. 2020 kl. 23:21 skrev Sverre Moe :
> tor. 26. mar. 2020 kl. 21:29 skrev Alexey Semenyuk <
> alexey.semen...@oracle.com>:
>
>>
>>
>> On 3/26/2020 4:13 PM, Sverre Moe wrote:
>>
>> tor. 26. mar. 2020 kl. 20:41 skrev Alexey Semenyuk <
>
tor. 26. mar. 2020 kl. 21:29 skrev Alexey Semenyuk <
alexey.semen...@oracle.com>:
>
>
> On 3/26/2020 4:13 PM, Sverre Moe wrote:
>
> tor. 26. mar. 2020 kl. 20:41 skrev Alexey Semenyuk <
> alexey.semen...@oracle.com>:
>
>>
>>
>> On 3/26/202
tor. 26. mar. 2020 kl. 20:41 skrev Alexey Semenyuk <
alexey.semen...@oracle.com>:
>
>
> On 3/26/2020 11:17 AM, Sverre Moe wrote:
> > Running jpackage to build an RPM will add some Requires to the package.
> >
> > It comes from the Template file:
> >
>
Running jpackage to build an RPM will add some Requires to the package.
It comes from the Template file:
https://github.com/openjdk/jdk/blob/jdk-14%2B36/src/jdk.incubator.jpackage/linux/classes/jdk/incubator/jpackage/internal/resources/template.spec
Autoprov: 0
Autoreq: 0
%if
fre. 18. okt. 2019 kl. 01:17 skrev Alexey Semenyuk <
alexey.semen...@oracle.com>:
>
>
> On 10/17/2019 6:10 PM, Sverre Moe wrote:
>
> I wonder if there is something I can contribute with to improve the
> localization. Perhaps work further with the existing Localizati
.net/browse/JDK-8232136
>
> - Alexey
>
> On 10/10/2019 1:46 PM, Sverre Moe wrote:
> > It should be possible to provide localized strings to the Windows
> installer
> > with jpackage.
> >
> > WiX supports building localized installers through the use of language
It should be possible to provide localized strings to the Windows installer
with jpackage.
WiX supports building localized installers through the use of language
files that include localized strings.
tir. 8. okt. 2019 kl. 19:19 skrev Alexey Semenyuk <
alexey.semen...@oracle.com>:
>
>
> On 10/8/2019 12:43 PM, Sverre Moe wrote:
> > Some comments about the jpackage+1-49 update.
> >
> > 1) It has become a lot more verbose since jpackage+1-35. Makes using t
Some comments about the jpackage+1-49 update.
1) It has become a lot more verbose since jpackage+1-35. Makes using the
verbose argument difficult to actually see relevant output, like the actual
rpmbuild/dpkg command output.
It seems to be running rpmbuild --version twice
Running [rpmbuild
ons. 2. okt. 2019 kl. 19:14 skrev Alexey Semenyuk <
alexey.semen...@oracle.com>:
>
>
> On 10/2/2019 12:33 PM, Sverre Moe wrote:
>
> ons. 2. okt. 2019 kl. 16:07 skrev Alexey Semenyuk <
> alexey.semen...@oracle.com>:
>
>> Hi Sverre,
>>
>> Thank y
ons. 2. okt. 2019 kl. 16:07 skrev Alexey Semenyuk <
alexey.semen...@oracle.com>:
> Hi Sverre,
>
> Thank you for doing this research. I don't think we should complicate
> jpackage by adding signing steps in it.
> However we can add a call to custom script after msi is constructed but
> before it
ons. 25. sep. 2019 kl. 15:45 skrev Sverre Moe :
> I have some new comments regarding the Windows build of jpackage.
>
> 1)
> Is there any way to build an trusted application installer using WiX?
> I want to avoid "Unknown Publisher" when installing the applicatio
I have some new comments regarding the Windows build of jpackage.
1)
Is there any way to build an trusted application installer using WiX?
I want to avoid "Unknown Publisher" when installing the application.
Also having problems with Windows Defender SmartScreen, depending on what
settings the
gt; mailinglist.
>
> Yes, that would be best, as this is no longer related to jpackage.
>
> -- Kevin
>
>
> On 9/19/2019 12:43 AM, Sverre Moe wrote:
> > Yes it would seem so.
> >
> > I am still perplexed to why it has an RPM Requires
> libavcodec-ffmpe
p. 2019 kl. 01:09 skrev Michael Paus :
> If you don't use audio or video, you will probably not need it.
>
> Have a look here: https://ffmpeg.org/
>
> > Message: 2
> > Date: Wed, 18 Sep 2019 23:44:19 +0200
> > From: Sverre Moe
> > To: Philip Race
> >
(SUNWprivate_1.1)(64bit)
libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)
libnet.so()(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
libpthread.so.0(GLIBC_2.3.2)(64bit)
libverify.so()(64bit)
libz.so.1()(64bit)
/Sverre
tir. 17. sep. 2019 kl. 10:25 skrev Sverre Moe :
> I have bu
Sverre Moe :
> Where does the Requires for libavcodec-ffmpeg and libavcodec.so come from?
> Is it javafx-media which requires these.
>
> The first one of these two requires I cannot find an RPM package for on
> www.rpmfind.net.
>
> Actually we are not using the javafx-media in our
, but would be interesting to see what would happen
without this require while running an media JavaFX application.
/Sverre
ons. 18. sep. 2019 kl. 23:20 skrev Sverre Moe :
> It seems many of the RPM Requires comes from me adding the JavaFX jmods to
> the application image.
> --ad
I have built many times with the new jpackage, but actually just now tried
to install the package built by it.
The new jpackage adds a lot of Requires to the built RPM package. We had
the same problem with the old javapackager. Its default RPM spec file had a
lot of Requires that made it
0)
at
jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:513)
at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:97)
at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:51)
tor. 5. sep. 2019 kl. 17:12 skrev Sverre Moe :
> I have done some investigation myself.
>
1 skrev Andy Herrick :
> This is easily reproducible by putting ampersand in --vendor value on
> windows.
>
> will investigate.
>
> /Andy
> On 9/4/2019 8:05 AM, Sverre Moe wrote:
>
> Running WiX failed.
> The problem it seems is the -dJpAppVendor. It cannot handle sp
ntially cause problems when installing SNAPSHOTs which have
the same version?
Anyway it does not seem WiX XML schema has any release or build attributes.
/Sverre
tor. 29. aug. 2019 kl. 17:38 skrev Sverre Moe :
> No, have not installed WIX. Had InnoSetup from when we use javapackager.
> I wi
I tired the latest build 14-jpackage+1-35 today. Good to see that debian
package file name is finally up to the specification.
Noticed something though with building the debian package:
When using a control file from the resource directory, jpackage does not
use its version and release.
Must
ted all three arguments as expected.
>
> /Andy
> On 9/2/2019 7:14 AM, Sverre Moe wrote:
>
> I am having problem with arguments not being passed to the application.
> The fix JDK-8224486 in this EA release seems to have something to do with
> arguments, but it is actually just the
I am having problem with arguments not being passed to the application.
The fix JDK-8224486 in this EA release seems to have something to do with
arguments, but it is actually just the JavaOptions.
The options in ArgOptions in the jpackage cfg does not seem to be passed to
the application
on your machine? That is a prerequisite.
>
> Andy: Do we have a bug filed to produce a better error message in this
> case? If not, we need to file one.
>
> -- Kevin
>
>
> On 8/29/2019 7:30 AM, Sverre Moe wrote:
>
> It is not working creating native installer on Windows.
>
> It
It is not working creating native installer on Windows.
It will not take neither exe nor msi as --package-type on Windows.
jdk.jpackage.internal.PackagerException: Error: Invalid or unsupported
package type: [exe].
at
is to set the --app-version CLI option.
/Sverre
Den man. 17. des. 2018 kl. 11:31 skrev Sverre Moe :
>
> I have discovered a bug with the jpackage created application image.
> It does not pass any --arguments to the application.
> The application.cfg contains the arguments, but the native
/Sverre
Den søn. 16. des. 2018 kl. 20:28 skrev Sverre Moe :
>
> Den søn. 16. des. 2018 kl. 19:32 skrev Andy Herrick :
> >
> >
> > On 12/15/2018 12:44 PM, Andy Herrick wrote:
> > While investigating this, I found undocumented functionality left over
> > from
Den søn. 16. des. 2018 kl. 19:32 skrev Andy Herrick :
>
>
> On 12/15/2018 12:44 PM, Andy Herrick wrote:
> While investigating this, I found undocumented functionality left over
> from JavaFXPackager that may be the root of these class-path messages.
>
> This is both dangerous and powerful, and
Den søn. 16. des. 2018 kl. 14:27 skrev Andy Herrick :
>
> The result of JDK-8213392 was not that there was any problem creating
> the package, but that the packaged app would not run, because the
> modules from the --module-path arg are never included in the packaged
> app, or referenced in the vm
Den lør. 15. des. 2018 kl. 18:44 skrev Andy Herrick :
>
>
> On 12/15/2018 11:26 AM, Sverre Moe wrote:
>
> Some feedback from using this new JDK12 jpackage.
>
> I have yet to find out how to specify the bundle resources. It tells to put
> them on the class path,
Noticed now that there was an --app-version argument as replacement for the
previous --version.
Though I would like to see any examples during help how to specify the
bundle resources to class path.
/Sverre
Den lør. 15. des. 2018 kl. 17:26 skrev Sverre Moe :
> Some feedback from using this
Some feedback from using this new JDK12 jpackage.
The argument --version is no longer used for setting the bundler version.
Thus one needs to specify bundle resources (spec for RPM and control for
DEB), if the version is anything other than "1.0".
I have yet to find out how to specify the bundle
/application.png)
Perhaps jpackager should have an package directory argument
--package-dir build/deploy
/Sverre
Den tor. 15. nov. 2018 kl. 15:05 skrev Andy Herrick :
>
> On 11/10/2018 8:12 AM, Sverre Moe wrote:
>
> I have been using the jpackager that Johan Vos backported for OpenJDK 11.
Hello,
May I chime in a little on the jpackager.
I have been using it with OpenJDK 11, as backported by Johan Vos from Gluon.
It has worked fine, but I have noticed some flaws.
1)
The control file for DEB package does not set correct description
--name test
--description This is a Test
I have been using the jpackager that Johan Vos backported for OpenJDK 11.
For this I have some points of improvement I would like to mention.
1)
The control file for debian package does not set correct description
--name test
--description This is a Test Application
46 matches
Mail list logo
