> > Maybe we should resurrect pdt.incubator ? > +1
> BTW, I also think that at least two most active commiters should be > invited to PDT team. Sounds good to me. Greetings, Michal On Wed, Oct 7, 2015 at 5:47 PM, Dawid Pakuła <zu...@w3des.net> wrote: > Hi, > > Plan looks good. Gossi? > Problem are not library dependencies. Composer plugin use code from other > projects: > 1. Provide metadata for class/interface wizard, so probably should be > moved to PDT > 2. Require E4, fortunately we decide to keep api compatibility with > previous eclipse release only > 3. Use JSON editor from outside eclipse, JSON-WTP is still in CQ phase > 4. Is based on Robert Composer Java Bindings. This library probably also > should be moved to PDT and released in eclipse maven repository. > > Maybe we should resurrect pdt.incubator ? > > BTW, I also think that at least two most active commiters should be > invited to PDT team. > > -- > Dawid Pakuła > +48 795 996 064 > > On 7 October 2015 at 08:12:15, Kaloyan Raev (kaloya...@zend.com) wrote: > > Hi, > > I think we need to build a plan and start executing it. How about this: > > 1. Open CQs with code contributions to PDT. This may be quite a heavy > step. As far as I understand, the PEX Composer has a lot of dependencies. > We need to clarify what gets contributed to PDT and what is removed as > dependency. We (Zend) can also contribute via CQ our Composer plugin from > Zend Studio. Once we have the code of both PEX and Zend Composer plugins > under EPL and IP-verified we can start thinking how to merge them in the > ultimate PDT Composer plugin. > > 2. Agree and implement a common Core API part for both PEX Composer and > Zend Composer plugins. The goal is that we have all plugins depending on > Composer (like the Symfony plugin from PEX and the Apigility plugin from > Zend Studio) to use a common Composer Core API. > > 3. Start merging the UI. > > What do you think? > > Kaloyan > > On Tue, Oct 6, 2015 at 5:37 PM, Dawid Pakuła <zu...@w3des.net> wrote: > >> Hi, >> >> 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 (zu...@w3des.net) wrote: >> >> HI, >> >> 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. >> >> [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=471820 >> [2] - https://git.eclipse.org/r/#/c/51516/ >> [3] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=472758 >> >> -- >> Dawid Pakuła >> +48 795 996 064 >> >> On 22 September 2015 at 14:50:02, Thomas Gossmann (ecli...@gos.si) 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 >> >> gossi >> _______________________________________________ >> pdt-dev mailing list >> pdt-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/pdt-dev >> >> >> _______________________________________________ >> pdt-dev mailing list >> pdt-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/pdt-dev >> > > _______________________________________________ > pdt-dev mailing list > pdt-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > _______________________________________________ > pdt-dev mailing list > pdt-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/pdt-dev >
_______________________________________________ pdt-dev mailing list pdt-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/pdt-dev
