[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-533) Equinox Transforms plugin for JBDS

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBDS-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12507569#action_12507569 ] 

Nick Boldt commented on JBDS-533:
---------------------------------

1. Build switched to use new version.

/devstudio/trunk/devstudio-installer/version.properties
/devstudio/trunk/releng/org.jboss.ide.eclipse.releng/requirements/equinox/build.properties

Note that I changed the filename from 
http://repository.jboss.org/eclipse/galileo/org.eclipse.equinox.transforms.hook_1.0.100.201001192308.jar
to
http://repository.jboss.org/eclipse/galileo/org.eclipse.equinox.transforms.hook_1.0.100.v20100119-2308.jar
for consistency w/ the unpatched ones; I hope that won't cause a problem. (I didn't tweak the jar contents, just renamed it.)

2. I've added the following line to these files:

/devstudio/trunk/product/plugins/com.jboss.jbds.product/config.ini
/devstudio/trunk/transforms/plugins/org.jboss.tools.equinox.transforms.xslt/config_jbds.ini

osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar at 1\:start,org.eclipse.equinox.transforms.xslt at 1\:start,org.jboss.tools.equinox.transforms.xslt at 1\:start

Will be able to verify starting with 

http://hudson.qa.jboss.com/hudson/view/DevStudio_View/job/devstudio-nightly-3.0.0.CR2/70/

> Equinox Transforms plugin for JBDS
> ----------------------------------
>
>                 Key: JBDS-533
>                 URL: https://jira.jboss.org/jira/browse/JBDS-533
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>    Affects Versions: 2.0.0.cr1
>            Reporter: Rob Stryker
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 3.0.0.CR2
>
>         Attachments: config.ini, eclipse.ini, org.eclipse.equinox.transforms.hook.zip, org.jboss.tools.runtime_1.0.0.jar
>
>
> 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