jira-importer commented on issue #306: URL: https://github.com/apache/maven-install-plugin/issues/306#issuecomment-2771866645
**[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented First as you already realized in your logging output you see exactly what happens. The `finalName` will only change the name for the artifact in `target` directory. During the installation you see the result: ``` [INFO] Installing D:\Workarea\sample\sample2\test1\target\blabla.jar to C:\Users\xxx\.m2\repository\test1\test1\1.0-SNAPSHOT\test1-1.0-SNAPSHOT.jar ``` The install plugin converts the artifact to follow the naming schema: `artifactId-version-classifier.extension` which is required. Furthermore the deploy plugin does the same. Furthermore changing the naming schema is simply not possible. If it would be possible this would break the whole remote repository. Apart from that you seemed to be misunderstanding the `generatePom` configuration cause it will generate a pom file if you don't offer one yourself with `install-file` or `deploy-file` goals. So unfortunately I don't see any issue here. The goals `install-file` and `deploy-file` behave as expected based on the docs and breaking functionality is something which can of course happen if we have a major version change... -- 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
