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

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Sun Jan 24 20:19:19 EST 2010


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

Snjezana Peco commented on JBDS-533:
------------------------------------

I have tested jbdevstudio-eap-win32-3.0.0.v201001212308N-H73-CR2.jar
The plugin has been correctly added to the build, but the metadata generator isn't called after installation which is the reason why xslt transforms plugins don't have the correct startlevel.
The metadata generator worked correctly in 3.0.0.M4.


> 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

        


More information about the jbosstools-issues mailing list