We are looking for ways to solve this problem in a smart way. It's harder than it seems (to do it right).
Using the same file location for different builds
"... won't be updated because of the old file location ..."
I get the above build warning because I have used the same folder in different builds.
The reason I did this is because one of our app's folders changes rarely, but has 900 of files ~300MB. I don't want to have to dupe this 300MB up with every build, plus the extra time required to compare the files.
It may be useful if there was a way to ignore these build warnings for certain specified folders? I mean, it would be useful that I don't have to trawl through 900 warnings looking for one that may actually be a problem for me.
Ok great, I can see it is not that straightforward (to do it right)!