Opened 11 years ago
Closed 11 years ago
#5627 closed defect (bug) (fixed)
Update phpunit grunt task to not use deprecated util
Reported by: | netweb | Owned by: | djpaul |
---|---|---|---|
Milestone: | 2.1 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Core | Keywords: | has-patch commit |
Cc: |
Description
Via #WP27343 and related #bbPress2542
Grunt is deprecating the Grunt.Util.* api
(mentioned in the 0.4.3 announcement http://gruntjs.com/blog/2014-03-07-grunt-0.4.3-released
and the 0.4.2 announcement http://gruntjs.com/blog/2013-11-21-grunt-0.4.2-released)
Once WordPress has a working patch upstream this should be implemented here.
Attachments (2)
Change History (8)
#2
@
11 years ago
- Keywords has-patch added; needs-patch removed
- Milestone changed from Future Release to Awaiting Review
Upstream via 27343 we have gone with the method to include grunt-legacy-util
In 5627.diff:
Grunt is deprecating the Grunt.Util.* api, adding grunt-legacy-util
will allow us to continue using grunt.util.spawn
to spawn the multiple phpunit
Grunt tasks.
- Adds
grunt-legacy-util
topackage.json
- Requires fresh
npm install
to update dependencies
Thanks for keeping an eye on the upstream Grunt module releases.