quarkus: 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
3.2.1.Final
Build tool (ie. output of mvnw --version
or gradlew --version
)
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 28 (14 by maintainers)
Ok, thanks for the info. The quarkusRegistryClient isn’t relevant for install, btw, in case you run these commands yourself.
It would be even more convenient if
quarkus
CLI would honour the environment variableHTTP_PROXY
andHTTPS_PROXY
.