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

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753442#comment-12753442 ] 

Mickael Istria commented on JBIDE-13476:
----------------------------------------

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.
                
> Get rid of bootstrap profiles in root poms for JBT projects (no longer needed)
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-13476
>                 URL: https://issues.jboss.org/browse/JBIDE-13476
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: Build/Releng, Visual Page Editor core
>            Reporter: Mickael Istria
>            Assignee: Nick Boldt
>             Fix For: 4.1.0.Alpha2
>
>
> 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira