Skip to content
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

Closed
sam-afsa opened this issue Aug 1, 2017 · 5 comments
Closed

check goal fails with multiple proxy definitions #831

sam-afsa opened this issue Aug 1, 2017 · 5 comments

Comments

@sam-afsa
Copy link

sam-afsa commented Aug 1, 2017

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:

[INFO] --- dependency-check-maven:2.1.0:check (default) @ parent-pom ---
[WARNING] Multiple proxy definitions exist in the Maven settings. In the dependency-check configuration set the mavenSettingsProxyId so that the correct proxy will be used.
[ERROR] Failed to execute goal org.owasp:dependency-check-maven:2.1.0:check (default) on project parent-pom: Execution default of goal org.owasp:dependency-check-maven:2.1.0:check failed: Ambiguous proxy definition -> [Help 1]

I am using an ancient version of Maven because I work for a glacier:

$ mvn -version
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-18 01:22:22+1000)
Maven home: redacted
Java version: 1.7.0_75, vendor: Oracle Corporation
Java home: redacted
Default locale: en_AU, platform encoding: Cp1252
OS name: "redacted", version: "redacted", arch: "amd64", family: "windows"

Current workaround is to specify mavenSettingsProxyId in the POM as suggested but I'd prefer not to have to do that.

@jeremylong
Copy link
Owner

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.

@sam-afsa
Copy link
Author

sam-afsa commented Aug 6, 2017

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.

@Tholian
Copy link

Tholian commented Jul 5, 2018

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.
It's a pity that the issue was closed.

Do you see any chance to reopen it and fix it?

Best regards

@jeremylong
Copy link
Owner

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.

@lock
Copy link

lock bot commented Nov 27, 2018

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.

@lock lock bot locked and limited conversation to collaborators Nov 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants