[jbosstools-issues] [JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
Max Rydahl Andersen (JIRA)
issues at jboss.org
Mon Jun 29 07:05:02 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084545#comment-13084545 ]
Max Rydahl Andersen edited comment on JBIDE-19757 at 6/29/15 7:04 AM:
----------------------------------------------------------------------
reopen for clarification:
Do I read this right that the difference between optimized site and general one is at minimum 20 seconds ? That is a lifetime for a user.
But I read this as this is how we got it setup now for Mars Beta1 ? (slower install times for the wtp server adapter, correct?) Then i'll got try and see what happens and see how it actually feels - but 5s extra to wait for it to popup and then 15s+ for install is not nice ;/
was (Author: maxandersen):
reopen for clarification:
Do I read this right that the difference between optimzed site and general one is at minimum 20 seconds ? That is a lifetime for a user.
And you say we are installing *less* ...how come ? we should be installing the exact same should we not ?
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS 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
> Assignee: Nick Boldt
> Priority: Minor
> Labels: releasework
> 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)
More information about the jbosstools-issues
mailing list