Deployment Excluded Paths - local paths defaulting to wrong project directory

 Configuring a new project and setting up Excluded Paths in a Deployment (per normal), however when I manually enter a relative path to a local file/directory that I know exists, the warning icon displays and indicates that the local item "not found". Selecting the file selector dialog next to the Excluded Path shows that the project is trying to use the path to an entirely different project's directory as the root for this project's Excluded Paths.

I can't figure out how this came to be or how to resolve it. I have tried setting up a new deployment from scratch, but that did not help. Somehow, the project is confused about its local root directory within the scope of Excluded Deployment paths, but happily maps to the true local root directory in every other context.

Thanks, Fritz

 

1 comment
Comment actions Permalink

I manually enter a relative path to a local file/directory that I know exists

0

Please sign in to leave a comment.