Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.2
-
Security Level: public (Regular issues)
-
None
Description
The m1 build has an explicit manifest.mf file for this jar. We can generate an appropriate manifest in m2. The m1 manifest has classpath entries starting with ../lib/ which can be removed since all jars involved are in lib. The dependencies in the pom.xml need to be adjusted to match the explicit manifest used in the m1 build.
After this is done most likely the online-deployer won't need so many manifest classpath entries.