On 11/03/2008, at 6:52 AM, John Casey wrote:
I'd propose to resolve this using a mechanism borrowed from OSGi: we
should create some sort of manifest of classes to be exported from
the extension for use by the rest of Maven. This file could be
optional, and the existing behavior would result. But if the file
were present, it would name all the classes (and class patterns?) in
the extension artifact (and possibly its dependencies) to "export"
into the main maven ClassRealm(s) for use by plugins. This is a
relatively small change to Maven's extension mechanism for 2.1, and
would restore many of the best features of the old extension
functionality without incurring the blind incompatibilities of the
old system.
Anyone have any thoughts on this?
It was really off the top of my head, but it sounds like the right
approach. So you're saying this would be a maven specific feature, not
a general plexus one?
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
