| [platform-vision] Minutes from September 17, 2014 |
|
Greetings all. My apologies for getting these out so late. Our next call is today at noon eastern (40 minutes from now, yikes) Phone numbers North America 1-866-569-4992 Germany 49-692-2224-6059 France 33-(0)-17-070-8535 UK 0800-033-7806 Switzerland 41-44-580-2115 Sweden 46-85-063-8386 Italy 003-902-3604-8268 Then enter the participant conference extension: 430, then enter pin 4718 Alternatively, SIP clients can call 430@xxxxxxxxxxxxxxxxxxxx, then enter pin 4718 -- In attendance: Wayne Beaton Martin Lippert John Arthorne The main focus of the call was to talk about the desktop, but we ventured into a few other corners. I've captured the gist of the conversation below. As always, if I've mischaracterised anything, please make appropriate corrections. We need Oracle representatives to join this call. I need to keep pushing on this. JavaFX is going to figure prominently in Java over the next three years and beyond. Java 9 modularity will also be a big part of the future. This will have an impact on our tooling, including the Plug-in Development Environment (PDE). Maven needs to be part of the story. Maven support has become one of those things that is just expected in a Java IDE. Aside: we didn't speak about this, but we need to think about next generation build technology. e.g. Gradle Refactoring JDT to implement microservices architecture. Flux: message backbon; combine pieces. Flux in three years: 1. Connections between cloud and desktop tools (sync, migration of projects, integrations) 2. Build cloud "microservices" "Java Microservices": are these part of Flux, Che, Orion, JDT? Something else? Asynchronous integration. Build an integration eco-system. Less coupled integration. Move away from monolithic architecture. No "IDE" projects. * Web editors and navigation * Backend/workspace/provision Pick bits and pieces from "feature" projects. "Give me the Cloud IDE" (Flux+Orion+JDT) Running/hosting Cloud IDE * Not on EF infrastructure * Eco-system provides the hosting * Partial hosting by EF of some microservices (core messaging/front ends); stateless services. Wednesday afternoon meeting at EclipseCon Europe (followed by dinner and drinks). Wayne will sort this out. Platform was "the" integration point. Much more fragmented world now. Refactoring Eclipse to fit into the polyglot tooling environment. Make JDT usable in other ways. Plug into other editors. More flexible/integrate into other tools (e.g. Tomcat integrating with ECJ). Able to fit into other tooling environments. Interactive tooling is more challenging to pull apart. Java/_javascript_ is "just an example". Polglot node.js/ruby/php/c Wayne --
Wayne Beaton @waynebeaton The Eclipse Foundation  |