-
Notifications
You must be signed in to change notification settings - Fork 34
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
commons-io-unsafe-2.5 causes ParseException if missing commons-io dependency. #115
Comments
You can convert the error to a warning: |
That isn't documented over at Gradle Usage Instructions so I missed it. It's also not exactly what I'm looking for since it causes lots of output in the described case. The following is currently printed for each and every module that doesn't have the
|
There is already an issue about this: #83 The documentation about all the flags is available on Maven Central as part of the documentation artifact. In addition the Jenkins server also generates it (see link in Github Wiki). As Github does not allow to publish HTML pages as part of its Wiki, the "official" documentation is not visible on Github. There are many settings in Ant/Maven/Gradle that can be customized. The Wiki entries on Github are just a "quick" setup howto, not a documentation. |
The below exception is causing
forbiddenApis
Gradle task to fail ifcommons-io-unsafe-2.5
is added to thebundledSignatures
but the module isn't actually usingcommons-io
.While I understand why this happening, I think it shouldn't be an error or a cause for a failure of the
forbiddenApis
task. It should instead just skip thecommons-io
checks in that case.The rationale for this is that I'd like to configure
forbiddenApis
once, globally, in case of a multi-module Gradle build without having to manually add thecommons-io
checks only to modules that actually usecommons-io
.Stack trace
The text was updated successfully, but these errors were encountered: