You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This component depends on Commons Lang 3 and delivers it via the shaded jenkins-test-harness-htmlunit in the normal package namespace. This is problematic because there exists a Commons Lang 3 library plugin, which also might be on the test classpath and might provide the identical classes, and based on the order of the dependencies on the classpath one or the other might be used. Ideally we would remove the dependency on Commons Lang 3, for example by relocating the packages in the shaded jenkins-test-harness-htmlunit JAR, but this is challenging for a few reasons:
This component itself exposes an ImmutablePair type in its public API (via JenkinsRule._createWebServer), so consumers would need to be adapted.
The fact that the test harness has delivered Commons Lang 3 on the classpath for a long time means that a few dozen plugins have grown to depend on it, so removing it would break upgrade for those plugins. They should be adapted ahead of time to drop their dependency on Commons Lang 3 (for example, by instead depending on the Commons Lang 2 provided by Jenkins core or standard Java Platform functionality).
The text was updated successfully, but these errors were encountered:
This component depends on Commons Lang 3 and delivers it via the shaded
jenkins-test-harness-htmlunit
in the normal package namespace. This is problematic because there exists a Commons Lang 3 library plugin, which also might be on the test classpath and might provide the identical classes, and based on the order of the dependencies on the classpath one or the other might be used. Ideally we would remove the dependency on Commons Lang 3, for example by relocating the packages in the shadedjenkins-test-harness-htmlunit
JAR, but this is challenging for a few reasons:ImmutablePair
type in its public API (viaJenkinsRule._createWebServer
), so consumers would need to be adapted.The text was updated successfully, but these errors were encountered: