Comment 1 for bug 1575628

Revision history for this message
Olivier - interfaSys (olivier-interfasys) wrote : Re: "copy" plugin symlinks whole snap folder when no source is given

Some clarification.

The biggest problem I have with the current approach is that anything, apart from blacklisted files/folders, will be copied to the build folder of every part which uses the copy plugin. If one keeps the built snaps in the root folder of the project, they will all end up in the part' s build folders. Same thing if you keep archives in various src/part folders.

I fail to see a real use case for copying the whole project folder to the build folder, apart for some very minimalistic projects which don't use a src folder, so even if snaps end up being blacklisted, the whole recursively copying the top folder bugs me as an approach. Similar issue if '.' is moved to 'src' as a default.

If you look at the snippet I've posted, it's very simple and should only copy one file. You could argue that adding an extra line of configuration doesn't make it less elegant and I would agree, but the problem is that others may make the same mistake I did and end up with GBs of extra data in their project until they realise what's happening, like I did.

Since "source" is used in more than just the copy plugin, there may be problems with changing the approach, so maybe it's simply a documentation (or user :P) issue.