[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[pdt-dev] Locale Package Development with PDT and Composer
- From: Thomas Gossmann <eclipse@xxxxxx>
- Date: Fri, 29 Apr 2016 13:13:57 +0200
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
I've been on a mission for this, since I created the composer eclipse
plugin with Robert - well, JDT inspired me.
First, let me introduce what I mean by locale package development:
Nowadays, php devs create package and not seldom multiples of them that
often depend on each other. If you have an update ready, you need to
roundtrip packagist, which is around ~3 coffee for each update ;) I
tried to avoid the packagist roundtrip and created a plugin to simply
symlink and read package descriptions from where they are on the local
HDD  (The plugin is more of a research project with the intention of
contributing this back into composer itself). You can read more about
composer local development at .
Now, the job of any IDE would be to help with that.
1) Regardless of composer being used or not, PDT should support taking
other projects into its build path . Now, with composer installed, it
would realize, that one of the packages under vendor/ is symlinked and
is also a project present in the current workspace. It would add this
project into the build path instead of the paths found in composer
autoload. (Since this issue is discussed right now, I'd like to share
that background on this).
2) Follow symlinks on cmd/ctrl+click: Since composer automatically marks
a vendor/ dir as derieved, there is a warning when one tries to change a
file there, which is correct. If sb cmd/ctrl+clicks on something and the
if the target of that is symlinked and the original files are a project
under the current workspace, the original file can be opened instead,
see  and .
Would like to hear your comments.