Hello,

My project has an "includes" folder with a few PBDs in it, that is included in the working copy via an svn:externals property (http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html).

This causes errors when attempting to do an SVN Update on the project:

 ---------- Source Control
SVN update
SVN client is updating target. Please wait...
An explicit update tried to update the path [D:\something\ws_objects\include\include.pbl.src] that doesn't live in the repository and cannot be brought in
An explicit update tried to update the path [D:\something\ws_objects\include\dw2xls.pbd.src] that doesn't live in the repository and cannot be brought in
An explicit update tried to update the path [D:\something\ws_objects\include\pbdom.pbd.src] that doesn't live in the repository and cannot be brought in
An explicit update tried to update the path [D:\something\ws_objects\include\pbwsclient.pbd.src] that doesn't live in the repository and cannot be brought in
An explicit update tried to update the path [D:\something\ws_objects\include\pbsoapclient.pbd.src] that doesn't live in the repository and cannot be brought in
SVN update Success.
SVN update
 ---------- Done Source Control

It appears that these are benign errors where the SVN integration doesn't recognise that the items are included from a different part of the repository and attempts to fetch them from the wrong place.

Is this something that will be addressed in the R3 release of PB 2017?

In addition to errors generated on an SVN Update, an SVN Commit will create empty folders for the PBDs under the ws_objects folder, and offer to commit the objects contained within those PBDs in the SVN Commit dialogue box, as has already been identified in another Q&A item (https://community.appeon.com/index.php/qna/q-a/pbdom170-pbd-and-native-svn).