This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Gruntfile in site root not found in when mapping tasks to actions | ||
---|---|---|---|
Product: | javascript | Reporter: | Vladimir Riha <vriha> |
Component: | Tools | Assignee: | Jan Stola <jstola> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.0.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Vladimir Riha
2014-05-30 09:07:16 UTC
(In reply to Vladimir Riha from comment #0) > If you want to map Grunt tasks to context menu actions in IDE, Gruntfile > must be in project root. But if Gruntfile is in e.g. site root, Do you have project with this layout? Having gruntfile in siteroot is wrong imo. > This would be also useful for issue 244747 where (in case of e.g. PHP > project), Gruntfile could be in some nested folder (e.g. folder named > "client"). And the client folder is in fact HTML5 Project, right? I tend to avoid mixing NB projects if there is no benefit in doing so (but that is purely personal reason, doesn't mean anything) and if I have "client" folder in PHP project, it is really just a folder and I'd put Grunt file there instead of directly to sources folder. If it's possible to run tasks from Gruntfile in site root, why not this mapping as well ? I can imagine e.g. when creating a module for NodeJS, one would like to have site root == project root in a new project but that need some extra actions so why not put it to site root instead... I'm looking at [1] for instead - if you want to create a new HTML5 project with similar structure you would probably prefer to see folders like static, tasks, scripts in site root (because it is visible in Projects view) But I really don't have a strong opinion, if you disagree or think it's not worth doing, I won't object :) [1] https://github.com/karma-runner/karma |