On Mon, 12 Jul 2021 at 22:17, Emilian Bold wrote:
> I don't think the Platform is opinionated about not including a JRE,
Absolutely, in fact in some ways the opposite ...
> NetBeans used to come as a JDK bundle in the Sun Microsystems and
> Oracle days. So, all the plumbing is still there and
The Java Modules referred to there can simply be the modules of the JRE - not
your application. I use jlink and jpackage all the time to package non-modular
applications.
I just have to select the Java modules of the JDK that the application needs.
Since my application is non-modular, I
I don't think the Platform is opinionated about not including a JRE,
it's just that they can't under Apache.
NetBeans used to come as a JDK bundle in the Sun Microsystems and
Oracle days. So, all the plumbing is still there and in the conf file
is just a jdkhome to set.
It was relatively easy to
Hi everyone,
Thank you very much for the thoughtful replies. It's very helpful to
hear about how others do things.
It sounds like I am probably making my life more difficult than it needs
to be by choosing to use JPMS modules. Personally, I believe that as
JPMS modules are adopted more and
On Wed, 7 Jul 2021 at 21:19, Emilian Bold wrote:
> 2. Use Maven and nbm-maven-plugin.
...
> 4. Once you have a zip file with the launchers it's super easy to make
> a macOS DMG and a Windows installer (using Inno Setup).
Mostly agree with Emi, but despite using Maven for most things, I do
still
"The jlink tool links a set of modules, along with their transitive
dependencies, to create a custom runtime image."
JPMS is necessary if you want to use jlink, according to the oracle manual.
It is the reason I am migrating my old programs to JPMS as and when the
mood takes me.
On Thu, 8 Jul
Use of jlink and jpackage does NOT require that you use JPMS.
I have never made a “modular” application using JPMS, but I use jpackage all
the time (but I wasn’t making NetBeans platform apps). You just need to know
which modules from the JDK to include in the runtime, assuming you don’t need
I agree with everything Emilian said in the other post. My own experience:
1) I have never tried JPMS.
2) Yes, maven-based NetBeans Platform projects work great. I switched my
NetBeans Platform project to Maven several years ago, and haven't had any
problems with it compared to ant.
3) Yes,
Chris,
I devevelop an Ant-based Netbeans platform application
(https://github.com/jjazzboss/JJazzLab-X) and had to follow this path too.
I use only 2 external libraries that are packed in wrapper modules. I let
Netbeans build the launchers and I have a shell script that prepare the
packages
1. Don't use JPMS
2. Use Maven and nbm-maven-plugin. Documentation isn't the best but
you can do most things with it including wrapping jars (ie. Maven
Central dependencies), doing branding, doing the app.
3. I don't think anybody looked into using jlink/jpackage (which
probably would need JPMS,
10 matches
Mail list logo
