When importing an exported make file, the error message 'Failed to parse make file at line 19#5' is received. The actual line number will vary depending on the actual make file, but the general message is always the same.
In order for the information to display after check out, it is important to set the 'generate meta data method' check box to enabled. This is found under Window --> Options, select Visual Composition, then select Code Generation. Enabling this option will allow you to export as .java files and maintain the visual information by generating a getBuilderData() method.
1. Check to make sure RCS is installed by doing 'which rcs' 2. If the comm agent is running under root then 'which rcs' should show the path where RCS is installed or export the path to point to RCS location
These changes are only saved back into the Production at checkin. A work around is to use the export utility with VA Java. This will allow the development area to reflect saved changes with the VA Java workarea without having to do a checkin.
11529 Licensing issue using Oracle repository 11555 DS make unable to export or make when there is large number of targets 11558 Form Designer unable to access forms without Object designer license.
With the same name "eChange Man -> Serena Web Services Database Migration Utility". Click on export . After you click on export, you might get some errors with references to duplicate keys.
