<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/25/2016 05:35 PM, Alexey Kazakov
wrote:<br>
</div>
<blockquote
cite="mid:a5351a7a-6439-ecfc-543e-bb57e8d33e38@redhat.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
On 10/25/2016 08:33 AM, Alexey Kazakov wrote:<br>
<blockquote
cite="mid:d1b9652b-4f4f-463a-01d3-7658389fb116@redhat.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p>Hi,</p>
<p>Yes, in general, I think it would make sense to move upstream
JBossTools parts which are not Red Hat specific. But
technically it's not so easy. For example our HTML editor uses
a lot of shared code from base/common and jst components.
Validation, navigation, Palette, etc. All these are our
internal JBossTools frameworks which we havily use in
different JBossTools components. So we can't just move HTML
editor to Eclipse without moving a lot of common JBossTools
code. In the past we actually discussed if we can move some
our stuff like JavaEE stuff to Eclipse but faced the same
issues.<br>
</p>
</blockquote>
</blockquote>
Ok,<br>
Are there jiras or Eclipse bugs about it?<br>
I imagine a part of the JBoss Tools "frameworks| could be moved
together with the contributed services and extensions.<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer for <a href="http://developers.redhat.com">Red
Hat Developers</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>