Hi tison,
As mentionned it depends the "impl" you use but for jdk (mvn4) it will be
https://github.com/apache/maven-resolver/blob/master/maven-resolver-transport-jdk-parent/maven-resolver-transport-jdk-11/src/main/java/org/eclipse/aether/transport/jdk/JdkTransporter.java#L347
(also check out the
Thanks for your reply!
> Maybe that is a bug in Nexus itself.
I ever thought of it. But according to Romain's comment, it seems the
MavenSession has the information but not printed out.
> if you feel motivated to send a pr it would be welcomed I guess.
I'd like to spend some time to see if I
interesting details
IMHO, we're back to the HTTP wire protocol between Maven CLI and repositories
not being precisely defined on edge cases
= what to put as HTTP return code, what to put as reason phrase (deprecated in
HTTP/1.1, removed in HTTP/2), and what to get from HTTP body
idea has been
Hi,
This is a valid error but if you want to see it you need to enable HTTP
frames.
For the record the error returns a HTML response with this content: *Cannot
find a matching staging profile*.
If you want to check them out it depends a bit of your maven version but
for 3.9 you just comment the
On 2024/01/04 14:00:08 tison wrote:
> Hi,
>
> When deploying artifacts to Nexus repository, 400 Bad Request can be
> one of the most confusing error code. See [1] as an example.
>
> Sonatype has a page to document some common causes of 400 Bad Request
> [2]. But I wonder if we can return an
Hi,
When deploying artifacts to Nexus repository, 400 Bad Request can be
one of the most confusing error code. See [1] as an example.
Sonatype has a page to document some common causes of 400 Bad Request
[2]. But I wonder if we can return an error message (diagnostic) along
with the error code,
