Currently I'm trying to evaluate the use of PVCS Tracker 6 along
with PVCS VM (Version Manager) 6.5 and Sybase PowerBuider.
PB and VM integrate rather fine, PowerBuilder's "Library Painter"
has an interated checkout/checkin feature making it unnecessary
to cope with the Version Manager GUI, as far as the PowerBuilder
objects are concerned.
The integration of PVCS Tracker and Version Manager includes
the association of SCRs (System Change Requests) with
actions in VM (like checkin), as well as submitting new SCRs
or update existing ones (TrackerLink), or doing checkout/-ins
from within Tracker (Update/Checkout,-in).
So far, so good ... but there seem to be no integration
of Tracker with PowerBuilder, since the PB Library Painter's
Checkout/-in dialogs are not modified by Tracker's installation
(as opposed to Version Manager, which afterwards had a new button
"Associate SCRs" on the Checkin dialog, and the TrackerLink menu
item under the "Admin").
Is there any way to reach a higher integration ? Checking out
PowerBuilder objects with the Version Manager GUI is only
theoretically possible, since the text files VM stores for
PowerBuilder objects can not be imported into PowerBuilder
directly. You have to add a header line with $pbexport$<object_name>
before export, import it into a work library, modify it there,
export it, delete the $pbexport$ line, check back in
and then synchronize the PowerBuilder Library the object was registered
in. That's simply impossible to perform ...
Any opinions, ideas or insights how to reach a satisfiable
level of integration of the three tools ?
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.