remove com.google.inject

[stbischof]

I had a look in the dependencies and wondered if this may can be reduced.

this would remove com.google.inject

[waynebeaton]

While I agree that we should keep dependencies as tight as possible, rearchitecting to avoid using a commonly used and supported dependency injection framework, isn't a goal of the project.

I have considered that we should probably refactor the CLI bits out of the core module along with the Guice dependency, but leave the org.jakarta.inject annotations in core (that is, make core work with any dependency injection implementation).

FWIW, the first implementation actually did use the notion of a context object. I recall that passing the context around was cumbersome, so I investigated various options, including OSGi services and e4 contexts, but decided to go with Guice.

[stbischof]

I did this to understand better what is going on. So okay with closing this.

Even when i would love osgi Services much much more.

Is there a Ticket for the cli extraktion task

[waynebeaton]

I have considered that we should probably refactor the CLI bits out of the core module along with the Guice dependency, but leave the org.jakarta.inject annotations in core (that is, make core work with any dependency injection implementation).

See #387