Uploaded image for project: 'ServiceMix'
  1. ServiceMix
  2. SM-694

problem packaging multiple service unit dependant from the same component

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 3.0
    • None
    • tooling
    • None

    Description

      I have a problem packaging multiple service unit dependant from the same component using the dependency way in pom. The same doesn't happen if I use the <property><componentName> way.

      If I package more than one (with only one is ok) serviceunit that use the same component in the same service assembly I receive the following error:
      >
      > [INFO] [jbi:generate-jbi-service-assembly-descriptor]
      > [INFO] Generating jbi.xml
      > [INFO] Determining component name for service unit su4
      > [INFO] Determining component name for service unit su6
      > [INFO] ------------------------------------------------------------------------
      > [ERROR] BUILD ERROR
      > [INFO] ------------------------------------------------------------------------
      > [INFO] The service unit su6 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 su6
      > does not have a dependency which is packaged as a jbi-component or a project
      > property 'componentName'
      > at
      > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
      > at
      > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
      > at
      > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
      > at
      > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
      > at
      > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
      > at
      > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
      > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
      > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
      > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
      > 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 su6
      > 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:271)
      > at
      > org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:172)
      > at
      > org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMojo.execute(GenerateServiceAssemblyDescriptorMojo.java:116)
      > at
      > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
      > at
      > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
      > ... 16 more
      >
      >

      the error message is not true because the service unit does decleare a dependecy to a jbi-component. If I switch back to the property way so that I have one serviceunit using dependency and one or more useyng the property way it works.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              raffaelespazzoli Raffaele Spazzoli
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: