-
Notifications
You must be signed in to change notification settings - Fork 15
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
Support analysis of source-containing root projects #3
Comments
Re-opening, wrong issue! Meant #2 . |
It's an important request. It would be very helpful for simple one-module projects or test projects. Currently, it is always necessary to create unnecessary submodules. |
@handstandsam I can make a PR request for this if you would consider such a change. |
@handstandsam I can also volunteer for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This plugin currently assumes that, if it is applied to the root project, the only possible relevant classpath is the buildscript classpath. However, it is possible and quite common for (generally simple, uni-modular) projects to have source in the root. An example is the Dependency Analysis Plugin.
The text was updated successfully, but these errors were encountered: