[
https://jira.jboss.org/jira/browse/JBIDE-3161?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-3161:
--------------------------------------
I've verified previous build and it looks like all plugins related to transformation
are in place, but I still can see JBoss Server runtimes defined in WTP. I noticed why it
might happen during moving jbds.product feature in separate builder for JBDS-511 . JBDS
Installation root folder contains two subfolders eclipse and studio. First one for all
dependencies, second for all JBT/JBDS plugins, but problem is that during installer build
c.j.jbds.product.feature and c.j.jbds.product branding plugin are moved from
studio/eclipse(plugins|features) to eclipse(plugins|features) folders accordingly. It is
necessary because only in such configuration studio shows splash screen and loads branding
plugin. Solution is move transformation plugin in eclipse/plugins
The same problem with adding runtimes plugin to build. if it is included in
jbds.product.fetaure it should be copied to eclipse/plugins to be loaded during studio
start, but it depends on plugins which are in studio folder. I'm not sure runtimes
plugin can work in this configuration.
Equinox Transforms plugin for JBDS
----------------------------------
Key: JBIDE-3161
URL:
https://jira.jboss.org/jira/browse/JBIDE-3161
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.0.0.beta1
Reporter: Rob Stryker
Assignee: Nick Boldt
Priority: Critical
Fix For: 3.0.0.cr1
Develop a plugin which will be able to transform / invalidate other plugins in an
installation. First iteration could be just a core with a hard-coded list of plugins /
extension points which we want invalidated.
The goal here is to have all appropriate plugins in our installation, but disable the
ones we do not want. Currently, JBDS removes the webtools jboss server-tools jar entirely,
which makes the update site fail. What we need here is to have the webtools jboss
server-tools jar IN hte installation, and loaded as a plugin, but have all of its
extension points invalidated so it is effectively an empty non-contributing plugin.
org.eclipse.jst.server.generic.jboss_1.5.205.v200805140145 is the plugin we need
invalidated. We need it's plugin.xml to be essentially empty with just base
<plugin></plugin> tags.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira