It took a fair amount of work before XML editor was reusable. That's the technical side of it. From the process side, the main thing you loose is ability to control your releases. Only a project can release. If you a part of WTP, you are tied to WTP release schedule, which may be a problem for some adopters that are on a faster release cycle. For instance, you would not be able to do the first release until June of next year, unless you can convince WTP leadership to allow this feature into a service release. There are other details that differ, like control over committer list and dispute resolution. I can go into further detail if there is interest.
I can help with the paperwork if the project team decides to go the separate project route. Happy to see this happening either way. Konstantin Komissarchik Senior Development Manager Eclipse Tools Group Oracle Also, can you point out why it would be harder to reuse component from Wtp sse? Xml editing is already widely reused is it not ? /max
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. Konstantin Komissarchik Senior Development Manager Eclipse Tools Group Oracle
On 07/03/2015 07:51 PM, Konstantin
Komissarchik wrote:
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.
|
