we're using 7.0.2 as a framework for a large project that will need to be deployed on production servers in the near future.
it seems that FuseESB is embedding absolute file paths in the bundle cache when environments are built. this has the implication that you can't tar/untar or zip/unzip a fuse directory to move it around. this isn't so bad for linux/unix where /opt can be setup as needed, but it makes it hard to deploy in windows environments where you might have built in c: and then need to deploy in d: (just as an example).
is this a bug that crept in, or something required by the architecture?
I'd say the bundle cache in data folder is very dynamic thing, I don't think it was designed for tar and move.
If you need deploy containers on different machines/evn, we have features and fabric profiles which can make it a lot easier for you.