<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Sorry, missed <a class="moz-txt-link-abbreviated" href="mailto:eclipse-team@redhat.com">eclipse-team@redhat.com</a>.<br>
</p>
<br>
<div class="moz-cite-prefix">On 10/25/2016 08:33 AM, Alexey Kazakov
wrote:<br>
</div>
<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>
<p>Thanks.<br>
</p>
<br>
<div class="moz-cite-prefix">On 10/25/2016 04:50 AM, Mickael
Istria wrote:<br>
</div>
<blockquote
cite="mid:929287df-e40f-26ce-68f3-e97199f7ef39@redhat.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi all,<br>
<br>
There are some stable parts of JBoss Tools, such as some
extension to HTML editors (and family), that would make sense to
be upstream in Eclipse WebTools.<br>
The benefits would be:<br>
* Better Eclipse IDE, happier and more numerous users<br>
* Move maintenance to a public and shared location where we may
be able to get more people to help<br>
* This might even reduce a bit our releng effort if some
bundles/component fully move upstream.<br>
<br>
I don't think this would have a negative impact on JBoss Tools.
Indeed, I imagine users of JBoss Tools install it for WildFly,
OpenShift, Hibernate or whatever JBoss/Red Hat technology
support; not for things such as HTML edition.<br>
<br>
Would that be doable for the Oxygen target? What features could
relatively easily go upstream?<br>
<br>
Cheers,<br>
-- <br>
<div class="moz-signature">Mickael Istria<br>
Eclipse developer for <a moz-do-not-send="true"
href="http://developers.redhat.com">Red Hat Developers</a><br>
<a moz-do-not-send="true"
href="http://mickaelistria.wordpress.com">My blog</a> - <a
moz-do-not-send="true"
href="http://twitter.com/mickaelistria">My Tweets</a></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</body>
</html>