The contributed code depends on wtp-sse. It is hard to predict right now
but I guess on many cases JSON editor will require wtp-sse release.
--
Gorkem
On 3 Jul 2015, at 14:39, Konstantin Komissarchik wrote:
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 Jul 3, 2015, at 11:16, Mickael Istria <[email protected]> wrote:
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.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
wtp-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
