jira-importer commented on issue #269: URL: https://github.com/apache/maven-deploy-plugin/issues/269#issuecomment-2771520587
**[Benjamin Bentmann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bentmann)** commented > Still, the question remains why the behavior is different between the local repository and remote repositories. > More than likely, this is a misobservation. The format of the local repository is controlled by a repo layout just as with the remote repositories, and the local repo's layout is "default", i.e. the format and code paths taken by Maven to install an artifact to the local repo are the same as for remote repos. Otherwise I would like to see the log line "Installing \<src> to \<dst>" from the Maven Install Plugin. > So is this considered to be an bug or accepted behavior? > This is by design. The local/remote repos are meant as a place to share artifacts, with a well-known layout to facilitate automatic artifact lookup by its coordinates (groupId, artifactId, etc). The final name is not part of these coordinates. Enabling users to deploy artifacts with arbitrary names would simply complicate the task for tools to locate artifacts. I suggest to have a look at the [Wagon Maven Plugin](http://mojo.codehaus.org/wagon-maven-plugin/) that allows to upload artifacts without the coupling to a Maven repository. The deployment of the Deploy Plugin can be skipped if completely undesired. -- 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]
