Eclipse BlueSky provides a rich development experience for Web development in Eclipse IDE, including editing assistance, debugging and other features that ease development of web applications.
Eclipse BlueSky relies on existing mainstream and maintained components to provide the language smartness, over popular configuration files like TextMate and protocols like Language Server Protocol or Debug Adapter Protocol; and may rely on some valuable pieces of Eclipse WebTools.
But Eclipse BlueSky is not meant to be a project where we (re)implement parsers or debuggers; it's only focused on integrating existing components. Any work that deals with plain language or debugger logic should be excluded from BlueSky and directed to the underlying components used by BlueSky.
As such, Eclipse BlueSky won't host specific language server or TextMate grammars and will only consume those artifacts produced by other projects.
Eclipse BlueSky is about integrating existing technologies for those languages more than creating more specific language smartness.
Eclipse BlueSky deeply integrates with Eclipse IDE and several related projects. It also targets a wide audience of Web developers.
We believe contributing BlueSky to Eclipse.org will allow Eclipse IDE to provide some better quality support for Web technologies with a low maintenance cost. We also think that the interest in BlueSky from the Eclipse ecosystem is going to be big enough to make it worth enforcing top-quality governance by embracing the Eclipse Development Process.
While the code authored in BlueSky (the integration parts) are EPLv2; the reused artifacts (TextMate grammars, language servers...) are under MIT license. Starting the Language Server requires node.js to be installed on user's machine.
The project will release a 0.1.0 version as soon as it's migrated to Eclipse.org.
The project would then release minor updates whenever one of the included language servers provides interesting updates.
Future work will involve:
* typical bugfixes and minor improvements in code and UI
* Adoption of newer Eclipse Platform/TM4E/LSP4E when they release
* Adoption of newer language servers and textmate grammars
* (Probably) adoption of debuggers conforming ot the Debug Adapter Protocol