[jira] Commented: (GERONIMO-3316) warn but don't prevent deployment if an ear's manifest cps are messed up, and provide more info on where.

["David Jencks (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642950#action_12642950 ] 

David Jencks commented on GERONIMO-3316:
----------------------------------------

We should look at the spec a bit before allowing anything into the mfcp.... some parts of the spec are very specific about only _jar_ files being allowed in certain places.  I don't have a big problem relaxing this based on a flag, but would prefer that we keep the literal spec compliant behavior as the default.

> 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, 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
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.1.4, 2.2
>
>
> 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.