Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-10863

All modules of a multi-module maven project are not deployed with "mvn fabric8:deploy" when fabric8-maven-plugin-1.2.0.redhat-630371 is used

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • fuse-6.x-GA
    • Fabric8 v1
    • None
    • % %

    Description

      When deploying a multi-module maven project with maven-fabric8-plugin-1.2.0.redhat-630371, only the last bundle is applied to the profile.

      Project Structure:
      
      Parent:
           Module1
           Module2
      
      
      JBossFuse:karaf@root> profile-display elpp 
      Profile id: elpp
      Version   : 1.0
      Attributes: 
      	abstract: false
      	parents: karaf
      Containers: 
      
      Container settings
      ----------------------------
      Bundles : 
      	mvn:com.module2/Module2/0.0.1-SNAPSHOT
      
      Agent Properties : 
      	  lastRefresh.elpp = 1561001872606
      
      
      Configuration details
      ----------------------------
      PID: io.fabric8.web.contextPath
        com.module1/Module1 Module1
        null/null Fuse-Profile
        com.test/Module1 Module1
        com.test/Module2 Module2
        com.module2/Module2 Module2
      
      
      
      Other resources
      ----------------------------
      Resource: dependencies/requirements.json
      Resource: dependencies/com.test/Module2-requirements.json
      Resource: dependencies/com.module2/Module2-requirements.json
      Resource: dependencies/com.module1/Module1-requirements.json
      Resource: dependencies/com.test/Module1-requirements.json
      
      
      

      But this works while using maven-fabric8-plugin-1.2.0.redhat-630343 and running "mvn fabric8:deploy". With this version, all the modules described in the parent project are applied to the specified profile.

      JBossFuse:karaf@root> profile-display elpp 
      Profile id: elpp
      Version   : 1.0
      Attributes: 
      	abstract: false
      	parents: karaf
      Containers: 
      
      Container settings
      ----------------------------
      Bundles : 
      	mvn:com.module2/Module2/0.0.1-SNAPSHOT
      	mvn:com.module1/Module1/0.0.1-SNAPSHOT
      
      Agent Properties : 
      	  lastRefresh.elpp = 1561022742912
      
      
      Configuration details
      ----------------------------
      PID: io.fabric8.web.contextPath
        com.module1/Module1 Module1
        null/null Fuse-Profile
        com.test/Module1 Module1
        com.test/Module2 Module2
        com.module2/Module2 Module2
      
      
      
      Other resources
      ----------------------------
      Resource: dependencies/requirements.json
      Resource: dependencies/com.test/Module2-requirements.json
      Resource: dependencies/com.module2/Module2-requirements.json
      Resource: dependencies/com.module1/Module1-requirements.json
      Resource: dependencies/com.test/Module1-requirements.json
      

      A similar issue was reported earlier with ENTESB-5433
      But in 1.2.0.redhat-630347 the following property was added because of ENTESB-8039

        /**
           * Whether or not we should override the existing profile.
           */
          @Parameter(property = "fabric8.overrideProfile", defaultValue = "true")
          private boolean overrideProfile;
      
           /**	    /**
      

      So, if I use mvn fabric8:deploy -Dfabric8.overrideProfile=false all the modules are deployed properly with 1.2.0.redhat-630371. But I think it will impact some other properties.

      Attachments

        Issue Links

          Activity

            People

              ggrzybek Grzegorz Grzybek
              rhn-support-adongre Avinash Dongre
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: