This means that in your SU, you have to define either: 1) a dependency on a component (packaged as jbi-component) 2) the component name in the plugin configuration
This is needed to create the SA jbi descriptor which includes the target component for each SU. On 10/18/06, moraleslos <[EMAIL PROTECTED]> wrote:
I'm using the Maven 2 plugin for Eclipse 3.2 and am now trying to automate my build process (been zipping up my SUs/SAs manually). I followed the instructions for creating a SU and SA here-- http://servicemix.org/site/maven-jbi-plugin.html-- but am running into a problem with SA. First of all, I'll describe my current directory structure: --> /integration-esb --> /integration-servicemix -->/src/... -->pom.xml --> /integration-servicemix-jbi -->pom.xml -->pom.xml In my integration-esb directory, my pom uses the 'pom' packaging to go to the corresponding subdirectories. In my integration-servicemix directory, the pom uses 'jbi-service-unit' packaging. This looks good. The integration-servicemix-jbi directory does not contain any source code. It is there only to package the SU into an SA. This pom looks like this: *************************************** ..... <groupId>com.test.integration.servicemix.jbi</groupId> <artifactId>integration-servicemix-jbi</artifactId> <name>Servicemix Service Assembly</name> <packaging>jbi-service-assembly</packaging> <version>1.0-SNAPSHOT</version> <dependencies> <dependency> <groupId>com.test.integration.servicemix</groupId> <artifactId>integration-servicemix</artifactId> <version>1.0-SNAPSHOT</version> </dependency> </dependencies> .... *************************************** When I run mvn compile, I get this error: [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [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. -los -- View this message in context: http://www.nabble.com/issues-with-Maven-building-SA-tf2468029.html#a6880923 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
