Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-13476

Get rid of bootstrap profiles in root poms for JBT projects (no longer needed)

XMLWordPrintable

      It seens like the bootstrap profiles are not used by developers.
      The only exceptuin is the BrowserSim pieces that use those profiles to have BrowserSim built standalone.
      We should review the profiles for BrowserSim to make it more adapted to use cases (create a "browsersim-standalone" profile for example); and remove bootstrap profiles from other poms.

      Those bootstrap profile cause issue with the set-version plugin, and may cause issue with plugins that look at modules in general

            [JBIDE-13476] Get rid of bootstrap profiles in root poms for JBT projects (no longer needed)

            Mickael Istria added a comment -

            All PR were merged. No more bootstrap profiles.

            Mickael Istria added a comment - All PR were merged. No more bootstrap profiles.

            Max Andersen added a comment -

            I applied jbosstools-gwt and then github.com crashed...will look at it when backup again.

            Max Andersen added a comment - I applied jbosstools-gwt and then github.com crashed...will look at it when backup again.

            Nick Boldt added a comment -

            Nope, Max took away my God Mode Powerz a long time ago. These are for nivologd@gmail.com or maxandersen to apply.

            Nick Boldt added a comment - Nope, Max took away my God Mode Powerz a long time ago. These are for nivologd@gmail.com or maxandersen to apply.

            Mickael Istria added a comment - - edited

            Still to process:

            nivologd@gmail.com, nickboldt: Are you gatekeepers for these repositories? Could you process those PR so we can mark this issue as done?

            Mickael Istria added a comment - - edited Still to process: https://github.com/jbosstools/jbosstools-gwt/pull/4 https://github.com/jbosstools/jbosstools-freemarker/pull/5 https://github.com/jbosstools/jbosstools-runtime-soa/pull/10 https://github.com/jbosstools/jbosstools-bpel/pull/8 nivologd@gmail.com , nickboldt : Are you gatekeepers for these repositories? Could you process those PR so we can mark this issue as done?

            Rob Stryker (Inactive) added a comment -

            https://github.com/jbosstools/jbosstools-server/pull/43 pushed to master

            Rob Stryker (Inactive) added a comment - https://github.com/jbosstools/jbosstools-server/pull/43 pushed to master

            Yahor Radtsevich (Inactive) added a comment -

            Submitted PR https://github.com/jbosstools/jbosstools-vpe/pull/32

            Pushed to master.

            Yahor Radtsevich (Inactive) added a comment - Submitted PR https://github.com/jbosstools/jbosstools-vpe/pull/32 Pushed to master .

            Mickael Istria added a comment -

            In such a case, we'd recommend you to create an "orchestrator pom" which would simply contains the references to the modules you want to build together. This should not get committed and should be specific to your use-case.
            We discovered that bootstrap profiles don't fix common use-cases, instead letting each one make his own pom to reference the modules (in this this case base+vpe) would be ore convenient.

            Mickael Istria added a comment - In such a case, we'd recommend you to create an "orchestrator pom" which would simply contains the references to the modules you want to build together. This should not get committed and should be specific to your use-case. We discovered that bootstrap profiles don't fix common use-cases, instead letting each one make his own pom to reference the modules (in this this case base+vpe) would be ore convenient.

            Yahor Radtsevich (Inactive) added a comment -

            Earlier I used bootstrap profiles when I wanted to build all my component dependencies from their sources.

            Let's say I made some local changes in the base component and I want to see how it works with vpe component.
            What can I do to achieve this, when the bootstrap profiles will be removed?

            Yahor Radtsevich (Inactive) added a comment - Earlier I used bootstrap profiles when I wanted to build all my component dependencies from their sources. Let's say I made some local changes in the base component and I want to see how it works with vpe component. What can I do to achieve this, when the bootstrap profiles will be removed?

            Mickael Istria added a comment -

            Submitted PR https://github.com/jbosstools/jbosstools-vpe/pull/32

            Mickael Istria added a comment - Submitted PR https://github.com/jbosstools/jbosstools-vpe/pull/32

            Konstantin Marmalyukov (Inactive) added a comment - - edited

            Sorry, browserSim standalone has its specific pom(jbosstools-vpe/products). I build it, not vpe root pom.

            Konstantin Marmalyukov (Inactive) added a comment - - edited Sorry, browserSim standalone has its specific pom(jbosstools-vpe/products). I build it, not vpe root pom.

              manderse@redhat.com Max Andersen
              mistria@redhat.com Mickael Istria
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: