geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <j...@apache.org>
Subject [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.
Date Fri, 07 Nov 2008 15:14:45 GMT

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

Joe Bohn commented on GERONIMO-3316:
------------------------------------

Can somebody (Jeff?) please clarify why support for a directory only specification rather
than specific jars?  Why can't you just use /lib and avoid having to code manifest classpath
at all if it is a problem to specify each jar name?

If it is directory support and other more lenient support is necessary (beyond listing all
of the problems) ... can you please provide more details on what you would like to see? In
addition to directory support there was another reference to permitting missing jars (presumably
without error) and allowing the deployment to succeed.  Are there other areas that you would
like more lenient,  non-spec compliant interpretation?

If we do support this it will be via a command line param, -DXorg.apache.geronimo.deployment.LenientMFCP=true
which I have on my local image rather than a plan addition ... now we have to figure out what
that exactly means.   Thanks.

> 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: Joe Bohn
>             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.


Mime
View raw message