Maven 2.x EJB Plugin

Make it possible to put full file name in manifest classpath

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.1
  • Fix Version/s: 2.2
  • Component/s: None
  • Labels:
    None
  • Environment:
    Maven 2.0.7
  • Number of attachments :
    1

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Siefert added a comment -

My experience with this is a little lackluster--as could any developer willing to help improve this plugin. Could you provide more discrete examples of what you are asking for? Thanks!

Show
David Siefert added a comment - My experience with this is a little lackluster--as could any developer willing to help improve this plugin. Could you provide more discrete examples of what you are asking for? Thanks!
Hide
Permalink
Martin von Zweigbergk added a comment -

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.

Show
Martin von Zweigbergk added a comment - 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.
Hide
Permalink
Benjamin Bentmann added a comment -

Since plugin version 2.2, there are more configuration options for the Maven Archiver, e.g.

<configuration>
  <archive>
    <manifest>
      <addClasspath>true</addClasspath>
      <classpathLayoutType>custom</classpathLayoutType>
      <customClasspathLayout>$${artifact.groupId}-$${artifact.artifactId}-$${artifact.version}$${dashClassifier?}.$${artifact.extension}</customClasspathLayout>
    </manifest>
  </archive>
</configuration>

should do for the use case provided here.

Show
Benjamin Bentmann added a comment - Since plugin version 2.2, there are more configuration options for the Maven Archiver, e.g. 
<configuration>
  <archive>
    <manifest>
      <addClasspath>true</addClasspath>
      <classpathLayoutType>custom</classpathLayoutType>
      <customClasspathLayout>$${artifact.groupId}-$${artifact.artifactId}-$${artifact.version}$${dashClassifier?}.$${artifact.extension}</customClasspathLayout>
    </manifest>
  </archive>
</configuration>
should do for the use case provided here.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.