If you have dependencies that you do not wish to include you should be able to add
<scope>provided</scope> since they are part of the platform. Cheers P On 10/18/06, moraleslos <[EMAIL PROTECTED]> wrote:
I gave this a try but Maven kept complaining that I needed the dependency--in this case, servicemix-lwcontainer--installed in the repo. Since I only need a reference to lwcontainer so that Maven can generate the appropriate jbi.xml, I went back to using <properties><componentName>... instead. -los Philip Dodds-2 wrote: > > Note that you can also add a dependency on the actually Service Engine > and the plugin will work out the component name. > > Cheers > > P > > On 10/18/06, Terry Cox <[EMAIL PROTECTED]> wrote: >> > [INFO] The service unit integration-servicemix does not have a >> > dependency >> > which is packaged as a jbi-component or a project property >> > 'componentName' >> > >> > >> > Not sure what the above error means... does it need the >> > integration-servicemix to create the zip SU first before the SA can be >> > created? If so, how am I suppose to let maven know how to do this? >> > Thanks >> > in advance. >> >> In your service unit, you can define which component the code in the >> service unit is to deploy to, for example: >> >> <properties> >> <componentName>servicemix-http</componentName> >> </properties> >> >> This allows you to set the target component if it cannot be resolved >> implicitly. >> >> Terry >> >> > > -- View this message in context: http://www.nabble.com/issues-with-Maven-building-SA-tf2468029.html#a6884738 Sent from the ServiceMix - User mailing list archive at Nabble.com.
