In Glassfish 4.1, I have an Enterprise Application running. I used maven to pack my ears. Dependency bans are stored inside the ear / lib folder. Among these cans, there are several cans in which there are signs of a class path.
Take an example batik-js-1.7.jarthat has Class-Path: xbean.jaras a manifest element without a version string. xmlbeans-2.3.0.jarlocated in this lib folder. Since this bank has the version string in the file name, Glassfish throws a warning:
PWC6351: In TLD scanning, the supplied resource file:<path_to_server_ear>/lib/xbean.jar does not exist.
Now, if I delete the version line when packing the ear with the configuration <fileNameMapping>no-version</fileNameMapping>from maven-ear-plugin, then for this banner the warning message does not appear anymore, but it causes the same warning for other cans, whose entries in the Manifest class have the names jar with the version.
How can I solve this warning issue? Is there anyway to remove the Path class entry from the manifest during maven packaging or tell Glassfish not to scan the manifest for the class?
source
share