Quarkus build does not use the proxy settings in maven settings.xml

Describe the bug

In case of changing the quarkus version the first build has to be called with implicit java proxy settings on the command line in order to get a build behind proxy.

Maven downloads all the necessary jars, but some of them are downloaded by the quarkus plugin which does not honor the setting.

Expected behavior

in case the setting is set in maven, every plugin should honor it.

Actual behavior

[INFO] 
[INFO] --- maven-surefire-plugin:3.0.0-M7:test (default-test) @ sc-datasource-rest ---
[INFO] Tests will run in random order. To reproduce ordering use flag -Dsurefire.runOrder.random.seed=201451074564952
[INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
[INFO] 
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running RestDataSourceTest
Downloading from central: https://repo.maven.apache.org/maven2/io/quarkus/quarkus-resteasy-reactive-kotlin/2.12.1.Final/quarkus-resteasy-reactive

Stuck here and times out.

How to Reproduce?

Delete quarkus version and rebuild something with tests inside.

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.12.1.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[smil2k]

<?xml version="1.0" encoding="UTF-8"?>

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

  <proxies>
    <proxy>
      <id>p</id>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy</host>
      <port>3128</port>
    </proxy>
  </proxies>
</settings>

[aloubyansky]

Haven’t been able to reproduce it so far. Here is what I tried:

• setup a local Nexus server running on port 8085
• deployed Quarkus version 999-SNAPSHOT to the local Nexus
• created a settings.xml with
  • local repo pointing to my project’s target/local-repo to make sure it’s cleaned with mvn clean test
  • configured Maven repositories in an active by default profile for my local Nexus, except with the port 8083 instead of 8085 (having nothing running on 8083)
  • configured my local proxy
• launched a local LittleProxy that intercepts requests that go to localhost:8083 and redirects them to localhost:8085
• launched my project’s build with mvn clean test -s settings.xml

The idea was that if the Quarkus resolver was not applying the proxy settings to the configured repos I would see a request to a Maven repo with port 8083 which would fail because nothing is listening on that port. That didn’t happen though. I get a successful test run.

I see it’s failing on quarkus-resteasy-reactive-kotlin in your case. Which is a conditional dependency that gets activated having quarkus-resteasy-reactive and quarkus-kotlin in the project, which I also have and see quarkus-resteasy-reactive-kotlin being downloaded through my proxy.