My personal opinion: seems the main issue here is that the nbexec expects to get userdir (and cache dir) from the product/application launcher. If that's good or bad, that I guess is a question to NetBeans Platform architects, but this (as far as I can tell) is not really anything new in this release. But to me personally, if one can create a platform application, and that application will run, the current state does not seem too terrible. AFAIK we are talking about an alpha release, about thing that probably exists for a long time and if that does not affect applications based on the platform, is it really a show stopper.
Jan On Wed, Nov 15, 2017 at 2:17 PM, Jaroslav Tulach <[email protected]> wrote: > > On Wednesday, November 15, 2017, Geertjan Wielenga < > > [email protected]> wrote: > > > > > Well, the question would be why it is useful. > > > > > > And what does it prove -- and is it a requirement for release. > > > > What does it show if the launcher isn't working? That you cannot start > platform! > > When I wrote the installation proposal > https://platform.netbeans.org/articles/installation.html I described that > nbexec shall be there and shall be used to launch the platform. I don't > think much changed since then. > > Releasing something without a way to start it doesn't make it very useful, > in my opinion. My 2 Kč > -jt > > > On Wed, Nov 15, 2017 at 9:49 AM, Jaroslav Tulach < > > > > [email protected] > > > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > > > > > >> 2017-11-14 20:32 GMT+01:00 Geertjan Wielenga < > > >> [email protected] > > >> <javascript:_e(%7B%7D,'cvml','[email protected]');>>: > > >> > > >> > Calling the exe doesn’t really make sense. Who/why would one do > this. > > >> > > > >> > > >> Why it doesn't make sense? Calling platform/lib/nbexec.exe shall start > > the > > >> platform. Calling platform/lib/nbexec does so on Unix. > > >> -jt > > >> > > > > > > > > >
