MANIFEST.MF: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 22: | Line 22: | ||
The <tt><dependency-name></tt> is the name of the module to add to the class path of the deployment. To specify that the dependency is optional, add the "<tt>optional</tt>" flag. To specify that the dependency is to be re-exported, add the "<tt>export</tt>" flag. | The <tt><dependency-name></tt> is the name of the module to add to the class path of the deployment. To specify that the dependency is optional, add the "<tt>optional</tt>" flag. To specify that the dependency is to be re-exported, add the "<tt>export</tt>" flag. | ||
For more details on WildFly modules see: | For more details on WildFly modules see: | ||
Latest revision as of 22:49, 10 March 2016
Overview
If you modify the MANIFEST.MF file, make sure to include a newline character at the end of the file.
MANIFEST.MF and WildFly
WildFly module dependencies can be added in the JAR's MANIFEST.MF file as follows:
Manifest-Version: 1.0 Dependencies: org.jboss.logmanager Class-Path: OrderManagerEJB.jar
The Dependencies: syntax is as follows:
Dependencies: <dependency-name> [optional] [export][, <dependency-name> [optional] [export][, ...]]
The <dependency-name> is the name of the module to add to the class path of the deployment. To specify that the dependency is optional, add the "optional" flag. To specify that the dependency is to be re-exported, add the "export" flag.
For more details on WildFly modules see:
The configuration can be generated with Maven, for more details see: