I think it largely depends on if you want service injection or not. If
your "component" requires other services it might make sense to make
it plexus-managed.
As an example, I have been irritated the the plexus-io collections are
themselves plexus-components. This is because they get the plexus
lo
I'm working on a plugin where there's a use-case in which the user
will want to add something to the plugin's classpath and then
configure a class.
Is there any advantage to using plexus injection for this as opposed
to just ordinary classpath fishing for a named class?
--
