nacx commented on pull request #78: URL: https://github.com/apache/jclouds/pull/78#issuecomment-649639166
I think this is not correct. The project depends on pulling a dependency from a specific repository, otherwise, it will break. The main issue here is releasing under the same `groupId` and `artifactId`, something that is not official. That is what Maven coordinates are for, so people can understand provenance and trust the libraries. We shouldnt' have a dependency called gson if it is not the official gown, nor we should depend on being connected to that particular unofficial repository. The previous approach was renaming and repackaging, just to make sure it was very clear that we were using a modified gson bundle. If this becomes a problem, then I'd consider just reverting to official gson, and make this an OSGi consumers problem. One good step, would be to contribute the updated bundle to `Servicemix`, for example that has a lot of convenience dependencies for OSGi, and pull it from there, but in the end, whatever approach we pick, we shouldn't be _replacing_ official libraries in this way. ---------------------------------------------------------------- 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
