We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As of 0.7.x line, a few dependencies are specified with named fields on the extension:
0.7.x
sharedLibrary { coreVersion = "2.86" testHarnessVersion = "2.24" }
There are also a few named dependencies in the inner dependencies declaration for plugins:
sharedLibrary { pluginDependencies { workflowCpsGlobalLibraryPluginVersion = "2.8" } }
additional dependencies are added with the coordinates to the extension itself, which is similar to Gradle's dependency notation:
sharedLibrary { pluginDependencies { dependency("io.jenkins.blueocean", "blueocean-web", "1.2.4") } }
These different methods can be confusing and should be aligned and fully documented for 1.0.0 release
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As of
0.7.x
line, a few dependencies are specified with named fields on the extension:There are also a few named dependencies in the inner dependencies declaration for plugins:
additional dependencies are added with the coordinates to the extension itself, which is similar to Gradle's dependency notation:
These different methods can be confusing and should be aligned and fully documented for 1.0.0 release
The text was updated successfully, but these errors were encountered: