-
Notifications
You must be signed in to change notification settings - Fork 11
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
Excluded coordinates should not be queried in the OSS Index ? #66
Comments
@dvbarnz do you have a more complete example showing this exclusion is not working? Dependency collection should respect these rules, but its hard to tell why its not for you w/o a concrete example showing it is not. |
Hi there @jdillon - this should illustrate what the issue is. Apologies if it wasn't clear to start with. |
@dvbarnz Thx, that helps. The reasoning here is that (as the impl stands today) the If you had used the dependency exclusions mechanism it would have not included the coordinate in the request to the service. This is why I wanted to see an example so I could confirm how you are configuring Maven ;-) ATM I don't see any reason why the application of |
Great, thanks @jdillon . Yes, I realised the original description was a bit ambiguous but for some reason I couldn't find the edit button to add a bit more context at the time. :) |
Using config similar to below (obfuscated) - the excluded artefact is still included in the network request to query the index.
The excluded artefact is one of our internal dependencies. We do not wish for this information to be transmitted outside of our networks.
The text was updated successfully, but these errors were encountered: