Thanks for your efforts Tony ! It seems to be the wrapper, i get this using upstream jar, Debian jar , Debian wrapper: $ java -jar compiler.jar --warning_level VERBOSE --jscomp_warning=checkTypes --compilation_level SIMPLE_OPTIMIZATIONS --js="file with spaces.js" --js_output_file=/tmp/compiled.js$ java -jar /usr/share/java/closure-compiler.jar --warning_level VERBOSE --jscomp_warning=checkTypes --compilation_level SIMPLE_OPTIMIZATIONS --js="file with spaces.js" --js_output_file=/tmp/compiled.js$ closure-compiler --warning_level VERBOSE --jscomp_warning=checkTypes --compilation_level SIMPLE_OPTIMIZATIONS --js="file with spaces.js" --js_output_file=/tmp/compiled.jsERROR - Cannot read: file ERROR - Cannot read: spaces.js ERROR - Cannot read: with 3 error(s), 0 warning(s)$
> Date: Thu, 16 Oct 2014 21:04:41 -0700 > From: [email protected] > To: [email protected]; [email protected] > Subject: Re: Bug#765563: closure-compiler: does not work when there are > spaces in the path/name of the JavaScript file > > On 10/16/2014 02:39 AM, Eerste Laatste wrote: > > Package: closure-compiler > > Version: 20130227+dfsg1-6 > > Severity: normal > > > > Dear Maintainer, > > > > Using closure-compiler fails when there are spaces in the path/name of a > > JavaScript file even when specifying them like: > > > > "/path name with spaces/and or/script name with spaces.js" > > or > > '/path name/with spaces/and or/script name with spaces.js' > > or > > /path\ name/with\ spaces/and\ or/script\ name\ with\ spaces.js > > Hi Eerste, > > Thank you for the bug report. I'll have to take a look to see if might > be an issue with the wrapper script (as opposed to an upstream issue). > > Cheers, > tony > >
