Open
Description
openedon Apr 24, 2024
Describe the bug
We are on Quarkus 2.1. We want to update to Quarkus 3.8.
We are in an enterprise environment and have in our maven settings our own nexus repository for maven.
This is all configured in our settings.xml - and mvn in our IDEs and terminals always respects this proxy.
When I try to use quarkus in my terminal and want to use 'quarkus update x', it prints this error message:
Could not transfer artifact io.quarkus.registry:quarkus-registry-descriptor:json:1.0-SNAPSHOT from/to registry.quarkus.io (https://registry.quarkus.io/maven):
transfer failed for https://registry.quarkus.io/maven/io/quarkus/registry/quarkus-registry-descriptor/1.0-SNAPSHOT/quarkus-registry-descriptor-1.0-SNAPSHOT.json
I tried adding our own domain in the registry, but it's domain is:
nexus.webapp.intern.repos/groups/maven
when I try that, Quarkus says, '/' is an illegal character in host-name.
What can I do?
Expected behavior
quarkus update respects the configured proxy the settings.xml when using mvn
Actual behavior
quarkus cli doesn't respect proxy
How to Reproduce?
No response
Output of uname -a
or ver
No response
Output of java -version
java 17
Quarkus version or git rev
quarkus 2.14
Build tool (ie. output of mvnw --version
or gradlew --version
)
mvn 3.8.6
Additional information
No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment