Repository navigation
[JENKINS-66563] Ability for a plugin to dynamically insert classes into its classpath #12160
Description
In some (very rare) cases it is helpful to dynamically insert classes into a plugins classpath.
For example the BouncyCastle plugin currently does so that it can still work in a FIPS enabled JVM this but uses restricted APIs.
Other randomly made up use cases would be some code that had platform specific variants (but used the same packaged (e.g. multiple jars where published with 2 different qualifiers).
Originally reported by 
teilo, imported from: Ability for a plugin to dynamically insert classes into its classpath
- assignee: teilo
- status: Closed
- priority: Minor
- component(s): core
- resolution: Fixed
- resolved: 2021-09-27T15:30:30+00:00
- votes: 0
- watchers: 2
- imported: 2025-11-24
Raw content of original issue
In some (very rare) cases it is helpful to dynamically insert classes into a plugins classpath.
For example the BouncyCastle plugin currently does so that it can still work in a FIPS enabled JVM this but uses restricted APIs.
Other randomly made up use cases would be some code that had platform specific variants (but used the same packaged (e.g. multiple jars where published with 2 different qualifiers).
Activity
jenkins-infra-bot commentedon Sep 25, 2021
Raw content of original comment:
teilo is this ready to be marked as closed with the release of 2.313 or is there work yet remaining before it is closed?
jenkins-infra-bot commentedon Sep 27, 2021
Raw content of original comment:
https://github.com/jenkinsci/bouncycastle-api-plugin/releases/tag/bouncycastle-api-2.25 is released so yup!