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
I want to request that docusign-esign-java be shaded using maven-shade-plugin.
Our company is currently adopting the DocuSign Java SDK and found that docusign-esign-java is not shaded. This is especially concerning, as docusign-esign-java is not a thin client and have many external dependencies. Particularly for us, docusign-esign-java is pulling in org.glassfish.jersey.media:jersey-media-json-jackson which conflicts with org.glassfish.jersey.media:jersey-media-jaxb (which is being pulled in by io.dropwizard). Please see here on why this would be an issue.
I would assume most (if not all) enterprise Java applications would utilize a Java framework, including Jersey. I would see this being an issue for many other companies that are trying to integrate DocuSign into their system.
I have already confirmed that shading docusign-esign-java resolves any conflicts.
Please let me know if I can provide any supplementary detail. Thank you for taking the time to read through this 🙂.
@rjdkolb@jglassenberg I ended up hosting my own shaded artifact on JFrog. Adding maven-shade-plugin to the pom.xml would shade the transitive dependencies.
@davidsubskribe I also tried pulling in 3.19.0 as @mmallis87 suggested, but I received the same Maven build error. I am experimenting with excluding signature files as you mentioned.
Not sure if that's the best option to go with (according to an answer by MattW, but time will tell.
If anyone else finds an elegant solution for this, please do share it!
Activity
jglassenberg commentedon Oct 25, 2021
Hi David,
Thanks for sharing this. I saw your post this weekend and am touching base with our engineers internally to evaluate this issue.
rjdkolb commentedon May 24, 2022
This would be a fantastic feature.
We have a lot of dependancy clashes because of the docusign-esign-java client.
davidsubskribe commentedon May 26, 2022
@rjdkolb @jglassenberg I ended up hosting my own shaded artifact on JFrog. Adding
maven-shade-pluginto thepom.xmlwould shade the transitive dependencies.mmallis87 commentedon May 27, 2022
The decision was to use uber jar. Here is how you can get 3.19.0 with Maven (similar syntax exits for Gradle and others):
davidsubskribe commentedon May 27, 2022
@mmallis87 I tried pulling
3.19.0into our project as you suggested and my Maven build failed with the following error:I'm wondering if this error shows up for anyone else.
My suspicion is that manifest signature files under
META-INFneed to be excluded from shading, as can be found here.Version 3.19.0 release (#233)
jacobbrokaw commentedon Jun 28, 2022
@davidsubskribe I also tried pulling in
3.19.0as @mmallis87 suggested, but I received the same Maven build error. I am experimenting with excluding signature files as you mentioned.Not sure if that's the best option to go with (according to an answer by MattW, but time will tell.
If anyone else finds an elegant solution for this, please do share it!