]
Nick Boldt commented on JBIDE-19757:
------------------------------------
jiralint wants me to punt this to Beta2 or mark it resolved, but I can't do that until
we release Beta1, as it depends on our changing the release process for Beta1.
[~maxandersen] could jiralint have some way of determining which issues can be closed for
Beta1, but which can't be closed until Beta1 is live? I could use a label like
"depends-on-release" or "resolve-after-released" if that would be
useful here.
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
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?