]
Mickael Istria commented on JBIDE-12447:
----------------------------------------
I think the plan is fine. Don't forget to consider tests too:
org.jboss.tools.runtime.test depends on a lot of bundles from all other modules. It should
be split and tests should be moved to each module.
We may also want to have a mock runtime detector to test the runtime detector framework by
itself, independently of another component.
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: