jira-importer commented on issue #399: URL: https://github.com/apache/maven-deploy-plugin/issues/399#issuecomment-2771537503
**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented Well, we don't have the content type and likely will not. I will explain why: Maven hands off all logical repo interaction of artifacts to Resolver. Resolver in turn uses an implementation-agnostic approach with Wagon where the actual transport is completely opaque to Resolver. Read, it does not know that it is HTTP, SFTP, S3, etc. Wagon provides a generic API to upload and download files. All it receives is a target path on the repository, and `File`/`InputStream`/`byte[]`. No additional attribution. Now consider that the developer is able to attach **any** kind of files to the build which Resolver + Wagon. There is no way to have this kind of metadata from the POM down to Resolver and Wagon. Maybe Wagon could receive an API change which would receive generic metadata which every transport **could** process according to its protocol. But at the end, it might always boil down to `application/octet-stream` and you are back to the same situation as before. A completely different approach would be is to modify the Wagon HTTP provider in a way that you could plug in your content type resolver and provide that kind of information back to the provider. See also https://github.com/apache/maven-wagon/pull/72. [hiljusti](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hiljusti), was is the actual benefit from having the content type in your case? -- 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
