[
https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19757:
------------------------------------
{quote}the difference between optimized site and general one is at minimum 20 seconds
{quote}
No, you read that wrong. The difference between using the JBT webtools-site for Luna
(4.2.3.Final) and the JBT site for Mars (4.3.0.Beta1) is 10 seconds. I don't have
data for the 4.3.0.Alpha1 site.
Note that the JBT webtools-site for Mars (4.3.0.Beta1) and the JBT webtools-site for Mars
(4.3.0.Alpha2) don't work because of new dependencies from Server to Base which no one
communicated to me (dev, releng failure), no one verified worked (dev, releng, QE
faiulre). So, for Beta1 we have two choices:
* use the full JBT site for Mars (4.3.0.Beta1), which is 10 seconds longer to use,
end-to-end
* rebuild the JBT webtools-site for Mars (4.3.0.Beta1 respin-d)
{quote}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 ;/{quote}
Yes.
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/2d3cc63a9b67753ad9...
)
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)