[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[pdt-dev] Composer contribution
|
Thanks for info. I didn't notice that IP process in still in progress.
Community plugin need some love, but off course can be (and probably schould be) main plugin.
Sooner it will be in master, sooner I will be able to give some love 
Michal
Od: pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> w imieniu użytkownika Dawid Pakuła <zulus@xxxxxxxxx>
Wysłane: 8 sierpnia 2016 12:01
Do: PDT Developers
Temat: Re: [pdt-dev] Composer contribution
Hi,
Community Composer Plugin is still in IPZilla [1]. We are after some questions so I hope that we receive +1 this week.
After approve and piggy back libs from orbit, can be merged.
Patch is ready to integrate with PDT build system. Things to do:
1. Add as maven module for PDT parent pom
2. Modify site.xml
Community plugin need some love, but off course can be (and probably schould be) main plugin.
Hi Dawid,
What is state of community Composer plugin? Patch is ready to merge or we have additional things to do? If we want first version ready for Neon.1 we need to start integration. It's how I imagine process:
1. Merge community plugin to master (can be still in incubation directory)
2. Add community plugin to build system, mark it as experimental/incubation (if you don't have time I can do this)
3. If we (Zend) will notice something useful in Zend plugin what is missing we will merge it with community plugin
4. Later we can think what we should do with issues reported on github for community plugin
In general I believe that community plugin will be that main plugin and we just move/integrate some features from Zend version of plugin.
What do you think?
Michal
Great! Thanks for info
Hi,
I’ll send patch to IP Team during this week. I think its possible to have initial support for Neon.1 ;)
Hi Dawid,
What is the status of moving community Composer to PDT? Do you think its possible to have first version ready for Neon.1? Also if you need help with something just let me know
Greetings,
Michal
Hi,
Yes, I was thinking about place in our gitroot where we can push source code, even without making it visible to the world with update site. Pushed code will be after IP review and it will be easier to manage it. When initial product (like Composer
support) will be ready we can add it to category.xml with Incubator/Experimental label. For example I can start and commit Zend Composer plugins.
Regarding existing pdt.incubator I also think that we should terminate it.
Michal
Hi,
I think we don’t need incubator as a project, only cons might be in theory parallel ip, so current pdt.incubator probably should be terminated.
After IP review we could keep such code inside our gitroot, and inside category.xml mark it as (Incubator) or (Experimental). See how WTP incubate their new components now.
Hi Dawid,
Your plan looks good From our side
(Zend) we have green light to contribute our Composer support to PDT. Maybe we can reopen Incubator and push code there to have full image. We can think about things that can be taken from both implementations. For example we integrated TM Terminal[1]
in Console view for colored and interactive output. Also if there will be problem with IP I can help reimplement some parts.
[1] https://marketplace.eclipse.org/content/tm-terminal
Michal
|
|
A fully working command-line Terminal inside Eclipse (renamed from "TCF Terminals"). Just press Ctrl+Alt+T to open a local command prompt (Terminal). That's all - it ...
|
Hi Team,
I want push forward merging composer support into PDT[1]. I know thats is not possible to finish before 4.0 but some things may happen in background:
1. Create initial contribution for IP Team. Collecting “approves” from all contributors might be a challenge.
2. Library IP cleanup. I switched Composer Binding to gpl simple json to orbit gson, and made initial patch for WTP JSON Editor integration.
3. Synchronization with orbit (pulse00 composer plugin use newest HTTPTools)
What you think?
[1] - https://wiki.eclipse.org/PDT/Composer_Migration
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev
|
Attachment:
20cddbae-75ff-4812-938a-b6ac3e9ffef6
Description: 20cddbae-75ff-4812-938a-b6ac3e9ffef6
