• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: docker-build-step-plugin
• Labels:

  None

[JENKINS-28755] docker-java dependency should be shaded in docker-build-step

Oleg Nenashev created issue - 2015-06-04 20:40

Oleg Nenashev made changes - 2015-06-04 20:42

Component/s		New: docker-build-step-plugin [ 18721 ]
Component/s	Original: docker-traceability-plugin [ 20626 ]
Assignee	Original: Oleg Nenashev [ oleg_nenashev ]	New: vjuranek [ vjuranek ]
Description	Original: Issues: * docker-java does not guarantee the backward compatibility across versions (there're binary compatibility violations in the latest releases) * sharing of incompatible lib as a plugin is not safe, so we want to setup the shading of the entire docker-java lib * if we leave the plugin as is, there's may be a conflict with other plugins using docker-java Solution: * Shade the docker-java library in the plugin I'm aware that this issue is a blocker for 1.0 release. Need some help to elaborate it.	New: Issues: * docker-java does not guarantee the backward compatibility across versions (there're binary compatibility violations in the latest releases) * sharing of incompatible lib as a plugin is not safe, so we want to setup the shading of the entire docker-java lib * if we leave the plugin as is, there's may be a conflict with other plugins using docker-java In my case I see the conflict with docker-traceability plugin, which causes classloading errors in build-step, because Jenkins takes the higher version. I also have JENKINS-28693 for docker-teaceability

Oleg Nenashev made changes - 2015-06-04 20:43

Link

New: This issue is related to JENKINS-28693 [ JENKINS-28693 ]

R. Tyler Croy made changes - 2016-07-25 23:51

Workflow

Original: JNJira [ 163611 ]

New: JNJira + In-Review [ 181309 ]