jira-importer opened a new issue, #399: URL: https://github.com/apache/maven-deploy-plugin/issues/399
**[J.R. Hill](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER281198)** opened **[MDEPLOY-289](https://issues.apache.org/jira/browse/MDEPLOY-289?redirect=false)** and commented Heya folks! I work with Amazon/AWS as a build engineer. I'm researching how much effort it would take to give our developers the option to build with Apache Maven. (opposed to other tools like Gradle) Right now we are blocked from an easy usage of Apache Maven because no "Content-Type" header is sent in requests, and it violates some expectations of our proxies. We use clones of maven repositories so we can have some governance controls across our codebase and services. We have ways we could work around around it - we could consider loosening our proxies, or adding special handling. We could also build our own plugin that does things the way we want. That said, I'd prefer to use off-the-shelf tools, and to be able to contribute to open source projects where possible. I looked a bit into how this plugin is performing deployments. I see it's using Aether for the deploy action, and see what looks like some complicated history there between Sonatype and Eclipse around the Aether project. I'm not sure if this is possible to fix this _in_ the Maven Deploy Plugin or if it'd have to go deeper into the Aether code base. Any pointers? I'd love to take a crack at something here. --- **Affects:** 2.8.2 -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
