-
Justin Wolbeck
- PowerBuilder
- Thursday, 22 January 2026 04:11 PM UTC
We recently migrated to PB 2025 and wanted to take advantage of the new Solution features. As part of this, we converted our workspace to a solution and are attempting to migrate from SCC to the native SVN integration. I came up with some steps to preserve all of our SVN history by checking in the pbl folder then manually moving the source files into the pbl sub folder and that seemed to work.
The issue we are having is when we attempt to do a SVN Commit at the Project (Target) level it shows all files in the Project need to be (added):

But if you do this same action outside of PowerBuilder it correctly shows nothing has changed.
Doing the Commit on an individual PBL folder (ar_elements in this case show below) PowerBuilder correctly shows nothing has changed:

This presents an issue when doing mass check-ins across multiple PBLs as even files you have modifications for show as "(added)" when they should be marked as (modified). Doing a commit on these files improperly flagged as (added) doesn't result in anything sent to the SVN server.
I have tried both build 3726 and I have now tried PB 2025 R2 Beta build 6267 and we have the same issue in both versions. Any thoughts on what might be going on here?
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.