[
https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-19757:
------------------------------------
Using
http://download.jboss.org/jbosstools/static/mars/development/updates/core...
Error is gone.
Time to load list of server adapters: ~30 seconds.
Time to load requirements to install JBossAS Tools Server Adapter
3.1.0.Beta1-v20150612-2158-B25, then complete the installation: ~45 seconds.
(Note that much of the time to load is from other sites, whose metadata apparently needs
to be loaded even when I just click on the JBossAS server adapter.)
Switching back to the Alpha2 site:
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: JBossAS Tools 3.1.0.Alpha2-v20150417-0145-B13
(org.jboss.ide.eclipse.as.feature.feature.group 3.1.0.Alpha2-v20150417-0145-B13)
Missing requirement: JMX JVM Monitor Tools 1.7.0.Alpha2-v20150417-0145-B13
(org.jboss.tools.jmx.jvmmonitor.tools 1.7.0.Alpha2-v20150417-0145-B13) requires
'bundle org.jboss.tools.common.jdt.debug 3.7.0' but it could not be found
Cannot satisfy dependency:
From: JBossAS Tools 3.1.0.Alpha2-v20150417-0145-B13
(org.jboss.ide.eclipse.as.feature.feature.group 3.1.0.Alpha2-v20150417-0145-B13)
To: org.jboss.tools.jmx.feature.feature.group 0.0.0
Cannot satisfy dependency:
From: JMX Console 1.7.0.Alpha2-v20150417-0145-B13
(org.jboss.tools.jmx.feature.feature.group 1.7.0.Alpha2-v20150417-0145-B13)
To: org.jboss.tools.jmx.jvmmonitor.tools [1.7.0.Alpha2-v20150417-0145-B13]
{code}
So... I guess we either need a new WTP site which includes the common.jdt deps, or we just
switch to symlinking the latest JBT release.
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)