[
https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18105:
------------------------------------
As discussed today, sounds like the best approach here is to XSLT from plugin.xml -> a
properties file like
https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent...
because the discovery plugin.xml already contains the explicit list of features which we
consider EA. Using p2 would pull in all the dependent features too, which is more than we
want tagged as EA in the UI (JBIDE-17808).
generate jbtearlyaccess.properties from
jbtearlyaccess-multiple.target
----------------------------------------------------------------------
Key: JBIDE-18105
URL:
https://issues.jboss.org/browse/JBIDE-18105
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build, central, discovery
Affects Versions: 4.2.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.2.0.CR1
Since the JBT EA .target file already contains all the IUs which are considered early
access (and their dependencies, which are sometimes also EA, like Tern) we can generate
the list of EA features from that .target file, and maintain an ongoing [min,max] version
range of what's considered early access.
Currently the properties file looks like this:
https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)