[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Ambitious composer plans


I want refresh this topic because we are in post 3.6.

 Would be good to start IP cleanup process.
Dawid PakuÅa
+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 [1][2] 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 [3]. Composer / puli or any other plugin can provide such information.

Dawid PakuÅa
+48 795 996 064

On 22 September 2015 at 14:50:02, Thomas Gossmann (eclipse@xxxxxx) wrote:

Hey guys,

I write a blog post about the composer plans [1] that Robert and me
discovered when we initially created the plugin and also talks about
merging this into PDT. So, despite having the idea of merging composer
into PDT, it is much more interessting to get the original idea of the
composer plugin. Especially since it has a lot potential for PDT.

I unfortunately had to cancel the GSOC project even before it was
submitted. Yet next summer still may be an opportunity for this
(depending on how fast I finish).

Nevertheless, merging composer into PDT is a huge effort and there are a
lot of challenges ahead (which I address in my post). It is also way
more than just refactoring the appropriate package names. I assume the
workload for one person to be 3 month (likely higher).

This thread should be used to think about the options we have, what
needs to be prepared (and how) and probably create a strategy merging this.

[1] http://gos.si/blog/pdt-and-composer-a-visionary-concept

pdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit