Compatibility :	3.5.26
Editions :
Platforms :

By default, the Wrapper will log warnings about any missing classpath elements at the DEBUG log level. It is fairly common to want to see these generated log messages without also enabling all of the debug output. This property makes it possible to specify the log level at which the warnings will be logged.

• FATAL :
  to log at the FATAL log level.
• ERROR :
  to log at the ERROR log level.
• WARN :
  to log at the WARN log level.
• STATUS :
  to log at the STATUS log level.
• INFO :
  to log at the INFO log level.
• DEBUG :
  to log at the DEBUG log level.
• NONE :
  to never log.

The default value is DEBUG.

wrapper.java.classpath.missing.loglevel=DEBUG

If your application often has missing jars, then setting this value to NONE will disable warnings at any log level.

Starting with version 3.5.44, classpath elements which are defined as wildcards will also log a warning if the wildcard fails to match at least one file. This can happen if the directory is missing or empty.

• wrapper.java.classpath.<n> (1.0.0)

  Set the elements of the classpath passed to the JVM.

• wrapper.java.classpath.missing.loglevel (3.5.26)

  Controls the log level of the messages reporting any missing Class Path elements.

• wrapper.java.classpath.use_environment (3.4.1)

  Configures whether the Wrapper passes the generated classpath to the JVM on the Java command line or by setting the CLASSPATH environment variable.

• wrapper.java.module_path.<n> (3.5.55)

  Set locations where Java modules of the application can be found.

• wrapper.java.module_path.missing.loglevel (3.5.55)

  Controls the log level of the messages reporting any missing Module Path elements.

• wrapper.java.upgrade_module_path.<n> (3.5.55)

  Set locations of modules that replace upgradeable modules in the runtime image.

• wrapper.java.upgrade_module_path.missing.loglevel (3.5.55)

  Controls the log level of the messages reporting any missing Upgrade Module Path elements.