I want refresh this topic because we are in post 3.6.
Would be good to start IP cleanup process.
+48 795 996 064
On 22 September 2015 at 15:02:26, Dawid PakuÅa (zulus@xxxxxxxxx) wrote:
Thanks for that!
Two comment from me for now:
1. JSON: On JSDT gerrit pending WTP-based JSON editor  I hope
it will be merged in Neon (together with bower support)
2. Namespace support: I opened bug to add class loader metadata
into build path . Composer / puli or any other plugin can
provide such information.
+48 795 996 064
On 22 September 2015 at
14:50:02, Thomas Gossmann (eclipse@xxxxxx) wrote:
I write a blog post about the composer plans  that Robert and
discovered when we initially created the plugin and also talks
merging this into PDT. So, despite having the idea of merging
into PDT, it is much more interessting to get the original idea of
composer plugin. Especially since it has a lot potential for
I unfortunately had to cancel the GSOC project even before it
submitted. Yet next summer still may be an opportunity for
(depending on how fast I finish).
Nevertheless, merging composer into PDT is a huge effort and there
lot of challenges ahead (which I address in my post). It is also
more than just refactoring the appropriate package names. I assume
workload for one person to be 3 month (likely higher).
This thread should be used to think about the options we have,
needs to be prepared (and how) and probably create a strategy
pdt-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit