[jbosstools-issues] [JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-19757:
----------------------------------------

There is no right URL with no site.xml in them.
What I did was importing the org.eclipse.wst.server.discovery bundle in my workspace, running application to check how long it took to load the JBoss Tools server adapter in the discovery page, then hacked the serverAdaptersSite.xml to replace URL, try again; then removed the site.xml on the remote site adn tried again.
AFAIK, there is not property available to override that. Hacking the serverAdaptersSite.xml is the best thing I found (I didn't search a lot).

Please try similar experiments on your side and see whether they infirm/confirm what I measured.

> Consider using main JBT site for server discovery
> -------------------------------------------------
>
>                 Key: JBIDE-19757
>                 URL: https://issues.jboss.org/browse/JBIDE-19757
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build, server
>            Reporter: Mickael Istria
>             Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad92a7bbcda15e1d15b2e22a8 )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)