Hi guys,
It seems that the avalon:meta tag generates the MyServiceProvider.xinfo
inside following packageL
com.mycompany.component.impl.mycompoent.MyServiceProvider
and therefore expects MyServiceProvider to abide by the above package
hierarchy.
I wanted to use
com.mycompany.component.mycomponent.impl.MyserviceProvider instead.
what happens is that I get the following error when I run maven with a
AbstractMerlinTestCase...
[junit] org.apache.avalon.composition.model.ModelException: Cannot
load component type because the type class
com.mycompany.component.impl.mycomponent.MyServiceProvider does not
exist in the classloader.
Is there a way to have *.xinfo generated to my desired package
hierarchy: com.mycompany.component.mycomponent.impl.MyServiceProvider
?
regards
Korosh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
