[jbosstools-dev] Moving parts of JBT to WebTools

[Max Rydahl Andersen]

Note: we have done this multiple time in the past for smallish things 
(especially maven/m2e features).

We tried with bigger things too (hibernate tools, html editing, CDI 
tooling etc.) but just not feasible due to the
slowness and restrictions put on how to implement things at Webtools.

A few comments:

> * Better Eclipse IDE, happier and more numerous users

+1

> * Move maintenance to a public and shared location where we may be 
> able to get more people to help

I assume you mean *more* public place, since the code is already public 
and shared.

> * This might even reduce a bit our releng effort if some 
> bundles/component fully move upstream.

I don't see how that could happen. We would need to do the work on WTP 
side instead and our needed fixes would
now have to wait for Eclipse/WTP to release. If anything this will make 
releasing harder if we move things
we are too dependent on.

> 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.

The HTML/JSF editing was a major part in past - eclipse really are not 
strong on it.

Suggestions for things that is somewhat movable: livereload (we'll need 
to make sure we decouple it so it is not tied to jboss tools WTP server 
adapters)

/max
http://about.me/maxandersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20161027/188c5523/attachment.html