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

Stephane Nicoll updated MEAR-75:
--------------------------------

         Assignee: Stephane Nicoll
    Fix Version/s:     (was: 2.4)
                   2.3.3

Last reported bug over here. Let's kill it! :)

> Incorrect file name in class path (in manifest) if specifying different 
> bundleFileName for module
> -------------------------------------------------------------------------------------------------
>
>                 Key: MEAR-75
>                 URL: http://jira.codehaus.org/browse/MEAR-75
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>         Environment: Windows XP SP2, Maven 2.0.7, JDK 1.5.0_12
>            Reporter: Anders Hammar
>            Assignee: Stephane Nicoll
>             Fix For: 2.3.3
>
>         Attachments: jbossaop-poc.zip
>
>
> The file name included in the class path in the generated Manifest.mf file is 
> incorrect if a different bundle file name is defined in the configuration for 
> the ear plugin. The file name used in the class path is the original file 
> name, not the defined bundle file name (which is the actual file name in the 
> created ear).
> In my POM I have:
> {code:title=pom.xml|borderStyle=solid}
>       ...
>       <dependencies>
>               <dependency>
>                       <groupId>jbossaop-poc</groupId>
>                       <artifactId>aop</artifactId>
>                       <type>jar</type>
>               </dependency>
>               ...
>       </dependencies>
>       <build>
>               <plugins>
>                       <plugin>
>                               <artifactId>maven-ear-plugin</artifactId>
>                               <configuration>
>                                       <archive>
>                                               <manifest>
>                                                       
> <addClasspath>true</addClasspath>
>                                               </manifest>
>                                       </archive>
>                                       <modules>
>                                               <jarModule>
>                                                       
> <groupId>jbossaop-poc</groupId>
>                                                       
> <artifactId>aop</artifactId>
>                                                       
> <bundleFileName>aop-${pom.version}.aop</bundleFileName>
>                                                       
> <includeInApplicationXml>true</includeInApplicationXml>
>                                               </jarModule>
>                                       </modules>
>                               </configuration>
>                       </plugin>
>               </plugins>
>       </build>
> {code}
> In the resulting ear file, the included artifact 'aop-1.0-SNAPSHOT.jar' has 
> been renamed to 'aop-1.0-SNAPSHOT.aop'. However, in the Manifest.mf (in the 
> ear) the class path incorrectly specifies:
> Class-Path: aop-1.0-SNAPSHOT.jar
> Attached is a multi-module project that should reproduce this.

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

        

Reply via email to