You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin von Zweigbergk (JIRA)" <ji...@codehaus.org> on 2008/09/22 18:09:45 UTC

[jira] Updated: (MEJB-30) Make it possible to put full file name in manifest classpath

     [ http://jira.codehaus.org/browse/MEJB-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin von Zweigbergk updated MEJB-30:
--------------------------------------

    Attachment: MEJB-30.zip

The attached file illustrates the problem. The resulting ear file contains two files - test-ejb-1.0.jar and test-jar-1.0.jar, but the class path entry in the manifest of the ejb jar refers to jar-1.0.jar, which of can not be found.

> Make it possible to put full file name in manifest classpath
> ------------------------------------------------------------
>
>                 Key: MEJB-30
>                 URL: http://jira.codehaus.org/browse/MEJB-30
>             Project: Maven 2.x Ejb Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1
>         Environment: Maven 2.0.7
>            Reporter: Martin von Zweigbergk
>         Attachments: MEJB-30.zip
>
>
> The ear and war plugins have a parameter called fileNameMapping. When this is set to "full", the groupId of any dependency is prefixed to the filename before packaging it in the ear or war file. To make this feature useful with included EJBs, it must be configurable to prefix the filename in the same way in the classpath entries in the manifest file of ejb jars.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira