[jbosstools-issues] [JBoss JIRA] (JBIDE-12447) Reorganization of 'runtimes' plugin

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-12447:
-------------------------------------

It looks to me that the as-tester is split out into a swt-bot test, but that the seam test is bundled in with the framework test, so yes, this needs to be split up. 

I adjust the steps as follows:

Step 0 becomes split the test suite first, such that one test plugin can safely move to astools, one can safely move to seam tools, and there is a framework test suite. 
                
> Reorganization of 'runtimes' plugin
> -----------------------------------
>
>                 Key: JBIDE-12447
>                 URL: https://issues.jboss.org/browse/JBIDE-12447
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: JBossAS/Servers, runtime detection, Seam 2
>    Affects Versions: 3.4.0.M1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 3.4.0.M1
>
>
> Runtimes plugin currently only has a handful of plugins (4), but sits at the top of the dependency tree. It depends on astools, seam, and has soft dependencies (via services) to project examples. 
> In order to move runtimes down the stack, and make it a low-level component which others depend on, the following should be done:
> 1) disable the plugins org.jboss.tools.runtime.as.detector and org.jboss.tools.runtime.seam.detector from the build
> 2) Clone org.jboss.tools.runtime.seam.detector (and its feature) into the seam component, but do not enable in build
> 3) Clone org.jboss.tools.runtime.as.detector (and feature) into the astools component, but do not enable in build
> 4) Without these two plugins and features, runtimes can safely be moved down the stack. This will require the build team to put runtimes lower on the build train. This should not affect anyone that CURRENTLY depends on runtimes, since it will still be available, only sooner. This will allow MORE plugins to depend on runtimes. 
> 5) Once runtimes (without it's as and seam detectors) is in the build and building properly, then we can:
> 6) Enable the new plugin and feature in astools
> 7) enable the new plugin and feature in seam
> 8) Once the new plugins are alive and building, we can safely remove the old ones from the runtimes svn tree. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira