Hi,

Just thought I would let people know of a little problem we came across in using GIT and OrcaScr190, took a while to figure out but pretty obvious once the problem was identified.

We have a large application of over 100 libraries and we use GIT as source control, just migrated from visual source safe. As part of this process we introduced an automated build process which would involve getting the latest version of the code and then issuing a command to get OrcaScr190 to rebuild the pbl's. At this point we realised that older versions of our objects were getting introduced in some libraries and the only way to resolve was to open PB2019 and do a refresh on the workspace, GIT was smart enough to realise what was in the pbl did not match the version in ws_objects directory. Checking library lists and pbl's we struggled to identify where the older version was getting introduced. Eventually chased this back to a rogue pbl existing in the ws_objects folder, containing the older versions.

OrcaScr190 seems to flatten the ws_objects directory and create the pbg files for all pbl folders that it contains, which it creates the pbl's from. Our problem was that the rogue pbl which was not in the target file was also extracted to root folder causing the newer objects to be overwritten and then when it starts taking the objects and placing in the pbl's it only has the old version.

Make sure that the ws_objects directory only contains the pbls that you expect to be there. hopefully this will provide useful for someone. It also highlights that if you have objects in different libraries that share the same name then OrcaScr190 will not be the best option to rebuild your pbl's, unless you introduce the manual refresh within PB2019 to finish off, kind of starts to move away from automation though.

Thanks

Gary