-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename Tasks not possible #84
Comments
Running into the same issue. Very frustrating.. |
I'll fix this week. |
kimmobrunfeldt
added a commit
to kimmobrunfeldt/progressbar.js
that referenced
this issue
Oct 11, 2014
dupe of #30 |
#35 landed and thus this is fixed. Sorry for the delay and thanks for reporting. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The grunt-release plugin registers
release
as a Task.The release task of the grunt-release plugin conflicts with an existing release task in ourt project. Our existing 'relase' task is part of a complex build process. So renaming our 'release' task would not be a solution here. To avoid such problems grunt allows to rename tasks using
grunt.renameTask('release','grunt-release');
As statet in http://gruntjs.com/api/grunt.task#grunt.task.renametask it should be possible to rename tasks. As I understood correctly the plugin should lookup its configuration using:
grunt.template.process(grunt.config.getRaw(this.name'+'.options.tagName')
instead of using hardcoded plugin name
grunt.template.process(grunt.config.getRaw('release.options.tagName')
The text was updated successfully, but these errors were encountered: