Alex Karasulu wrote:
Looks like you hit it dead on with the missing xinfo - I did not have the avalon:meta pregoal for the maven.xml. Perhaps the missing xinfo could be reported as such. If a component defined in the block.xml does not have an xinfo file then can't Merlin complain about it being missing instead of using an error message sounding like a classpath problem is at fault. Just my two cents.
The exception message has just been updated to include an i18n message as follows:
Cause: org.apache.avalon.composition.model.TypeUnknownException
Message: Unable to locate a component type descriptor for the component class [MyClass] in the classloader. Please verify that the component classname is correct and that a component type descriptor is included in a jar file available within the container classloader.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
