[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
12:36 p.m.
[
https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19757:
------------------------------------
After a few more iterations:
* Using FULL SITE, including TPs and Central:
Time to resolve JBossAS connector (not waiting for the rest to load): 15s
Time to complete install (including the above 15 seconds): 55s
* Using JBT 4.3.0.Beta1 site only (no TPs or Central):
Time to resolve JBossAS connector (not waiting for the rest to load): 4-7s
Time to complete install (including the above 15 seconds): 45s
So, I've decided to leave the symlink
http://download.jboss.org/jbosstools/updates/webtools/mars/ pointing here:
http://download.jboss.org/jbosstools/static/mars/development/updates/core...
Resulting install footprint is 12M:
{code}
$➔ du -sch `find plugins features -maxdepth 1 -mindepth 1 -mmin -10|sort`
52K features/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta1-v20150612-2158-B25
1.2M plugins/org.jboss.ide.eclipse.archives.core_3.6.0.Beta1-v20150612-2158-B25
172K plugins/org.jboss.ide.eclipse.archives.ui_3.6.0.Beta1-v20150612-2158-B25.jar
124K plugins/org.jboss.ide.eclipse.archives.webtools_3.1.0.Beta1-v20150612-2158-B25.jar
2.9M plugins/org.jboss.ide.eclipse.as.classpath.core_3.1.0.Beta1-v20150612-2158-B25.jar
48K plugins/org.jboss.ide.eclipse.as.classpath.ui_3.1.0.Beta1-v20150612-2158-B25.jar
900K plugins/org.jboss.ide.eclipse.as.core_3.1.0.Beta1-v20150612-2158-B25.jar
88K plugins/org.jboss.ide.eclipse.as.dmr_3.1.0.Beta1-v20150612-2158-B25.jar
1.4M plugins/org.jboss.ide.eclipse.as.management.as71_3.1.0.Beta1-v20150612-2158-B25.jar
28K plugins/org.jboss.ide.eclipse.as.management.core_3.1.0.Beta1-v20150612-2158-B25.jar
1.7M plugins/org.jboss.ide.eclipse.as.management.wildfly8_3.1.0.Beta1-v20150612-2158-B25.jar
608K plugins/org.jboss.ide.eclipse.as.ui_3.1.0.Beta1-v20150612-2158-B25.jar
308K plugins/org.jboss.ide.eclipse.as.wtp.core_3.1.0.Beta1-v20150612-2158-B25.jar
96K plugins/org.jboss.ide.eclipse.as.wtp.ui_3.1.0.Beta1-v20150612-2158-B25.jar
28K plugins/org.jboss.tools.archives.scanner_3.6.0.Beta1-v20150612-2158-B25.jar
48K plugins/org.jboss.tools.as.runtimes.integration_3.1.0.Beta1-v20150612-2158-B25.jar
48K plugins/org.jboss.tools.common.jdt.debug_3.7.0.Beta1-v20150608-1702-B21.jar
36K plugins/org.jboss.tools.foundation.checkup_1.2.0.Beta1-v20150608-1702-B21.jar
88K plugins/org.jboss.tools.foundation.core_1.2.0.Beta1-v20150608-1702-B21.jar
32K plugins/org.jboss.tools.foundation.ui_1.2.0.Beta1-v20150608-1702-B21.jar
72K plugins/org.jboss.tools.jmx.core_1.7.0.Beta1-v20150612-2158-B25.jar
212K plugins/org.jboss.tools.jmx.ui_1.7.0.Beta1-v20150612-2158-B25.jar
88K plugins/org.jboss.tools.runtime.core_3.1.0.Beta1-v20150608-1702-B21.jar
168K plugins/org.jboss.tools.runtime.ui_3.1.0.Beta1-v20150608-1702-B21.jar
732K plugins/org.jboss.tools.stacks.core_1.2.0.Beta1-v20150608-1702-B21.jar
212K plugins/org.jboss.tools.usage_2.1.0.Beta1-v20150608-1702-B21.jar
12M total
{code}
If we feel that 45 seconds is too long, I can adjust the webtools site category.xml [1] to
include the missing foundation, stacks, usage, runtime, and common plugins.
[1]
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
Then for Beta2 we can go back to using the special webtools-site instead of the whole JBT
site.
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)
3951
days inactive
3951
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Nick Boldt (JIRA)