Re: Rational Apex

[warwicks@telusplanet.net (Chris Warwick)]

In article <6q8ab6$3dg$1@newnews.startext.net>, "Glenn" <gdiehl@startext.net.nospam> wrote:
>Hello...
>
>Does anyone have any experiences using Rational Apex with an existing
>"legacy" project?  We are looking into transitioning from VADS to Apex (VADS
>support will be discontinued for the platform we are using) and I am
>concerned that our current processes (CM, etc.) will not work with Apex'
>highly integrated environment.

I find the concept of VADS support being discontinued, and Apex being the 
replacement. The VADS compiler is at the root of the Apex environment... I ran 
into this on the Sun where our upgrade after Rational bought VADS starting the 
Sun code under Apex acting like the VADS code under SCO (this was a good 
thing as we try to do as much work as possible on the Sun before going to 
SCO, and the differences were causing a few gotchas).

Apex is a small horde of 'C' shell scripts with a GUI on top, so you should 
have no problem customizing the enviroment to your current procedures. 
The things that take getting used to are the directory structure required by 
Apex, and the CM system. The CM system is odd because they copy files rather 
than creating links so your developers have the impression that they have a 
local copy of all the files, whereas Apex thinks you only have instances of 
the files...