If bringing it to technology does not introduce any extra overhead fine.
But we would want this include and available to JSDT from day one and don't feel the need to separate these if the only thing we get is more work todo.
Not from participation side, but from reuse and release planning side, a standalone project would allow for more flexibility. It also makes it easier for new participants in Eclipse ecosystem to find the component that they are interested in when its not buried within a larger project.
Senior Development Manager
Eclipse Tools Group
On 07/03/2015 07:51 PM, Konstantin
Yes. Please consider proposing a standalone project under technology project. The project process has been streamlined so it should take less time and effort to navigate. Oracle would like to participate in this effort.
What does it change except making the inclusion more complex?
If it gets to WTP-SSE or JSDT, there is nothing that would prevent
anyone to participate to the effort.