splatch commented on pull request #88: URL: https://github.com/apache/maven-resolver/pull/88#issuecomment-845252586
> @splatch Your proposal is to move the Guice/Sisu binding to a separate module to have more control over for non-DI users? I made one attempt with https://github.com/cstamas/maven-resolver/pull/4 - it makes guice/sisu optional. Sadly it still leaves implementation classes invisible for use under OSGi. Above PR allows all maven-resolver osgi bundles become active, yet it still does not let actual resolver service to be run. I guess we would need to consult this with someone working on m2e to see how they approach this issue (I suppose they are fine as long as sisu stays). Anyhow, I can think of few ways how we could work-around that (sisu index in META-INF consist list of classes available for IoC). -- 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: [email protected]
