Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0-M6, 2.0-M7, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
-
Security Level: public (Regular issues)
-
None
Description
DeploymentContext.getCompleteManifestClassPath figures out the whole set of jars in an ear in a modules classpath. If somethings missing it throws an exception and prevents deployment. We need a switch to be more lenient, and we need to provide more info when there's a problem on which jar has the problem and how we found it.
Thanks to David Harbige on the user list for pointing out that this is a big usability problem.