-
Bug
-
Resolution: Fixed
-
P3
-
7u6
Reported in the Oracle forums:
=======================
example printed by javafxpackager is misleading:
Sample usages:
javafxpackager -createjar -appclass package.class
-srcdir classes -outdir out -outfile outjar -v
Packages the content of the classes directory to outjar.jar,
sets the application class to package.class.
The use of "package.class" suggests that a .class file is being specified. But what is expected is a fully qualified class name, i.e.: package.name.ClassName Since the standard convention is for packages to be lowercase and class names to be CamelCase the lowercase .class in the sample through me off.
=======================
example printed by javafxpackager is misleading:
Sample usages:
javafxpackager -createjar -appclass package.class
-srcdir classes -outdir out -outfile outjar -v
Packages the content of the classes directory to outjar.jar,
sets the application class to package.class.
The use of "package.class" suggests that a .class file is being specified. But what is expected is a fully qualified class name, i.e.: package.name.ClassName Since the standard convention is for packages to be lowercase and class names to be CamelCase the lowercase .class in the sample through me off.