[
http://jira.codehaus.org/browse/MEJB-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MEJB-30.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.2
Assignee: Benjamin Bentmann
Since plugin version 2.2, there are more configuration options for the Maven
Archiver, e.g.
{code:xml}
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
<classpathLayoutType>custom</classpathLayoutType>
<customClasspathLayout>$${artifact.groupId}-$${artifact.artifactId}-$${artifact.version}$${dashClassifier?}.$${artifact.extension}</customClasspathLayout>
</manifest>
</archive>
</configuration>
{code}
should do for the use case provided here.
> 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
> Assignee: Benjamin Bentmann
> Fix For: 2.2
>
> 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
