A big +1 to that, with a particular tip of the hat to the notion of supporting popular open source servers like Tomcat out of the box. Last time I checked, Tomcat was an Apache project, not "vendor specific".
While decoupling of WTP from individual server adapters is great, we should not be pushing server adapter maintainers away from Eclipse Foundation, if thatâs where the maintainers would like to develop and host a particular adapter. This is especially true for adapters with long history of active development at Eclipse Foundation, like the Tomcat adapter. The key goals is decoupling of adapter schedules from WTP schedule and providing uniform access to adapters via adapter discovery, but none of those goals actually require moving adapter development somewhere else. Tomcat adapter could be split off as a separate project under server tools (provides release schedule independence) and published on eclipse.org for adapter discovery. - Konstantin From: [email protected] [mailto:[email protected]] On Behalf Of Elson Yuen In general, our direction is to move away to from shipping individual server adapters directly within WTP. We are pushing for all vendor specific server adapters to provide externally via the "Download additional server adapters" link. Therefore, if you happens to be creating a new server adapter for TomEE, it should be exposed via the downloadable server adapter. See the plugin org.eclipse.wst.server.discovery for providing additional server adapter.
| ||
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
