This exception sometimes occurs when you are packaging multiple SU that target the same component.
There are two ways to specify the JBI component that is targeted by a SU:
- adding a dependency to the SU's pom.xml, e.g.
<dependency> <groupId>org.apache.servicemix</groupId> <artifactId>servicemix-http</artifactId> <version>2008.01</version> </dependency>
- adding a property called
componentName
to the SU's pom.xml, e.g.<properties> <componentName>servicemix-http</componentName> </properties>
You can avoid this LifecycleExecutionException (The service unit xyz does not have a dependency which is packaged as a jbi-component or a project property 'componentName') by using the second alternative when specifying the JBI component name.