nacx commented on pull request #78: URL: https://github.com/apache/jclouds/pull/78#issuecomment-650318652
So, with the last update, this PR reverts back to the official gson library, which makes jclouds incompatible with OSGi. As mentioned in the different JIRA issues, we need to make a decision and find the balance between the cost of supporting OSGi in jclouds itself and being able to move forward faster. In my opinion, if we lack the OSGi expertise to do a proper job there, we should try to stop owning that and delegate that to end-users or to another community that can do it properly. In any case, this deserves a proper discussion in the jclouds dev/users mailing lists so the community is aware of the impact of the change. It would be great too, to trigger such a discussion cross-posting to jclouds-dev and karaf-dev. The Karaf community kindly took over the jclouds-karaf project and is now maintaining the Karaf and some OSGi bits. I think it makes a lot of sense to involve them in this topic and see also what is in their opinion the best way to keep OSGi support in jclouds from now on. I think reverting back to official gson should be put on hold until we have clarity on this, and we have a proper deprecation path and plan to make the community aware of the change. ---------------------------------------------------------------- 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
