#6017 closed enhancement (fixed)
Adding new folders to svn:ignore
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 2.2 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Core | Keywords: | has-patch |
| Cc: |
Description
.idea (it has the same value as .DS_Store, but for PHPStorm)
src/vendor (it has the same - almost - value as build, generated on local machines via composer install based on composer.json).
Attachments (1)
Change History (10)
#6
@
11 years ago
- Owner set to djpaul
- Resolution set to fixed
- Status changed from new to closed
In 9145:
#7
@
11 years ago
The initial problem was that I didn't have /build/ directory, more info in #6015.
And as I saw composer.json file in src/ folder, I just entered composer install in that src folder. Boone said that he works right from it, without build, mainly, so I thought this a good move. And that command created me a src/vendor folder. Now I understand, that build with composer.json file will be on packagist.
How are you getting Composer to give you a
src/vendorfolder?The way I imagined all the Composer stuff working was that, after the 2.2 release, we'd register https://plugins.svn.wordpress.org/buddypress/tags/2.2 etc on Packagist, and Packagist would then provide the release builds of BuddyPress (i.e. the contents of the
buildfolder generated by the Grunt task, notsrc). If you're using Composer with https://buddypress.svn.wordpress.org/, that's not intended (but harmless enough if it works I guess).