geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
Date Mon, 02 Feb 2009 14:25:59 GMT

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

Ivan commented on GERONIMO-4251:
--------------------------------

Thanks, Frank
One thing I want to confirm is that whether all the entries in the class-path be relative
URLs, which means /myLibs and /x/aDirectory in your example should be something like myLibs
and x/aDirectory ?


> Class-Path entry in WAR manifest didn't work if entry is a directory
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-4251
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4251
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>         Environment: Geronimo 2.1.2 on Windows XP
>            Reporter: Frank Meilinger
>            Assignee: Ivan
>             Fix For: 2.1.4, 2.2
>
>
> Hi,
> it's not possible to define an Class-Path element in the WARs manifest, if it's a directory.
 I try to access jar files packed in the EARs lib/ directory from within a WAR module.
> e.g. this will work:
> Class-Path: a.jar b.jar
> but this doesn't work:
> Class-Path: lib/
> If a directory is specifyed, I receive the following error:
> 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path
> entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../
> org.apache.geronimo.common.DeploymentException: Manifest class path entries must
>  end with the .jar extension (J2EE 1.4 Section 8.2): module=../
>         at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath
> (DeploymentContext.java:419)
> ...
> I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely
allows directories in manifest Class-Path entries. 
> See discussion:
> http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html

-- 
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