You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Liav Ezer <li...@gmail.com> on 2008/12/31 17:24:55 UTC
Need assistance to resolve SA build error
Hi all,
I have 3 su's (1 http consumer & 2 providers). I use fuse-esb-3.3.1.3.
On the last step - when i run "mvn install" for the creation of the SA i
first got an error indicating of missing SNAPSHOT-3 jars & it was fixed
after i edited the xbean-3.3.pom file in the repository (line 61).
Running mvn install again came up with the following error:
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The service unit http-provider2-su does not have a dependency which
is packaged as a jbi-component or a project property 'componentName'[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The service unit
http-provider2-su does not have a dependency which is packaged as a
jbi-component or a project property 'co
mponentName'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:585)
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.MojoExecutionException: The service unit
http-provider2-su does not have a dependency which is packaged as a
jbi-component or a project property
'componentName'
at
org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:407)
at
org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:214)
at
org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:158)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Any idea?
Thanks.
--
View this message in context: http://www.nabble.com/Need-assistance-to-resolve-SA-build-error-tp21233649p21233649.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Need assistance to resolve SA build error
Posted by Liav Ezer <li...@gmail.com>.
Hi Jean,
I found the cause & the resolution for it.
Please refer to:
https://issues.apache.org/activemq/browse/SM-694
Thanks.
Liav Ezer wrote:
>
> Hi Jean,
>
> I double checked my SU pom.xml & saw that indeed i defined the
> servicemix-http depedency:
>
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-http</artifactId>
> <version>${servicemix-version}</version>
> </dependency>
>
> Maybe it's related to the version which i changed in the
> %M2%\org\apache\xbean\xbean\3.3\xbean-3.3.pom
>
> (Please refer to this bug at
> https://issues.apache.org/jira/browse/XBEAN-110)
>
> By the way - I followed the tutorial advise & located the version at the
> root pom.xml file as follows:
>
> <properties>
> <servicemix-version>3.2.2</servicemix-version>
> </properties>
>
>
> Jean-Baptiste Onofré wrote:
>>
>> Hi Liav,
>>
>> you don't have the http component in the pom.xml of your SU.
>>
>> Check if you have something like thi in the SU's POM :
>>
>> <dependency>
>> <groupId>org.apache.servicemix</groupId>
>> <artifactId>servicemix-http</artifactId>
>> <version>2008.01</version>
>> </dependency>
>>
>> Regards
>> JB
>>
>> On Wednesday 31 December 2008 - 08:24, Liav Ezer wrote:
>>>
>>> Hi all,
>>>
>>> I have 3 su's (1 http consumer & 2 providers). I use fuse-esb-3.3.1.3.
>>>
>>> On the last step - when i run "mvn install" for the creation of the SA i
>>> first got an error indicating of missing SNAPSHOT-3 jars & it was fixed
>>> after i edited the xbean-3.3.pom file in the repository (line 61).
>>>
>>> Running mvn install again came up with the following error:
>>>
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] The service unit http-provider2-su does not have a dependency
>>> which
>>> is packaged as a jbi-component or a project property
>>> 'componentName'[INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Trace
>>> org.apache.maven.lifecycle.LifecycleExecutionException: The service unit
>>> http-provider2-su does not have a dependency which is packaged as a
>>> jbi-component or a project property 'co
>>> mponentName'
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>> at
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>> 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:585)
>>> 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.MojoExecutionException: The service
>>> unit
>>> http-provider2-su does not have a dependency which is packaged as a
>>> jbi-component or a project property
>>> 'componentName'
>>> at
>>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:407)
>>> at
>>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:214)
>>> at
>>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:158)
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> ... 16 more
>>>
>>> Any idea?
>>>
>>> Thanks.
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Need-assistance-to-resolve-SA-build-error-tp21233649p21233649.html
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>
>> --
>> Jean-Baptiste Onofré (Nanthrax)
>> BuildProcess/AutoDeploy Project Leader
>> http://buildprocess.sourceforge.net
>> jb@nanthrax.net
>> PGP : 17D4F086
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Need-assistance-to-resolve-SA-build-error-tp21233649p21239604.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Need assistance to resolve SA build error
Posted by Liav Ezer <li...@gmail.com>.
Hi Jean,
I double checked my SU pom.xml & saw that indeed i defined the
servicemix-http depedency:
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-http</artifactId>
<version>${servicemix-version}</version>
</dependency>
Maybe it's related to the version which i changed in the
%M2%\org\apache\xbean\xbean\3.3\xbean-3.3.pom
(Please refer to this bug at
https://issues.apache.org/jira/browse/XBEAN-110)
By the way - I followed the tutorial advise & located the version at the
root pom.xml file as follows:
<properties>
<servicemix-version>3.2.2</servicemix-version>
</properties>
Jean-Baptiste Onofré wrote:
>
> Hi Liav,
>
> you don't have the http component in the pom.xml of your SU.
>
> Check if you have something like thi in the SU's POM :
>
> <dependency>
> <groupId>org.apache.servicemix</groupId>
> <artifactId>servicemix-http</artifactId>
> <version>2008.01</version>
> </dependency>
>
> Regards
> JB
>
> On Wednesday 31 December 2008 - 08:24, Liav Ezer wrote:
>>
>> Hi all,
>>
>> I have 3 su's (1 http consumer & 2 providers). I use fuse-esb-3.3.1.3.
>>
>> On the last step - when i run "mvn install" for the creation of the SA i
>> first got an error indicating of missing SNAPSHOT-3 jars & it was fixed
>> after i edited the xbean-3.3.pom file in the repository (line 61).
>>
>> Running mvn install again came up with the following error:
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] The service unit http-provider2-su does not have a dependency
>> which
>> is packaged as a jbi-component or a project property
>> 'componentName'[INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: The service unit
>> http-provider2-su does not have a dependency which is packaged as a
>> jbi-component or a project property 'co
>> mponentName'
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> 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:585)
>> 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.MojoExecutionException: The service
>> unit
>> http-provider2-su does not have a dependency which is packaged as a
>> jbi-component or a project property
>> 'componentName'
>> at
>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:407)
>> at
>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:214)
>> at
>> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:158)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> ... 16 more
>>
>> Any idea?
>>
>> Thanks.
>> --
>> View this message in context:
>> http://www.nabble.com/Need-assistance-to-resolve-SA-build-error-tp21233649p21233649.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>
> --
> Jean-Baptiste Onofré (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net
> PGP : 17D4F086
>
>
--
View this message in context: http://www.nabble.com/Need-assistance-to-resolve-SA-build-error-tp21233649p21237346.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Need assistance to resolve SA build error
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Liav,
you don't have the http component in the pom.xml of your SU.
Check if you have something like thi in the SU's POM :
<dependency>
<groupId>org.apache.servicemix</groupId>
<artifactId>servicemix-http</artifactId>
<version>2008.01</version>
</dependency>
Regards
JB
On Wednesday 31 December 2008 - 08:24, Liav Ezer wrote:
>
> Hi all,
>
> I have 3 su's (1 http consumer & 2 providers). I use fuse-esb-3.3.1.3.
>
> On the last step - when i run "mvn install" for the creation of the SA i
> first got an error indicating of missing SNAPSHOT-3 jars & it was fixed
> after i edited the xbean-3.3.pom file in the repository (line 61).
>
> Running mvn install again came up with the following error:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The service unit http-provider2-su does not have a dependency which
> is packaged as a jbi-component or a project property 'componentName'[INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The service unit
> http-provider2-su does not have a dependency which is packaged as a
> jbi-component or a project property 'co
> mponentName'
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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:585)
> 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.MojoExecutionException: The service unit
> http-provider2-su does not have a dependency which is packaged as a
> jbi-component or a project property
> 'componentName'
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:407)
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:214)
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:158)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
>
> Any idea?
>
> Thanks.
> --
> View this message in context: http://www.nabble.com/Need-assistance-to-resolve-SA-build-error-tp21233649p21233649.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
jb@nanthrax.net
PGP : 17D4F086
Re: Need assistance to resolve SA build error
Posted by Gert Vanthienen <ge...@skynet.be>.
L.S.,
FWIW, I added a new FAQ entry for this exception:
http://cwiki.apache.org/confluence/display/SM/LifecycleExecutionException+-+The+service+unit+xyz+does+not+have+a+dependency+which+is+packaged+as+a+jbi-component
Regards,
Gert
Liav Ezer wrote:
> Hi all,
>
> I have 3 su's (1 http consumer & 2 providers). I use fuse-esb-3.3.1.3.
>
> On the last step - when i run "mvn install" for the creation of the SA i
> first got an error indicating of missing SNAPSHOT-3 jars & it was fixed
> after i edited the xbean-3.3.pom file in the repository (line 61).
>
> Running mvn install again came up with the following error:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The service unit http-provider2-su does not have a dependency which
> is packaged as a jbi-component or a project property 'componentName'[INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The service unit
> http-provider2-su does not have a dependency which is packaged as a
> jbi-component or a project property 'co
> mponentName'
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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:585)
> 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.MojoExecutionException: The service unit
> http-provider2-su does not have a dependency which is packaged as a
> jbi-component or a project property
> 'componentName'
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:407)
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:214)
> at
> org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:158)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
>
> Any idea?
>
> Thanks.
>