[ http://jira.codehaus.org/browse/MNG-1676?page=comments#action_78883 ] Wendy Smoak commented on MNG-1676: ----------------------------------
> The xsd states that the finalName includes the extension, yet as the original > issue indicates, the extension is ignored. No, the original issue indicates that finalName is completely ignored by the install plugin. This is by design. The documentation looks correct to me. If you have a question, please bring it up on the user list and give a link to this issue. > finalName not taken into account in install > ------------------------------------------- > > Key: MNG-1676 > URL: http://jira.codehaus.org/browse/MNG-1676 > Project: Maven 2 > Issue Type: Bug > Affects Versions: 2.0 > Reporter: Wim Deblauwe > Assigned To: Brett Porter > > Hi, > when I set <finalName/> in my pom.xml, the install plugin does not take this > name into account. > Just for testing I added <finalName>test.jar</finalName> to the pom.xml of a > custom plugin of mine. When doing 'mvn install', I get this: > [INFO] Installing > Y:\wimd_test_vob\modules\maven-plugins\maven-nmake-plugin\target\test.jar.jar > to C:\Documents and > Settings\WIMD\.m2\repository\com\barcoview\mavenplugin\maven-nmake-plugin\1.0-SNAPSHOT\maven-nmake-plugin-1.0-SNAPSHOT.jar > I was hoping it would install to the directory it does, but as test.jar. > regards, > Wim -- 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
