GSOC 2015: Contribute Composer Plugin to PDT

[Thomas Gossmann]

Hey Guys,

Google Summer of Code is announced and I probably have the idea to contribute the Composer Plugin to PDT. I'm mostly responsible for the Composer Plugin. The plugin itself is waiting some additions [1], that I'd like to add, too.

To summarize them: We install helpers that we run from the command line but would be cool to run them out of the IDE itself, e.g. phpunit. There should be no difference between running them from CLI or IDE. Some of them are installed through composer and I'd like to provide a framework, so these tools can be used in PDT (and if necessary installed). You may think about a phpunit plugin and if not installed the user gets asked if phpunit should be installed system-wide or per project and then be used that way.

The composer plugin also provides the required meta-information for a project to accurately utilize the "new Class/Interface/Trait" dialogs. That would be a great enhancement as well to move them into PDT as well from PEX.

However, Composer + PEX is not completely done by me, I cannot decide this on my own. So, I'm kindly asking you ...
... about this idea in general
... whether you would give your ok, that parts of your code would - given this project comes alive - contributed to eclipse under their terms
... zulus as head of PDT about this and if there is a mentor for this project.

Thanks a lot

P.S. There is a deadline, project needs to be placed by 16th of march (there is a little hurry, yes - I'm sorry for reacting late)

[1] https://github.com/pulse00/Composer-Eclipse-Plugin/issues

[rob...@dubture.com]

Hi Thomas,

 

sound like a good idea!

 

If you need anything for the initial GOC application where i could help, let me know.

 

 

 

cheers

 

-robert

--

You received this message because you are subscribed to the Google Groups "PDT Extensions Platform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pdt-extensions-pl...@googlegroups.com.

To post to this group, send email to pdt-extensi...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pdt-extensions-platform/22f6deae-cafd-4954-9888-d4a3da076566%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

 

[zulus]

Hi,

I also like this idea. I can be a mentor off course ;)
If everybody agree, you can open official discussion on pdt-dev.

[Marek Maksimczyk]

For me it's fine.

Best regards,

Marek Maksimczyk

--

[Thomas Gossmann]

Thank you Guys,

I think, because there is a little hurry, whom do I need to reach out too as well?

Thanks
gossi

[KUBO Atsuhiro]

Hi Thomas,

I absolutely agree.

--
KUBO Atsuhiro e-mail: ku...@iteman.jp

[zulus]

Hi,

Today is last day to send application to GSoC: https://www.google-melange.com/gsoc/homepage/google/gsoc2015

[zulus]

All composer eclipse plugin and composer java bindings contributors, please add +1 to this github thread: https://github.com/pulse00/Composer-Eclipse-Plugin/issues/131

I need it for IP process.

BTW: After IP legal process (for community and Zend plugins) we will start  "mix" process ;)

[zulus]

To keep all informed. Community composer support has been merged to PDT in last week and become main PDT implementation :D

Merged version is a little bit changed in compare to original one:
1. Third party JSON editor is no longer dependency (I personally save over 300mb of ram after remove it!)
2. com.dubture.composer.feature have com.eclipse.php.composer in dependency to allow simple migration.
3. Composer integration with PEX new class wizards has been moved to PEX Core-Plugin for now.
4. Composer integration will no be published as part of Neon.1 repository (it's a little bit too late). Will be part of PDT 4.1 p2 and marketplace entry. We plan add it to neon repository and PHP package since Neon.2 (after ~3 months).
5. Some lib dependencies has been removed.