Unable to change source file for closure compiler target |
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: 1. Run closure compiler for some target. 2. File compiled will have same name as target, but might not have the desired path. What is the expected behavior? What went wrong? Have a file called prefs.js, but when I try to use the closure compiler on prefs, it runs the closure compiler on a different prefs target. Is it possible to create a target for closure compiler that uses a source file other than <target_name>.js? Did this work before? N/A Chrome version: 57.0.2987.110 Channel: stable OS Version: Flash Version:
,
Mar 24 2017
,
Mar 27 2017
because you can just rename your file if necessary, this is not a high priority issue for me right now. sorry!
,
Mar 27 2017
,
Jul 21 2017
,
Jul 23
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 25
This should be addressed by the new way closure compilation works, see http://go/closure-compile-gn. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kkaluri@chromium.org
, Mar 24 2017