forked from abayer/gradle-hpi-plugin
-
Notifications
You must be signed in to change notification settings - Fork 50
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
0.39.0 Migration Guide #139
Milestone
Comments
See jenkinsci/templating-engine-plugin#64 for an example migration |
Closed
sghill
added a commit
to sghill/jira-trigger-plugin
that referenced
this issue
Jan 24, 2021
Migrate deprecated configurations to recommended replacements. jenkinsci/gradle-jpi-plugin#139
sghill
added a commit
to sghill/jira-trigger-plugin
that referenced
this issue
Jan 24, 2021
Migrate deprecated configurations to recommended replacements. jenkinsci/gradle-jpi-plugin#139 jenkinsci/gradle-jpi-plugin#181
This was referenced Oct 27, 2021
6 tasks
janssen-tiobe
pushed a commit
to tiobe/tics-intellij-plugin
that referenced
this issue
Apr 6, 2023
This includes the following changes: - Upgraded to Gradle 6.5 everywhere, except for the IntelliJ plugin (it uses Gradle 5.6.2 for now due to warnings when using Gradle 6.x) - Adjusted the Jenkins plugin to use Gradle-style dependencies; see jenkinsci/gradle-jpi-plugin#139 - Fixed the Jenkins makefile to run CheckStyle for every build and resolved all existing violations - Fixed repository URLs (Nexus) to use https instead of http Reviewed by @reniers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This migration guide accompanies version 0.39.0, a major release that uses Gradle Module Metadata to improve dependency resolution.
Prerequisites
Gradle
Gradle 6.0 or later is required.
Older projects can ensure a smooth experience by upgrading to Gradle 6.0 or later with gradle-jpi-plugin 0.38.0 before moving to 0.39.0.
Breaking Changes
Users of these features need to make some changes for 0.39.0.
Configurations
Previous versions of gradle-jpi-plugin included three custom configurations that have now been replaced with standard configurations from the java-library plugin.
jenkinsPlugins
implementation
jenkinsTest
testImplementation
optionalJenkinsPlugins
Optional Example
If you previously had an optional dependency declared:
A feature variant now needs to be registered. The same dependency will be declared on the feature's configuration:
The older configurations exist for now, but will fail with a friendly error message if used. All three configurations will be removed in a future release.
Sources and Javadoc
If
jenkinsPlugin.configurePublishing = false
, the plugin no longer wires up tasks to create source and javadoc jars. This can be added back by configuring the Java Extension:java { withJavadocJar() withSourcesJar() }
war
Task ConfigurationThis release stops applying the
war
plugin and instead defines ajpi
task of typeWar
. This means any configuration that was previously defined forwar
must be moved tojpi
. See jenkinsci/job-dsl-plugin#1244 for an example.Notable Differences
These changes alter output, but are not expected to break anything or require user action.
License Generation
The
generateLicenseInfo
task has been improved in two ways:Here's an example of the output for a dependency
org.example:myclient:2.0
without a POM:POM Generation
POMs are now generated by the maven-publish plugin and can appear different in two ways after upgrade:
provided
scope dependencies are no longer includedThe text was updated successfully, but these errors were encountered: