What problem are you trying to solve? Or, rather, what does this solve that editing netbeans,conf (by hand or programmatically) it a module that calls System.setProperty()?
-Tim On Thu, Sep 27, 2018 at 8:37 PM Laszlo Kishalmi <[email protected]> wrote: > Hi all, > > What do you think on the idea to create a simple Java agent which can > insert system properties into the JVM before NetBeans starts? > > My motivation are the following: > > 1. Sometimes you need to change some properties to debug NetBeans > behaviour. Copy and change netbeans.conf can be clumsy. (Ok, I know > what I'm doing and it is fine for me, but we have other users.) > 2. There can be a situation when some values needs to be computed, like > Java 11 were messing up with font rendering on Linux and there is no > proper default value for the antialiasing property which works on > all platform. Also dpi awareness for HiDPI would requires some logic > as well. > > Unfortunately this won't solve the currently quiet bloated command line > in netbeans.conf (just probably reduce it a bit.) > It would be good to be able to set the Memory and GC flags for the IDE > as well (though memory would be sufficient) > > What do you think? > > > -- http://timboudreau.com
