L.S.,
It looks as if the Maven JBI plugin hasn't been configured in your
project. You probably need to add
<plugin>
<groupId>org.apache.servicemix.tooling</groupId>
<artifactId>jbi-maven-plugin</artifactId>
<extensions>true</extensions>
</plugin>
to your <build><plugins> section to point to the correct JBI plugin
artifact name (org.apache.servicemix.tooling:jbi-maven-plugin).
Gert
Bou wrote:
Well I have this error now :-(
[INFO] The plugin 'org.apache.maven.plugins:maven-jbi-plugin' does not exist
or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-jbi-plugin' does not exist or no valid
versio
n could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1286)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1522)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:386)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException:
The plugin 'org.apache.maven.plugins:maven-jbi-plugin' does not exist
or no valid version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:228)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:90)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:166)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1257)
... 14 more
gnodet wrote:
The JBI descriptor for the service assembly is mandatory for ServiceMix
too.
I guess the problem comes from the SU, and the jbi maven plugin should
output something at that point if it can not generate the jbi.xml
descriptor for the SU.
On 10/26/07, Bou <[EMAIL PROTECTED]> wrote:
No just that :
[INFO] [jbi:generate-jbi-service-assembly-descriptor]
[INFO] Generating jbi.xml
[INFO] Determining component name for service unit Login-http-su
[INFO] Project [EMAIL PROTECTED] packaged
jbi-component
Gert Vanthienen wrote:
L.S.,
Normally, the Maven JBI plugin does generate jbi.xml files. Any
errors/warnings during the build...?
Gert
Bou wrote:
I have a new problem ;-)
When i do mvn package, it don't create jbi.xml.
Then when i want to import on an other server se says me that jbi.xml
is
required ?
thanks for your solution.
--
View this message in context:
http://www.nabble.com/how-to-redeploy-an-application-tf4682784s12049.html#a13428699
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
