> > Is there a way to have *.xinfo generated to my desired package > > hierarchy: com.mycompany.component.mycomponent.impl.MyServiceProvider > > ? > > Not sure what you mean by "desired". If you have package x.y.z and > class Widget then you will get x.y.z.Widget.xinfo. The existence of the > xinfo does not mean that the component will be deployed - it simply > declares that a component of a particular type exists. >
you see I used to have x.y.impl.z.Widget as the package hierarchy and I was able to deploy fine. I refactored package hierarchy to be.. x.y.z.impl.Widget. This broke the deployment. after running maven default target, the xinfo is still generated in x.y.impl.z.Widget and I believe the reason the deployment is failing. Even though I have changed all package hierarchies and xml definitions along with @avalon.service tag to x.y.z.impl.Widget. That is the only explanation I have for the deployment of Widget failing suddenly. But I guess what you are saying, is that it should work regardless. I must be doing something wrong. Korosh. > Cheers, Stephen. > > > > > > regards > > Korosh > > > > > > --------------------------------------------------------------------- > > 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]
