Hi
I read the Help about how this would be done and don't think this will work as expected. This is from the help. Sample with additional information. My remarks are in italic.
start session
scc set connect property localprojpath "D:\temp_svn"
;localprojpath must point to the parent directory of ws_objects folder
scc set connect property logfile "D:\temp_svn\svnorca.log"
scc set connect property logappend false
scc set connect property deletetempfiles "true"
scc connect offline
scc set target "D:\temp_svn\datawindow_json.pbt" "refresh_all importonly"
scc refresh target "3pass"
....
scc close
end session
scc set connect property localprojpath -- Specifies the parent directory of the ws_objects folder. This example supposes ws_objects is located in D:\temp_svn.
-> In a bigger project the pbls are not located in the root folder (but can be copied if needed)
-> It's compile only but the parent folder will contain a lot of other files when we have a project that is not PB only
scc connect offline -- Copies the objects from ws_objects up one level, that is, to the path specified in localprojpath (and it establishes no connection with the server). Objects with the same name in different PBL files will be overwritten.
-> When working with PFC and having an own layer that contains some enhanced objects only the names of the objects in the PFE and the own XXE are equals but the files have different source code.
scc set target -- Refreshes the object list in the PBL file according to the objects copied from ws_objects. The PBG file is no longer used by the SVN/Git solution to map and refresh objects in the PBL file.
-> When adding a new file this must be in the PBL as well otherwise this won't be refreshed. To have the file in the PBL the developer must commit (and push with git) the PBL with gives for sure a conflict in the PBL when other developers do so as well.
Any other thoughts on this?
Arthur
