-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check goal fails with multiple proxy definitions #831
Comments
Unfortunately, specifying the mavenSettingsProxyId is the only solution to this problem (currently). Allowing for multiple proxies and using the right one based on protocol (within the core engine) would be fairly low on the priority list right now - but PRs are welcome. |
I would like to create a PR but I would need to have development time approved by my employer. It would also be very low on their priority list and I'm not sure I could convince them it's worth it. |
Hi, ran into the same issue know because the admin of the jenkins configured more proxies now, so the build is failing. Tieing the id of a settings entry into the pom does not feels that good for me. Do you see any chance to reopen it and fix it? Best regards |
I'll put this back on the list of enhancements - but as I said before there are a ton of other things I'm working on. PRs are welcome. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I have two proxy definitions in Maven settings.xml. The definitions are for different protocols (HTTP and HTTPS) and can be disambiguated on that basis. The definitions have different IDs.
These are the relevant log entries:
I am using an ancient version of Maven because I work for a glacier:
Current workaround is to specify
mavenSettingsProxyId
in the POM as suggested but I'd prefer not to have to do that.The text was updated successfully, but these errors were encountered: