We are facing this challenge:
- Want to publish with a destination.
- The destination setup requires a local path to bind to SVN that can differ for any Flare author.
- We do not desire the workaround to have common local paths since not all users may have the according permissions.
- Idea: Exclude the destination files from source control so these can be managed locally based on some central guideline.
- "Unversion and add to exclusion list" via Tortoise SVN:
Flare detects this as "deleted" and allows no further handling (even if the file is locally still present). - Using a relative path:
The root of this path is "C:\Windows\system32", which is unacceptable for permission reasons. - Using a dynamic path which points to the user home "C:\Users\%username%":
In the Flare context the variable is not evaluated and the operation fails.