Currently self-contained applications created by the javapackager are not passed into the application when specified at build time. This is at odds with how the JNLP Processing works. We should be closer to consistent.

One quirk is that the executables for the self contained application do pass this arguments into the main class. This could be useful for some applications so a compromise must be reached. The current plan is that if a self-contained application is launched without any arguments, we will then look to see if the bundling contained default command line arguments. If so those will be passed into the application. If the application is launched with command line arguments from the user then those will be used and the build time defaults will not be consulted. There will be no "escape hatch" to force an application to launch without any command line arguments if there are defaults specified at build time.

Note that the htmlParameters and params passed into JNLP classes will not receive similar treatment at this time and will continue to be different. that is because those two arguments are directed at applets, whereas command line arguments are directed at generic applications.