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

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12441838#action_12441838 ] 

Nick Boldt commented on JBIDE-3161:
-----------------------------------

OK, looks like the last local JBDS build worked -- I'm getting the correct jar name.

Product feature zip contains this new plugin.

Archive:  ./jbds-build/2.0.0.CR1/200812090100/richfaces/com.jboss.jbds.product.feature.zip
  Length     Date   Time    Name
 --------    ----   ----    ----
   299642  12-09-08 01:24   plugins/com.jboss.jbds.product_3.0.0.CR1-N200812090100.jar
     3417  12-09-08 01:24   plugins/org.jboss.tools.equinox.transforms.xslt_3.0.0.CR1-N200812090100.jar
        0  12-09-08 01:24   features/com.jboss.jbds.product.feature_3.0.0.CR1-N200812090100/
    12301  12-09-08 01:24   features/com.jboss.jbds.product.feature_3.0.0.CR1-N200812090100/feature.xml
 --------                   -------
   315360                   4 files

Also in the all-in-ones:

$ unzip -l ./jbds-build/2.0.0.CR1/200812090100/all/jbdevstudio-2.0.0.CR1-N200812090100-ALL-win32.zip | grep equinox.transf
     3417  12-09-08 01:24   eclipse/plugins/org.jboss.tools.equinox.transforms.xslt_3.0.0.CR1-N200812090100.jar

----

I don't understand your other comments. Are you suggesting that something is wrong within the config.ini file? Or that I need to do something with those files other than just building and packaging the plugin?


> 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