Hi,
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.
Thanks.
On 10/25/2016 04:50 AM, Mickael Istria wrote:
Hi all,
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.
The benefits would be:
* Better Eclipse IDE, happier and more numerous users
* Move maintenance to a public and shared location where we may be
able to get more people to help
* This might even reduce a bit our releng effort if some
bundles/component fully move upstream.
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.
Would that be doable for the Oxygen target? What features could
relatively easily go upstream?
Cheers,
--
Mickael Istria
Eclipse developer for Red Hat Developers <
http://developers.redhat.com>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev