Using Grunt with expand-option (in files) screws up the output-path

[RonaldTreur]

Using Grunt's expand option in my config, results in the generated files ending up in the wrong place.

Take this example:

files: [{
    expand: true,
    cwd: 'src/www/',
    src: [
        '**/*.js',
        '!lib/**/*.js',
        '!vendor/**/*.js',
        '!shim/**/*.js'
    ],
    dest: 'src/logs/plato/'
}]

The above example does not put the generated files in src/logs/plato/files, but in src/logs/plato/ components/services/insight.js /files

Note that src/www/components/services/insight.js is actually a valid JS file. There are many more, but somehow grunt-plato took the location of the first file it encountered(?) and inserted it's path into it's output-location.