]
Alexey Kazakov commented on JBIDE-21377:
----------------------------------------
It all makes sense what Mickael is saying. But are we sure about that Yaml editor quality?
JSON Editor is contributed to Elclipse SSE project and we now have much more control on
it. We didn't include it into TP before that contribution (well we still wait for the
next SSE build to include it).
So if this Yaml Editor is tested and looks good to us then I would +1 to install it by
default. Otherwise it would be safer to keep it optional via a central connection until we
test it.
But maybe [~maxandersen] has a different opinion.
Include Yaml editor in JBoss Tools (& JBDS) via feature dep from
o.j.t.central & add to CoreTools category, too
---------------------------------------------------------------------------------------------------------------
Key: JBIDE-21377
URL:
https://issues.jboss.org/browse/JBIDE-21377
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: updatesite
Affects Versions: 4.3.1.Beta1
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt,
jbtcentral-p2diff_460.txt
There is a decent Yaml editor existing for Eclipse IDE:
https://github.com/oyse/yedit .
It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should
provide it to JBoss Tools users by default.
This would require adding it to the TP and adding a dependency from a JBT feature to it.
On longer-term, we should get it touch with the author to get this plugin migrated to
Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny])
--
Story points - 8 (fibonacci):
* update Central TP,
* update JBT/JBDS TPs,
* update JBT/JBDS category.xml files,
* update JBDS feature.xml,
* send announcement email re: TP changes