nacx commented on pull request #75: URL: https://github.com/apache/jclouds/pull/75#issuecomment-644326086
There were some [gson hacks](https://github.com/apache/jclouds/tree/master/gson) we did to be able to make it OSGi friendly, as there are uses of an `internal` gson package we use that has been unexpected in newer versions of the library. That made it impossible to upgrade to newer versions of it. Basically, we shaded those packages and renamed them so we can safely use them in our codebase. Now we're in a different place, and I think we should revisit our OSGi support. We moved jclouds-Karaf to the Karaf project because we lack the expertise in OSGi and maintaining it was adding too much burden on us. Does the same apply here? Should we just undo this hack, go with standard gson and upgrade normally, and remove the OSGi compatibility from our list of responsibilities? This shading hack is something that can be done by users, or even by the Karaf project, probably in a better way, so I'd be in favour of undoing this at the expense of losing compatibility. The cost of maintaining this is too high for the current community. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
