expand mode clobbers destination files with same name / different extensions

[tkellen]

One more reason to finish getting node-globule upstreamed.

gruntjs/grunt-contrib-compress#70

[stefanr]

I think a solution to this problem would be to change

destPath = destPath.replace(/(\.[^\/]*)?$/, options.ext);

to

destPath = destPath.replace(/(\.[^\/\.]*)?$/, options.ext);

in lib/grunt/file.js.

[dynamicdan]

Ok, this is a serious issue. I just lost 45 mins because I was searching for the magical (non-existent) dest glob (think $1 or %1) substitution solution.

My scenario:
I'm using compass/sass to output 3 css files (screen.css, print.css, ie.css) and then compress them (screen.css.gz, print.css.gz, ie.css.gz) using grunt-contrib-compress. This was fine in my first attempt where all files existed in their own build/ dir but that screwed up all relative image paths used in the CSS so I decided to be smart and use build.screen.css -> PROBLEM...

According to this http://stackoverflow.com/questions/16697344/configure-grunt-file-name-matching-for-files-with-multiple-dots the decision made with extensions (ext) that everything after the first dot is the extension killed me. Changing the input files to build-screen.css fixed the problem but this is not ideal.

I just found "extDot"..
Change the behavior of ext, "first" and "last" will remove anything after the first or last . in the destination filename, respectively. Defaults to "first".
#750 (comment) seems to reference some pressure to use this but I don't know anything about this upstreaming stuff.

[vladikoff]

@tkellen Setting this for 0.5.0, assuming that node-globule fixes this issue.

[tkellen]

It does.

[tkellen]

This has been resolved with the extDot option. See:
http://gruntjs.com/configuring-tasks#building-the-files-object-dynamically