Hi,
As part of restoring compatibility in the PluginManager I realize that
the old interfaces just need to mostly be moved to maven-compat and
new names and packages for the new implementations have to be created.
So the general pattern I'm thinking of is putting the original
interfaces in maven-compat and having the implementation delegate to
the new implementation. The implementation in maven-compat can adapt
behavior and do whatever nastiness is necessary and take the primary
functionality from the new implementation. The new interfaces and
interfaces will have new names and I would like to package them to
make them OSGi friendly. So start using an "internal" package name for
the implementation. Once I start doing this I want to work with the
PAX developers (Stuart, Alin, Toni) and the maven-bundle-plugin folks
(mostly Stuart) and devise a way to generate accurate OSGi manifests
because I don't want to maintain them by hand.
Igor, is this name changing going to cause you immense grief in M2E?
You're probably going to bind to the new implementation because the
PluginManager for example is missing about 4 methods that are required
by a splattering of plugins. So the old interface will not work for
you. I figure this has to be done before 3.0 GA and I want to start
with the plugin manager code.
Any thoughts?
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
