]
Mickael Istria commented on JBIDE-21377:
----------------------------------------
Cost: low. Yaml editor isn't intrusive, doesn't add irrelevant noise, is a
"light" feature.
User impact:
* for those using Yaml (hard to evaluate, but I estimate some 20%, and many
early-adopters/influential people): high satisfaction
* for those not using Yaml: no difference
Keep in mind that Central Software installation is nice, but it's still something that
many users may not even look at; and that users expect from a good IDE to not have to add
anything. If we want Eclipse+JBT to be a good IDE, we should not expect users to have
additional efforts to make in order to support an already popular (with growing
popularity) format.
Do I need to be more explicit about where my vote goes ? ;)
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