JBoss-IDE Architecture
JBoss-IDE is split into small modular units.
Map
The current plugin map is (release 1.3.x) :
Plugin | Component | Decription |
|---|---|---|
org.jboss.ide.eclipse.core | JBoss general constructs | Generic classes and constructs |
org.jboss.ide.eclipse.ui | JBoss general UI constructs | Generic classes and constructs for UI design |
org.jboss.ide.eclipse.deployer.core | JBoss Deployer Core | Allow to deploy archive and/or folder to JBoss |
org.jboss.ide.eclipse.deployer.ui | JBoss Deployer UI | Allow to configure the deployment to Jboss |
org.jboss.ide.eclipse.jdt.core | JBoss Development Tools constructs | Generic classes and constructs |
org.jboss.ide.eclipse.jdt.ui | JBoss Development Tools UI constructs | Generic classes and constructs for UI design |
org.jboss.ide.eclipse.jdt.j2ee.core | JBoss Development Tools for J2EE constructs | Generic classes and constructs |
org.jboss.ide.eclipse.jdt.j2ee.ui | JBoss Development Tools for J2EE UI constructs | Generic classes and constructs for UI design |
org.jboss.ide.eclipse.jdt.test.core | JBoss Development Tools for testing constructs | Generic classes and constructs |
org.jboss.ide.eclipse.jdt.test.ui | JBoss Development Tools for testing UI constructs | Generic classes and constructs for UI design |
org.jboss.ide.eclipse.jdt.ws.core | JBoss Development Tools for WebServices constructs | Generic classes and constructs |
org.jboss.ide.eclipse.jdt.ws.ui | JBoss Development Tools for WebServices UI constructs | Generic classes and constructs for UI design |
org.jboss.ide.eclipse.launcher.core | JBoss Launcher Core | Allow to launch JBoss in/out Eclipse |
org.jboss.ide.eclipse.launcher.ui | JBoss Launcher UI | Allow to configure the launching of JBoss |
org.jboss.ide.eclipse.packaging.core | JBoss Packaging Core | Allow to package archive and/or folder |
org.jboss.ide.eclipse.packaging.ui | JBoss Packaging UI | Allow to configure the packaging |
org.jboss.ide.eclipse.xdoclet.assist | XDoclet code assist | Code assistance for XDoclet tags |
org.jboss.ide.eclipse.xdoclet.core | XDoclet library management | Manage the XDoclet various jars |
org.jboss.ide.eclipse.xdoclet.help | XDoclet plugins help | XDoclet plugins help and how-to |
org.jboss.ide.eclipse.xdoclet.run | XDoclet generation | XDoclet generation per project configuration |
org.jboss.ide.eclipse.xdoclet.ui | XDoclet UI for icons | XDoclet icons (all UI will be moved here later) |
Each main functionality is split into two or more plugins. It follows the implicit convention of the Eclipse plugins, which tends to isolate UI from Core functionalities. For example, the org.jboss.ide.eclipse.packaging.core plugin contains the model and all persistence classes, and the org.jboss.ide.eclipse.packaging.ui plugin contains all the dialogs and panels needed to interact with the packager. This rule of separation is to be enforced to keep the structure clear.
Proposal Map
This map is related to the JBoss-IDE Roadmap :
Plugin | Component | Decription |
|---|---|---|
org.jboss.ide.eclipse.jdt.aop.core | JBoss Development Tools for JBoss-AOP constructs | Generic classes and constructs |
org.jboss.ide.eclipse.jdt.aop.ui | JBoss Development Tools for JBoss-AOP UI constructs | Generic classes and constructs for UI design |
org.jboss.ide.eclipse.jdt.debug.core | JBoss Development Tools for debugging constructs | Generic classes and constructs |
org.jboss.ide.eclipse.jdt.debug.ui | JBoss Development Tools for debugging UI constructs | Generic classes and constructs for UI design |
Comments