You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dave Sinclair (JIRA)" <ji...@codehaus.org> on 2008/07/31 22:17:26 UTC

[jira] Commented: (MWAR-116) The outputFileNameMapping config creates bad dependency files in WEB-INF/lib

    [ http://jira.codehaus.org/browse/MWAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143798#action_143798 ] 

Dave Sinclair commented on MWAR-116:
------------------------------------

I have 2.1-alpha-2-SNAPSHOT and am still seeing this problem. Here is the section from my pom. Any ideas?

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-war-plugin</artifactId>
                <version>2.1-alpha-2-SNAPSHOT</version>
                <configuration>
                    <archiveClasses>true</archiveClasses>
                    <outputFileNameMapping>${artifact.artifactId}.${artifact.extension}</outputFileNameMapping>
                    <filters>
                        <filter>src/main/filters/${wile.filter.properties}</filter>
                    </filters>
                    <webResources>
                        <webResource>
                            <directory>${basedir}/src/main/webapp/WEB-INF</directory>
                            <includes>
                                <include>beans.xml</include>
                                <include>web.xml</include>
                            </includes>
                            <targetPath>WEB-INF</targetPath>
                            <filtering>true</filtering>
                        </webResource>
                    </webResources>
                </configuration>
            </plugin>

> The outputFileNameMapping config creates bad dependency files in WEB-INF/lib
> ----------------------------------------------------------------------------
>
>                 Key: MWAR-116
>                 URL: http://jira.codehaus.org/browse/MWAR-116
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-1
>            Reporter: Chris Moesel
>            Assignee: Olivier Lamy
>             Fix For: 2.1-alpha-2
>
>         Attachments: mwar_93_webapp.zip
>
>
> I've tried using the new outputFileNameMapping feature (MWAR-93) by adding the following to my POM:
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-war-plugin</artifactId>
>   <version>2.1-alpha-1-SNAPSHOT</version>
>   <configuration>
>     <outputFileNameMapping>${artifactId}.${extension}</outputFileNameMapping>
>   </configuration>
> </plugin>
> This results in really oddly named files in my web-inf/lib now.  A typical example:
> org.springframework-mywebapp.null
> So, the resulting files are really mapped more like: ${groupId of the dependency}-${artifactId of my war module}.null
> I've attached an example Maven 2 project that demonstrates this.  Just run "mvn package" and look at the result in target.

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