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

Do Not Package Platform-Provided Dependencies #182

Open
sghill opened this issue Jan 24, 2021 · 0 comments
Open

Do Not Package Platform-Provided Dependencies #182

sghill opened this issue Jan 24, 2021 · 0 comments

Comments

@sghill
Copy link

sghill commented Jan 24, 2021

In order to only include necessary dependencies
As a plugin producer with dependencies
I want the jpi plugin to not include dependencies that Jenkins provides

Since v0.39.0 began using the built-in configurations for producing the jpi, transitive dependencies the platform provides must be manually excluded. For example: if a guice extension is brought in, it will bring guice with it as a transitive dependency, and that will be packaged into the jpi -- but Jenkins already provides this and it can be excluded from the archive.

One scenario to consider is when the included dependency is different than the provided dependency. Due to the way Jenkins loads classes, these will often not be considered anyway. The best course of action may be to fail and ask the user to make a decision.

See also Jenkins' Dependencies and Class Loading, Gradle's Capabilities.

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