-
Notifications
You must be signed in to change notification settings - Fork 77
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
BomContentTest disableMavenCentralCheck property #2310
BomContentTest disableMavenCentralCheck property #2310
Conversation
|
||
// Sometimes the artifacts are not yet available in Maven Central and only available in local | ||
// Maven repository. Use | ||
boolean enableMavenCentralAvailabilityCheck = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The variable name is the opposite of the property name, can we keep them consistent? Either disableMavenCentralCheck
or enableMavenCentralAvailabilityCheck
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
fd064cc
to
850d19d
Compare
// Sometimes the artifacts are not yet available in Maven Central and only available in local | ||
// Maven repository. Use this property in that case. | ||
boolean disableMavenCentralCheck = | ||
! "true".equals(System.getProperty("disableMavenCentralCheck")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should also remove !
here as well.
When some artifacts are not available in Maven Central yet, use "-DdisableMavenCentralCheck=true" system property when running BomContentTest.