E. Crane Computing Support Forum

Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.

You are not logged in.

#1 2005-06-13 05:16:57

Raghavendrajois
Guest

Re: PB10 - Source control issue and Build issue

We are currently working on a migration project from PB8 to PB10.

Migration goes through fine, but the problem we are facing is with,

A. Checking in migrated objects back to source control CVS w/ Jalindi Igloo.
    We are using CVS w/ Jalindi Igloo for source control.

B. Generating build using build scripts in PowerGen.
    We are using PowerGen build scripts for generating builds.

Below is the process we followed,

1. Check out all *.sr* files from all PBL's using CVS.

2. Open the workspace in PB10 to start migration.

3. Export all objects from PB10 to respective CVS folder.
Note: Unicode LE is the default, so we exported using Unicode LE encode option.

4. Checkin all the *.sr* objects through CVS.

After this, when we configured PB10 to source control,
we got message "Object exists in local project path, Press OK to overwrite or press cancel to cancel the operation".

Now we want to get pbl's and *.sr* files in sync, so we are trying to get a build taking latest *.sr* files.
But build is also failing, it gives "Incorrect release number" and other errors of this sort.

Please let us know whether the source control system we are using works fine with PB10
or if there is anything wrong in the procedure we followed.
Also please inform where can we find more information regarding this.

#2 2005-06-15 11:37:07

Phil
Guest

Re: PB10 - Source control issue and Build issue

Hi,

My guess is that the "Incorrect release number..." errors are caused by the Unicode encoding.   When checking objects in and out PowerBuilder uses the HEXASCII encoding so that the resulting objects files are pure ANSI and supported by all source code control systems.  This is what PowerGen assumes, too, when you are Syncrhonizing to these files.  Make sure you have the Import Option set for HEXASCII encoding.

The other message, "Object exists in local project path...", can be suppressed with a PowerBuilder source control option.  Maybe someone can jump in with the specific option that is needed?

Regards,

Phil

Board footer