An extension should still work there, as long as the things are
instantiated in the extension itself - sounds like doing it in the
plugin is the problem. Is there a reason it must be there, or can you
use the plexus component lifecycle to do the instantiation?
Other than extensions, you can use plugin dependencies in most cases
(though doesn't sound suitable here). You might also be able to use
the plugin context to share the values instead of an extension
(though not if you are introducing new types, so probably not the
case here also).
- Brett
On 23/04/2007, at 3:43 PM, Jochen Kuhnle wrote:
Hi,
we use several plugins that need to share data. This as done by
creating an extension containing some "container" classes, and
adding an extension to the project's pom. These container classes
are instantiated in a plugin using Plexus. However, since 2.0.5,
this stopped working, because extensions now have their own
container and the Plugin throws a NoClassDefFoundError.
Is there new way/workaround for this?
Regards,
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
