#5928 closed enhancement (fixed)
add composer support
Reported by: | DJPaul | Owned by: | djpaul |
---|---|---|---|
Milestone: | 2.2 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Core | Keywords: | has-patch |
Cc: |
Description
I'd like to add Composer support to BuddyPress.
This would involve adding a JSON file into the root of /src/ (thus it would end up in a regular release, not just the dev SVN); it would contain pretty similar to info that our NPM package.json already has. Here's an example: https://github.com/markjaquith/WP-TLC-Transients/blob/master/composer.json
#WP23912 is a discussion about Composer support in WordPress core; the issues covered in that topic don't affect us, but that ticket's description is helpful to read.
If we did this, once we have a release (because we want to use Composer with release versions), we can tell https://packagist.org/ about our new Composer support, which would allow someone to install BuddyPress by integrating with their own project/own site's composer.json (specifying BP as a package requirement). The easiest way to demo this is to install Composer and run a command like "composer require hyyan/logo-controller".
Attachments (1)
Change History (13)
#4
@
10 years ago
I would place the name type and license attributes closer to the top of the file, I'd also depend on ~1.0 rather than a specific version of the composer installer package.
Other than that it looks good
#5
@
10 years ago
What Tom said. While it's not technically meaningful I tend to put properties (loosely) in a same order as documentation (see https://getcomposer.org/doc/04-schema.md ), just makes it familiar for humans to skim through.
#7
@
10 years ago
- Owner set to djpaul
- Resolution set to fixed
- Status changed from new to closed
In 9088:
#8
@
10 years ago
Don't forget to register on https://packagist.org/ for easy usage of the package. I would also add "wordpress" to keywords, makes sense in that context.
Composer all the things! :)
#9
@
10 years ago
Yes, thanks. We will do that once the next version (2.2) is released, approx. mid January 2015. I want Packagist to be configured from http://plugins.svn.wordpress.org/buddypress/, not http://buddypress.svn.wordpress.org/ -- the latter is our development SVN and has some folder path differences, etc. :)
+1. This will be cool.