Composer support

[pelmered]

No description provided.

[georgestephanis]

I'm torn on this. On one hand, I'd ordinarily be fine adding Composer support to a plugin. I merged a pull request a while back to add it to Jetpack. On the other hand, the target of this plugin is for merge into core, and doing stuff to improve it as a plugin could be counterproductive or at least diversionary to that goal. I'm going to need to think on it.

[pelmered]

I can see why this is unwanted and unnecessary in the long run, but I don't really se the problem with adding this now to be honest. The composer support is completely separate from the plugin as the only file that is affected is composer.json. When the plugin should be merged you can just remove the file and there is no harm done. Nothing else in the plugin will be affected by this.

Until the merge, this helps anyone who uses composer to manage plugins. It will make the plugin more available and probably tested by more people. They would also get a good mechanism for getting newer versions of this plugin until till the plugin is merged.

[georgestephanis]

Fair enough. Merging.