[
https://issues.apache.org/jira/browse/MDEPLOY-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453527#comment-17453527
]
J.R. Hill commented on MDEPLOY-289:
-----------------------------------
{quote}Read [https://datatracker.ietf.org/doc/html/rfc7231#section-3.1.1.5]
{quote}
Yeah I agree on the point that something we're doing (or some http library or
something somewhere) is non-compliant if we're not handling this.
I think this is something we can fix on our side.
I think also Julian has a good point in "set it if you know it" -- looking
around more, I think Michael is right that either Resolver or Wagon might be
the place that could be updated. I'm not sure where yet where, but I'll look
into it this coming week.
> No "Content-Type" header in PUT requests when deploying.
> --------------------------------------------------------
>
> Key: MDEPLOY-289
> URL: https://issues.apache.org/jira/browse/MDEPLOY-289
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy
> Affects Versions: 2.8.2
> Environment: Mac/Linux
> Reporter: J.R. Hill
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
