[ http://jira.codehaus.org/browse/MNG-1676?page=comments#action_78889 ] Wendy Smoak commented on MNG-1676: ----------------------------------
Okay, now I see the duplicate extension in the filename. It does look like either a bug or incorrect documentation in the xsd, but it's still unrelated to the original issue here. Thanks for bringing it up on the user list... assuming no one has an explanation for it, you can open a new 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
