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

Warning from automatically applied build-scan plugin #128

Closed
grv87 opened this issue Nov 2, 2017 · 0 comments
Closed

Warning from automatically applied build-scan plugin #128

grv87 opened this issue Nov 2, 2017 · 0 comments

Comments

@grv87
Copy link

grv87 commented Nov 2, 2017

Gradle 4.3 introduced automatic application of build-scan plugin when --scan command-line option is used.

Whenever this is used with nebula.dependency-lock (4.9.5), there is a warning from build-scan plugin:

WARNING: The build scan plugin was applied after other plugins.
The captured data is more comprehensive when the build scan plugin is applied first.

Please see https://gradle.com/scans/help/plugin-late-apply for how to resolve this problem.

The problem is with nebula.dependency-lock plugin exclusively. I tested several other plugins and they don't cause this behavior.

Original issue report: gradle/gradle/issues/3341

@grv87 grv87 closed this as completed Nov 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant