On Mon, 13 Sept 2021 at 08:55, Luff, Chris <[email protected]> wrote: > Hey Neil, I love solving problems and producing our own may be the path of > least resistance, but I wonder if working with the existing JPackage so it > closer matches our needs may be a good choice. I’m sure NetBeans cannot be > the only solution that needs to solve these issues? > > JEP-8208405[1] in progress is looking to enhance with the ability exclude the > runtime.
Thanks for the feedback. However, excluding the runtime is far from the only problem. JPackage just does about 75% more than we'd need, the launcher mechanism particularly. I'm not sure how easy that would be to support launching NetBeans / platform in a non-hacky way, or how much solving that would mesh with needs elsewhere. And without that, we're mainly talking about deferring to native packaging tools. Bear in mind, we do already have our own, in the form of NBI. I was thinking this more as a possible (and simpler) alternative to that, that takes a similar approach to JPackage in terms of using native packaging tools. There are a bunch of people, including myself, who have been doing similar with the platform for a while. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
