I guess this comes from some modifications in the jbi-maven-plugin
for handling shared libraries. It only includes artifacts with a "jar"
packaging type, and components are "jbi-components".
Could you try modifying the jbi-maven-plugin and remove the check
for "jar" (in GenerateComponentMojo.java, line 191) and see if it
works better ?
On 9/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
My binding component is depending on servicemix-jsr181 because it needs
JBITransport (see issue SM-602). So I declare this dependency in the pom.xml:
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-jsr181</artifactId>
<version>3.0-incubating</version>
<scope>compile</scope>
</dependency>
When I build the install package with version 3.0-incubating the
servicemix-jsr181 doesn't get included so I get a ClassNotFoundException at
deploy time.
I didn't have this behaviour before is this a new packaging rule?
It looks like that the only way I have left is to cut and paste the JBITransport
class in my project, any advice?
thanks
Raffaele
--
Cheers,
Guillaume Nodet
