[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8460) Get JBossTools added to wtp's list of server adapters

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker updated JBIDE-8460:
-------------------------------

    Attachment: discoverPlugin.zip


1)  Unzip the attached zip file into some temporary location. It is the eclipse wtp plugin in charge of discovery. Note that the plugin is EPL, and also that the file "serverAdapterSites.xml" has been trimmed by me to only include our suggested site.

2) Import this plugin project into a clean eclipse / wtp installation. 

3) Run the runtime workbench

4) File -> New -> Server, then click "Download Additional Server Adapters"

5) Note that it comes up with a list of features to download. 

The version before my vacation did not work at all. Zero elements showed up in the list. Now, it seems, many do. This will be confusing for a user. I believe that simply having the highest-wrapper feature (as.feature) with the category should be enough. The dependencies will be fetched properly. 

I just tested it in the runtime workbench stuff, but it was impossible to get a proper installation after that. It looked like it fetched all the right stuff and none of the wrong stuff, but in the end, you can't install stuff through runtime workbench. 

The only way to 100% properly test it is for me to make a fork of the discovery plugin for my test environment, or for you to push to the actual URLs that are in the wtp builds. 

I've tried by exploding the discovery jar into a plugin folder, and then changing the site.xml, but that didn't work and only blew up my installation. I really don't know how else to test it other than you pushing to the live site 

> Get JBossTools added to wtp's list of server adapters
> -----------------------------------------------------
>
>                 Key: JBIDE-8460
>                 URL: https://issues.jboss.org/browse/JBIDE-8460
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: UpStream
>    Affects Versions: 3.2.0.Final
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 3.2.2.Final, 3.3.0.M4
>
>         Attachments: discoverPlugin.zip
>
>
> It seems what happens is you must make use of the org.eclipse.wst.server.discovery plugin. This plugin has a file (discovery.xml) which has "sites", and those sites (such as http://public.dhe.ibm.com/software/websphere/wasce/updates/) seem to be an eclipse update site.
> The entry point for this wizard is in the New Runtime wizard. At the top is a hyperlink that reads "Download other adapters" (or something similar). It then queries these sites, and allows you to select one of those available.
> It seems the objects are then downloaded as IInstallableUnit's, which is in the org.eclipse.equinox.p2.metadata package.
> I kinda lose track of it here, but, I suspect that after this it is downloaded as an actual eclipse bundle and added into the eclipse installation. But I guess I could trace through further
> Changes to our site would require adding the category and adding it to certain features in our site.xml. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira