yeah, that'd probably do it. It seems like I had a similar problem
once in the assembly plugin, and wound up excluding the component-api
dependency from the plexus-container-default artifact. It may need to
be declared as provided...not sure. Anyhow, I was having trouble with
the Contextualizable interface. It was picking up the wrong class
file for it, as I remember. (probably wasn't with the assembly
plugin, now that I think of it...)
-john
On Jul 13, 2007, at 10:11 AM, Mark Hobson wrote:
On 13/07/07, John Casey <[EMAIL PROTECTED]> wrote:
I you implement LogEnabled or extend AbstractLogEnabled (I prefer the
former), plexus will populate the logger when it initializes the
component, prior to use.
This is what I would have expected - I did try this initially but the
logger ended up being null. This is within the dependency plugin
which has issues regarding the plexus container api/default
dependencies, so perhaps this is causing plexus to not recognise
LogEnabled.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
