jira-importer commented on issue #323: URL: https://github.com/apache/maven-deploy-plugin/issues/323#issuecomment-2771531229
**[Florian Brunner](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=puce)** commented This is really strange. I have a project with: groupId=mySite.myProject artifact=lib-core To avoid name clashes (e.g. when copying dependencies to a directory) and to easily identify a jar in the library view of IDEs (NetBeans, Eclipse), I renamed the artifacts to: myProject-${project.artifactId}-v${project.version} I was surprised that the deployed file name was "lib-core-0.1.jar", which really doesn't say much about the jar. I actually don't see the lookup issue. In Nexus the the files are organized like: mySite.myProject.artifactId.version Afterwards the file names should be allowed to have arbitrary names, as long as the file extensions are correct. It would be slightly more complex, but not much, I think. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
