Do not delete all files at the target directory about bndtools

[pkriens]

The target directory must be completely rebuildable, its purpose is hold temporary files. Sounds dangerous to keep files there. This always turns against you when you rebuild from scratch

[wesleyse]

I agree that sounds dangerous, but it also is less flexible. I'm currently in a situation where I'd like to put all the generate jars in a single folder. The file named 'buildfile' contains the name of the generated files, why not just delete them?
I'd had to change the code of bndtools my self to work around this situation, but i'd be great if it you considered it to be official.

[pkriens]

Why not create another directory for your other files? bnd also stores other information in the generate directory. I would loathe to make that directory precious in any way except optimizing performance.

[wesleyse]

What I'm doing is using as the generated directory, the pickup directory of Virgo Web Server (when you put a jar there the server automatically deploys the bundle). Since I thought this would be a possible way of integrating one tool with the other one. The pickup directory does not accept a jar inside a directory, so i'm generating the jars there inside, any other suggestion?

[pkriens]

I think you want another directory in your project for this. I have no problem adding a feature in bnd that can duplicate the file into a number of deploy directories if there are no failures. Like:

-copy-to: virgo, /usr/jar

Would that help?

[wesleyse]

Is it possible
-move-to: virgo?

[wesleyse]

I think the answer is no.... :(

[pkriens]

Sorry I thought i replied, copy is possible, move to is not because it implies that nothing will be stored in the target directory which screws up some internal assumptions

[fhuberts]

@Rayn is this still relevant or can we close it?

[wesleyse]

Yes you can...thanks...