You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Prasad Kashyap (JIRA)" <ji...@apache.org> on 2007/07/25 20:23:31 UTC
[jira] Updated: (GERONIMO-3316) warn but don't prevent deployment
if an ear's manifest cps are messed up, and provide more info on where.
[ https://issues.apache.org/jira/browse/GERONIMO-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-3316:
-------------------------------------
Fix Version/s: (was: 2.0-M7)
2.0.x
> warn but don't prevent deployment if an ear's manifest cps are messed up, and provide more info on where.
> ---------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3316
> URL: https://issues.apache.org/jira/browse/GERONIMO-3316
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0-M6
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.0.x
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.