P3
As per discussion with build team:
1.) The papplauncher is only used internally, as a resource of jpackage. It's name should be more descriptive like jpackageapplauncher.
2.) The artifacts created should not be exposed in jdk/bin directory
3.) The associated library, currently 'jpackage', is only loaded by papplauncher, and should be renamed to make clear that this is not a library used by jpackage itself.
4.) All source files used to create this executable and it's library should be put in the appropriate directories corrisponding to it's new name.
5.) On windows, we create both a windowed and a console version of the app, and use one or the other depending if CLI "--console" is used.
Like "java" and "javaw", the console version should be the unmodified name, and the non-console version should be modified name (appending 'w' to the name) even if the non-console version is the default.
6.) in Lin-jdk.jpackage.gmk we create these artifacts, then copy them to the correct place using SetupCopyTargetFiles macro. Instead we should build them in the correct place and not have to copy them.
1.) The papplauncher is only used internally, as a resource of jpackage. It's name should be more descriptive like jpackageapplauncher.
2.) The artifacts created should not be exposed in jdk/bin directory
3.) The associated library, currently 'jpackage', is only loaded by papplauncher, and should be renamed to make clear that this is not a library used by jpackage itself.
4.) All source files used to create this executable and it's library should be put in the appropriate directories corrisponding to it's new name.
5.) On windows, we create both a windowed and a console version of the app, and use one or the other depending if CLI "--console" is used.
Like "java" and "javaw", the console version should be the unmodified name, and the non-console version should be modified name (appending 'w' to the name) even if the non-console version is the default.
6.) in Lin-jdk.jpackage.gmk we create these artifacts, then copy them to the correct place using SetupCopyTargetFiles macro. Instead we should build them in the correct place and not have to copy them.