Ok, did some further investigation: What I have is an extension
containing a class (C). This class is referenced in the fields of two
different Mojos, the fields are not even initialized by Plexus. Looking
at the new DefaultExtensionManager, I suppose this cannot work any
more, because the
On 24 Apr 07, at 5:48 AM 24 Apr 07, Jochen Kuhnle wrote:
Ok, did some further investigation: What I have is an extension
containing a class (C). This class is referenced in the fields of
two different Mojos, the fields are not even initialized by Plexus.
Looking at the new
On 2007-04-24 15:25:48 +0200, Jason van Zyl [EMAIL PROTECTED] said:
On 24 Apr 07, at 5:48 AM 24 Apr 07, Jochen Kuhnle wrote:
Ok, did some further investigation: What I have is an extension
containing a class (C). This class is referenced in the fields of two
different Mojos, the fields
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
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
