Skip to content

Conversation

@gounthar
Copy link
Contributor

Hello gitee developers! 👋

This is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:

Use API plugin instead of direct dependency

io.jenkins.tools.pluginmodernizer.ReplaceLibrariesWithApiPlugin

Use API plugins instead of direct dependency.

Copy link
Contributor

@MarkEWaite MarkEWaite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand why those API plugin dependencies were proposed. The plugin did not previously declare a dependency on any of those API's, so there is no direct library dependency that is being replaced.

Some of the libraries are already included as transitive dependencies from other plugins, but I don't see any reason to create a direct dependency on something that the plugin does not call directly.

Can you tell me if I've misunderstood something?

@gounthar
Copy link
Contributor Author

No Mark, you're spot on.
I wanted to test this recipe in a real case.
I should have used a dry run.
This recipe definitely needs some tlc.
I'll close this pr now, sorry for the noise.

@gounthar gounthar closed this Apr 25, 2025
@gounthar gounthar deleted the plugin-modernizer/replacelibrarieswithapiplugin branch April 25, 2025 18:57
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

Successfully merging this pull request may close these issues.

2 participants