Thanks for investigating! We don't have many options. I'd say, first of all we should open a PR with the fix and ask for a release, even if we know it is unlikely to be consdered.
Then, the options that come to my mind are: * Fork the project into a subfolder in jclouds-karaf and release it with the fix. * Use the maven-shade-plugin and its ManifestResourceTransformer [1] to produce a patchef versionon the fly in each build. Both have pros and cons. Perhaps the second one is the more direct and easy one for us, but has the con of reviewing the shaded manifest every time we change the version of the offending jar. The first one requires us to release our own version of the jar and probably maintain it to keep it in sync with the other dependencies. Any other ideas or thoughts? [1] https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html#ManifestResourceTransformer El 18 ago. 2016 5:39 a. m., "Andrew Phillips" <andr...@apache.org> escribió: > https://issues.apache.org/jira/browse/JCLOUDS-1156 >> > > An update: https://issues.apache.org/jira/browse/JCLOUDS-1156?focusedCo > mmentId=15425861&page=com.atlassian.jira.plugin.system. > issuetabpanels:comment-tabpanel#comment-15425861 > > TL;DR: It looks like we know what the issue is. However, the "correct" > solution requires a change in a no-longer-maintained external project. > Hmm... > > Regards > > ap >
