jira-importer commented on issue #260: URL: https://github.com/apache/maven-install-plugin/issues/260#issuecomment-2771861818
**[Brill Pappin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brill)** commented Yes, your right... I just didn't have time to produce a test. Should be easy though. The exact command I'm running is: CALL mvn install:install-file -Dfile=gwt-dev-windows.jar -DgroupId=com.google.gwt -DartifactId=gwt-dev -Dversion=1.4.60 -Dpackaging=jar -Dclassifier=windows -DgeneratePom=true -DcreateChecksum=true I expect the repo to have: .m2\repository\com\google\gwt\gwt-dev\1.4.60\gwt-dev-1.4.60-windows.jar but am getting: .m2\repository\com\google\gwt\gwt-dev\1.4.60\gwt-dev-1.4.60.jar quick fix is to copy the gwt-dev-1.4.60.jar to gwt-dev-1.4.60-windows.jar and the dependencies are then resolved. However its not consistent between two on my machines: Both machines are using maven 2.0.7 with an identical environment setup (with regards to java and maven) the only difference being the actual paths. It's not clear if its some sort of environment setting that makes the difference, but because of the nature of the beast it should not be making a difference. A classifier designation should behave the same regardless of the system setup or the version of maven. The **only** thing that might change it is repository layout (which I have not set and the default new version should be used). Now, this could be some sort of bug in maven and not the plugin (maven not passing information to the plugin) but I am unable to verify that right now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
