jcompagner commented on PR #284: URL: https://github.com/apache/httpcomponents-client/pull/284#issuecomment-1276211362
> OSGi bundles can be maintained outside of the project by people who understand OSGi and care about it, while we can focus on things we understand and care about. but this means forking the product.. why would you support or promote that? Because it is not something that you can configure outside of it differently, really the manifest needs to be what it is. Also if you just generate it, there is not much to maintain, i maintain a lot of libs and eclipse plugins I almost never have to do anything to really maintain it.. (i guess only with major releases that have a lot of changes of dependencies and new packages) Besides that Eclipse is already a consumer of this, if the maven central artifacts would have OSGi entries then if something is wrong, the Eclipse plugin that includes this would right away notice this and then make a patch, just for example what they did yesterday because i noticed something was a bit too strict (SLF4J import) on the forked libs: https://git.eclipse.org/r/c/orbit/orbit-recipes/+/196310 But still you talk about that there where all kinds of bugs or problems.. but still i have no idea what those where.. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
