cwd bug

[SerDIDG]

Hello. When i trying somethings like that, my "prod" folder will stay empty after copying process:

copy: { fonts: { files: [{ expand: true, cwd: 'lib/fonts/', src: ['**/*.*', '!**/*.json'], dest: 'build/fonts/lib/' },{ expand: true, cwd: 'src/fonts/', src: ['**/*.*', '!**/*.json'], dest: 'build/fonts/' },{ expand: true, cwd: 'build/fonts/', src: ['**/*.*'], dest: 'public/fonts/' }] } }

When I remove the cwd parameter the files are copied successfully to the prod folder, but without the relative paths, as expected. Is this is a bug or a feature?

[nofear87]

please show actual and expected file structure thanks!

[SerDIDG]

I've made sample repository. After running grunt command I expect Folder_D is exactly the same as Folder_C, hovever Folder_D was not created at all. https://github.com/SerDIDG/Grunt-CopyCWDTest

[nofear87]

Try this:

copy: {
            test: {
                files: [{
                    expand: true,
                    cwd: 'Folder_A',
                    src: ['**'],
                    dest: 'Folder_C'
                },
                {
                    expand: true,
                    cwd: 'Folder_B',
                    src: ['**'],
                    dest: 'Folder_C'
                }]
            },
            test2: {
                files: [ {
                    expand: true,
                    cwd: 'Folder_C',
                    src: ['**'],
                    dest: 'Folder_D'
                }]
            }
        }
    });

   grunt.registerTask('default', ['clean', 'copy:test', 'copy:test2']);

Folder_C can't be copied, because the folder did not excist at this time. Thats because I used a second task. Another solution could be a watch or a delay. Hope this helps?