This file lists the recent defects fixed in Version Manager. For information on installing and using the current release of Version Manager, see the <Install_Directory>\vm\readmevm.html file.
NOTES:
If you assign a version label or promotion group that matches a revision number to a different revision, you can no longer access the revision with the matching number using the desktop client, the web client, or the PCLI. For example, if you apply the label "1.5" to revision number 1.7, it is longer be possible to access revision 1.5, because attempts to access revision 1.5 yield revision 1.7.
This has been resolved. Whenever the Revision field or corresponding PCLI option (-r) has a value that looks like a revision number (like 1.5 or 1.4.2.1), Version Manager tries to get a matching revision number and not check whether there is a label or group by that name. If you need to use the Revision field or corresponding PCLI option to access a version label or promotion group that looks like a revision number, precede that label or group with a backslash (\).
Caution: In dialog boxes where you pick a label or group from a list, this release of Version Manager does not automatically precede the label or group with a backslash when the label or group looks like a revision number.
To avoid confusion, we strongly recommend never using labels or groups that look like revision numbers.
This has been fixed. See DEF78155.
This has been fixed.
This has been fixed.
If you execute vsplit -u from the directory containing the metadata archive, the archive may be deleted.
This has been fixed.
This has been fixed.
This has been fixed.
In certain circumstances, unsplitting a split archive will cause the metadata of the new unsplit archive to reflect the information stored in the delta.d file.
This has been fixed.
Using the Version Manager web client with an Apache 1.3.x server configured to use EAPI produces an error when you try to start the Apache server. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Following the otherwise successful completion of a command or script, PCLI prints:
Exception in thread "main" java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next(Hashtable.java:976)
at pvcs.vm.VmFlexFactory.checkinAllLicenses(VmFlexFactory.java:52)
at pvcs.cmd.CmdProcessor.pcliMain(CmdProcessor.java:202)
at pvcs.cmd.CmdProcessor.main(CmdProcessor.java:174)
This issue has been resolved.
When the Version Manager desktop client opens on a remote X Windows display, screen updates can take a very long time.
This has been fixed.
After you perform certain operations in the project pane of the Version Manager desktop client, the project pane occasionally collapses, requiring you to browse back to your original project.
This has been fixed.
The default semaphore suffix used by vsplit (??$) results in a failure when you try to split an archive that has a dollar sign ($) in the file-name suffix.
This has been fixed. The vsplit command now supports the -C option, which you can use to pass the command a configuration file that redefines the semaphore suffix to be used (for example, SemSuffix = +-sem). For more information, see the SemSuffix directive in the Serena ChangeMan Version Manager Command-Line Reference Guide.
When an event trigger executed from a UNIX client tries to access a file on a File Server (for example, through a CLI command), that trigger fails with a SOAP FAULT message.
This has been fixed.
The description of the different types of configuration files is somewhat confusing.
This has been fixed.
This has been fixed.
If TRANSLATE is on, the "unchanged" prompt does not appear on Unix. This has been fixed.
When vtransfer -r is used only to change the case of the name of an archive, it can result in the loss of the archive.
This has been fixed.
A UNIX File Server configured to be case-insensitive sometimes treats an archve in a case-sensitive manner. Such archives are temporarily unavailable to the Version Manager clients.
This has been fixed.
The Version Manager Web Application Server process used to provide the File Server, the Version Manager Web Server, and WebDAV services sometimes shuts down on Windows systems when someone logs off from that system's console.
This has been fixed.
Attempts to run vsplit or vsql against a DBCS (double-byte character set) archive on a File Server locks up those commands. This has been fixed.
In Version Manager 8.0.2.x, the Visual SourceSafe convertor fails with the message "ERROR: PVCS_E_ACCESS_DENIED". This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Some of the default configurations in the Tomcat server used by Version Manager can expose potential vulnerablilities.
This has been fixed by switching to Tomcat 5 and by modifying and removing vulnerable configurations.
This has been fixed.
This has been fixed. For details, see the online help for the new promotion dialog boxes.
When an https: connection string is specified to connect to the File Server, the IDE integration prefixes that string with http:. This makes it impossible for the IDE integration to connect to the File Server via HTTPS.
This has been fixed.
Under certain circumstances (generally involving users logging off), the temporary files stored in the File Server client cache directory are not cleaned up on exit. This issue is being addressed by a new feature that automatically cleans up old files whenever a Version Manager session first contacts the File Server.
You can exert some control over this feature by adding entries to your islv.ini file.
NOTE: Time values are in seconds by default, but you can specify minutes or hours using the <n>m or <n>h syntax.
New settings of interest are as follows (shown with the default values that will be used if the entry is absent):
[PVCSGUI_6.5]
pvcs.fileserver.cache.cleanup.frequency=12h
Wait at least 12 hours following a cleanup operation before attempting to clean up the cache directory again.
pvcs.fileserver.cache.cleanup.age=24h
Clean up all files that are at least 24 hours old.
pvcs.fileserver.cache.cleanup.mode=m
Determine the age of the file based on its modification time ('m'). Can also be set to 'a' (file access time) or 'c' (file creation time). The default is highly recommended as some file systems could exhibit bad behavior with the other options.
NOTE: The location of the File Server client cache directory is determined by the environment variable FS_TMP or, if FS_TMP is not defined, FS_TEMP. If neither is defined, the directory defaults to %TMP%\pvcsfs or, if TMP is not defined, %TEMP%\pvcsfs.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed for the Solaris platform.
This has been fixed.
This has been fixed.
When using the browse capability for local file systems or when trying to open a project database, some users receive the following error: "There is no disk in the drive. Please insert a disk into drive A:."
This has been fixed.
Clicking the file browse button in any Version Manager web client dialog box can cause an error message to appear in the Java Console referring to an A: drive security problem. In that case, the browse dialog box does not open.
This has been fixed.
The job fails with one or more of the following messages:
VMMBI6200: verify_gets: Error: The get for: '<file_name> failed', the work file time does not match:
If the current time is within Daylight Saving Time, the error message is produced for those Version Manager workfiles that have a "last modified date" outside of Daylight Saving Time. Likewise, if the current time is outside of Daylight Saving Time, the error message is produced for those files within Daylight Saving Time.
The failure occurs only when the build directory is located on a FAT or FAT32 disk volume. It does not occur on NTFS volumes.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. Wheel mice now work correctly in the desktop client, and they work in any web client that uses version 1.4.1 or higher of the Jave Runtime Environment (JRE).
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
There is no good way to obtain the entity path for the versioned file for which an event trigger is executed.
This has been fixed. There is a new event parameter, EVENT_ENTITY_PATH, for all the event types, and the EVENT_WORKFILE parameter is enabled for the events Lock, Unlock, Promote, and Create Archive.
If a user is a member of an access list group, and that group is specifed in an archive after an empty access list group, the user cannot see the revisions even if the user has unlimited privileges.
This has been fixed.
CLI commands on UNIX interpret the SemaphoreDelay as a value expressed in seconds rather than tenths of a second. This has been fixed.
This has been fixed.
A certain combination of ACD privileges can make a user UNLIMITED. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If a specific port is specified for the license server during installation, Version Manager adds an extra @ character in islv.ini.
This has been fixed.
This has been fixed. The AddUser command now has a new -ps option for specifying a custom privilege set.
The following example creates a new user with Developer and PromoteToQA privileges:
AddUser -ps"Developer,PromoteToQA" Simba
The -ps option is not required. If you specify the option, you must include an argument specifying a list of one or more privileges. Use commas to separate multiple privileges. If the argument contains spaces, enclose it within double quotation marks.
If you do not specify the option, the new user will have the Unlimited privilege set.
If the default font size used by Version Manager is too small in the your UNIX environment, you can increase the font size through the pvcs.fontSize property; however, some dialog boxes do not reflect the change.
This has been fixed.
This has been fixed.
This has been fixed.
If you are a member of multiple privilege sets and one of these privilege sets is restricted to a promotion group, attempts to view the Granted Privileges on an archive (right-click | Properties) generates a Java exception (Windows) or causes a crash of the desktop client (UNIX).
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed. The command now returns –1 if the import fails.
This problem occurs when your Access Control Database has a file-name extension of .acd.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
In a heterogeneous environment where the Client Name of a Path Map is specified as "windows style", a UNIX client cannot read the pvcsldap.ini file from the File Server.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Using the Diff/Merge tool from the Version Manager web client on UNIX shows the revision contents in DOS style, even if the archive being examined has the TRANSLATE archive attribute enabled. If you compare a revision against a checked-out workfile that has TRANSLATE enabled, the Diff/Merge tools reports all lines as being different.
This has been fixed.
This has been fixed.
This has been fixed.
When the user ID is the same throughout the PDB but the password is different among projects or subprojects, the login dialog box does not appear when the user selects the plus sign (without selecting the folder) to expand a project or subproject tree.
This has been fixed.
If you check in an unchanged file, and the option to not check in an unchanged file is enabled, the file is unlocked as expected, but a prompt asks whether you want to merge the branch to the tip (even though there may be no branch revision).
This has been fixed.
This has been fixed.
This has been fixed.
When you delete a file from your workspace, you get the option of deleting the file from the Source Control Tool; however, if you do not delete the file from the project at that time, you do not get the option again when you run synchronize.
This has been fixed.
This has been fixed.
This has been fixed.
If a version label starts with a digit, the PCLI isDifferent command fails, and the error message displays the wrong version label.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
When the $(Command) alias is used in configuration files, it incorrectly identifies PCLI as "VMGUI" on UNIX and Linux platforms.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
Access to a File Server PDB is denied when you log in using a DBCS (double-byte character system) ID. This has been fixed.
If your ARCHIVEWORK and WORKDIR directories point to a slow drive, such as a network volume, attempts to update an archive on the File Server may corrupt the archive. Because ARCHIVEWORK and WORKDIR default to the current directory for command-line interface (CLI) operations, you could trigger this result just by running a CLI command when the current directory is a mapped network drive, or even by using a local drive on a busy system.
This has been fixed.
This has been fixed.
The security report (Admin | Security | Show Report) shows the passwords stored in the ACD if the user running the report is a SUPERUSER. Because it is fairly easy for an UNLIMITED user to become a SUPERUSER, we need a way to disable this feature.
This has been fixed. By default, the Security Report no longer shows passwords, even if the user running the report is a SUPERUSER.
To allow a SUPERUSER to see passwords (as they could prior to this change), there must be a file called:
VM_Install_Dir/vm/common/pvcsprop/pvcs/vm/security.properties
with these contents:
vm.showpasswords=enabled
This has been fixed.
New revisions are not created when you check in files from Interdev. This has been fixed.
This has been fixed.
When the File Server and the Version Manager web server are running in the same instance of Tomcat, journal files and reference directories are sometimes modified with information pertaining to delta.d file changes. This has been fixed.
The setting of the %TEMP%, %FS_TEMP%, and %FS_TMP% directory environment variables can cause heap corruption that leads to Java "unknown exception" and other failures. This has been fixed.
These occur if there is no diskspace left on the Temp directory defined under File Server Administrator | Options. This has been fixed.
If temporary directories are not specified, temporary archive files get created in the product installation directory. This has been fixed.
This has been fixed.
This has been fixed.
With LDAP authentication in place, users sometimes receive an error stating that they lack the privileges to access files. This has been fixed.
This has been fixed.
The documentation suggests that a read-only network share is a valid location for the servers.ini file; however, this configuration causes error conditions.
This has been fixed; the product now supports this documented configuration.
If the chosen or default device-specific temp directory is invalid because the specified name already exists as a file name, attempts to update files through the Version Manager File Server result in these files being replaced by 0-byte files.
This has been fixed; an appropriate warning now appears.
When you run the vsplit command, the .??$ semaphore file that gets created for the archive does not get removed. This has been fixed.
This has been fixed. The section on licensing workstation installs has been removed; the subject is covered correctly in another part of the guide.
This has been fixed.
The default location for the new pvcsldap.ini file is the Version Manager installation directory, which causes problems when the Version Manager installation is local.
This has been fixed; the default location is now the root of the PDB.
If the case of the login ID returned by the HOST login source changes (for example, as a result of the customer switching domains) in a case-insensitive PDB, the private workspaces for the users are permanently deleted. This has been fixed.
To preserve path names with spaces in an @list, you normally need to enclose the invidual path names within quotation marks; however, the vsplit command silently ignores quoted path names. This has been fixed.
The file server client does not honor the total cache file size limit. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
If you are using version 4.0 or 4.0.1 of Collage and you try to interface Version Manager and Collage, the files are not uploaded to Collage. This has been fixed.
This has been fixed.
Populating your Access Control Database by adding authenticated LDAP users using the auto-create feature doesn't work if you are using the Version Manager web client. This has been fixed.
This has been fixed.
The documentation incorrectly refers to a Tracker project rather than a Tracker server in connection with configuring servlets. This has been fixed.
This has been fixed.
Though we are shipping mod_jk 1.2.1 for Apache 1.3, a customer noticed that we are still shipping the 1.2.0 release for Apache 2.0 on Solaris. This has been fixed.
If you run VSPLIT on archives stored on the File Server, and the archives contain an AccessList at the time of the split, attempts to retrieve revisions from the archives will fail. This has been fixed.
When you use Version Manager Server 7.5.1.0 on Windows with a client on Solaris, the execuatlable bits of a read-only workfile are lost after a check-in. This has been fixed.
This has been fixed.
From within an IDE, performing a Show History operation on revisions locked by a specific user returns all users. This has been fixed.
If a user that does not have version label permissions within WSAD connects to a Version Manager Project Database and attempts to label a file from within WSAD, the operation seems to proceed with no errors; however, viewing the file in Version Manager reveals that it does not contain the version label. This has been fixed.
This has been fixed.
This has been fixed.
This has been fixed.
UNIX: Any attempt to start the Version Manager web server with daemons enabled produces an error.
This has been fixed.
When a sufficiently large promotion model is being edited in the desktop client, it gets deleted from the CFG file. This has been fixed.
This has been fixed.
When not utilizing File Server, Version Manager should recognize a split archive and display a useful message stating that the archive is split and must be referenced through a file server. This has been implemented.
Changes made to web.xml are not read until the server is restarted, and may cause incorrect operation of the server. This has been fixed.
Licenses allocated to Version Manager web-client user sessions are never returned to the license pool; the license should be returned to the pool five minutes after the user logs out from the web client.
This has been fixed.
The client appears to work but applet operations fail. This has been fixed.
When the customer performs simultaneous Show History operations on multiple PDBs (in multiple browser windows), Version Manager hangs. This has been fixed.
This has been fixed.
On a multiple-file check-in or add, the Use Change Description for all check box is not selected by default. This has been fixed.
If you set up a post-put event trigger, configure the PDB to remove the lock on an unchanged file, check out a file without changing it, check in the file with "Prompt" selected for unchanged workfiles and with "Keep read-only workfile" selected, and reply "no" when asked if you want to check in an unchanged file, an event trigger fires even though no check-in occurred. This has been fixed.
This has been fixed.
If you perform an action that results in an error in the desktop client, the Details window takes about five seconds to auto-expand. This has been fixed.
The documentation for the pcli list -ca command contains errors (:= should be =). This has been fixed.
If the selected workfile location does not match the project's default location, selecting "Don't check in workfile" changes the default workfile location. This has been fixed.
The comma should remain the default delimiter. This has been fixed.
The PCLI manual contains references to PCLI PR and PCLI ID (without the underscore). This has been fixed.
In the Add Workfiles dialog box, clicking the Browse button sometimes displays a path with an extra \*.*. This has been fixed.
This has been fixed.
When checking if the allusers.ser data in memory is out of date compared with the persistent data, the code looks for the file in the wrong directory. This has been fixed.
If you modify an existing user to have an expiration date of today (or any date before today), a blank dialog box appears and cannot be dismissed except through the Windows Task Manager. This has been fixed.
The IsDifferent command always performs the comparison against the tip rather than the default revision. This has been fixed.
When you enter a new user name in the Switch User dialog box, the user name in the status bar is sometimes repainted incorrectly. This has been fixed.
The -v option should be treated as a label and accept numeric characters without requiring escape characters. This has been fixed.
This has been fixed.
This has been fixed.
The PCLI commands ImportArchives and AddFiles do not observe the Run options -y, -n and -np. Instead of accepting the Yes, No, and No Prompt options being passed through Run, the functions still pass the question to the user.
This has been fixed.
This has been fixed.
If you try to update an ACD file (for example, add a user) and the ACD file is flagged by the operating system as being in use (for example, because another process is reading the file), the ACD file is deleted and must be restored from backup. This has been fixed.
During import, , a corrupt archive will generate the error "Unexpected error: java.lang.NullPointerException" and halt the process. This has been fixed.
This has been fixed.
On a branch, checking in a file creates a new revision even with a "remove lock if unchanged" option selected ("Don't check in" or "Prompt" when the file is unchanged). This has been fixed.
This has been fixed.
You can no longer highlight a project by selecting the Project Database root on the left side (Project Pane) and then typing the first letter of the project you want to work on. This has been fixed.
"Show Journal" doesn't display the proper journal information when the "Date Range" is set from the morning of the current day to the night of current day, even though actions have taken place on the versioned file during the current day. This has been fixed.
If you run two exports within a few seconds of each other, duplicate IDs can occur. This should be avoided, and a note has been added to the documentation.
When archive operations are performed between midnight and 1:00 AM during Daylight Savings Time, the date incorrectly specifies the previous day. This has been fixed.
This has been fixed.
The -a option of the Readline command should be able to assign the individual words in a line of input to elements of an array; however, all words are placed into the first array element. This has been fixed.
The Version Manager product link is out of date in the installation guide. This has been fixed.
When you edit a large promotion model in the desktop client, the model gets deleted from the configuration file. This has been fixed.
The installation does not allow you to select a Program Folder for all users on the machine; it lets you select a Program Folder only for the current user. This has been fixed.
When you access a project database through a file server, the journal files do not get created or updated with your last action. This has been fixed.
The vtransfer command option -f to fix a RevLib path does not work. This has been fixed.
When accessing a project database through a file server, you may get lock errors after attempting to check in files. This has been fixed.
In the desktop client and web client, long label names are not allowed to fill up the available space in the Filter Selection list, and so get unnecessarily truncated. This has been fixed.
In the desktop client and web client, long label names are not allowed to fill up the available space in the Filter Selection list, and so get unnecessarily truncated. This has been fixed.
On a multiple-file check-in or add, the Use Change Description for all check box is not selected by default. This has been fixed.
This has been fixed.
You do not receive a prompt to enter different passwords to enter subprojects with a different password for the same User ID. This has been fixed.
On check-in of an unmodified workfile, the "modified" date is changed if an UnconditionalPrePut event trigger is defined for that project. This has been fixed.
This has been fixed.
If you are using a Netscape browser and you resize the results window during a checkout, the action is aborted and the results information is lost. This has been fixed.
The VMINET.HTML page, the vminet_install.html page, and the sample project database servlet page come up blank when you try to access them in your web browser. This has been fixed.
This has been fixed.
For Eclipse-based IDEs, the Merant menu and the source-control glyphs are not enabled by default. The information is saved in the user workspace, so you have to enable the menu and glyphs for each new workspace you create. This has been fixed.
When the TD plug-in is installed, it should create the following registry key:
HKEY_LOCAL_MACHINE->SOFTWARE->Mercury Interactive->Version Manager->Test Type
The value of the string should contain the test types for TD, separated by commas.
This has been fixed.
An "Unable to get file" error occurs during a Get that includes Get latest version of... or Refresh Project View. This has been fixed.
This has been fixed.
This has been fixed.
If you select a file in the default workfile location and attempt to associate an SCR, nothing appears to happen. If you click the button again, the following error is returned: Empty Selection Set: Browse to select directories or files. This has been fixed.
When an item under source control is opened by an external application, such as MS Word, and the user performs a GET function through the IDE, the GET fails. This is correct behavior; however, in Version Manager 7.5.1.0, no error is passed, and the user is not alerted to the failure. This has been fixed.
Creating a plug-in project in an Eclipse-based IDE creates a file named plugin.xml. If you try to modify a field in that file, a dialog box prompts you to check out the file (even if the file is already checked out). Clicking Yes or No does not dismiss the dialog box or provide a way to check in the modified file. Shutting down the IDE through the Task Manager is the only way to dismiss the dialog box.
This has been fixed.
Menu items that spawn dialog boxes are not followed by an ellipsis. This has been fixed.
When you modify the properties for the Web Project, the .websettings file does not get checked out, and an error is generated. This has been fixed.
The .classpath file stores the java class path for the application. This file can contain custom directory values that are specific to the current user workstation. The .classpath file is getting automatically checked out and can cause problems when a modified version is checked back in.
This has been fixed: The user can now "disconnect" the .classpath file.
This release is primarily intended to provide compatibility with Merant® MoverTM. If you wish to use Merant Mover with Version Manager, you must install this release or upgrade to Version Manager 8.
Version Manager may shut down when trying to connect to a Microsoft Active Directory Server via Secure Socket Layer. This has been fixed.
As of Version Manager 7.5.1.0, the PCLI List output format for the Archive:LockInfo attribute was inadvertently changed, which can adversely affect scripts parsing this output. With the 7.5.1.5 patch, the original format has been restored.
Double-clicking the Create or Duplicate buttons on the Create User or Duplicate User dialog boxes may corrupt the list of valid users and prevent login to the project database. This has been fixed.
NOTE: If you have experienced this problem prior to installing the 7.5.1.4 patch, you may now see the following message when opening the affected project database (PDB):
[Warning] A user with a blank (null) name was found in allusers.ser. Your access control database might have lost some users--restoring from backup is recommended.
In that case, it is recommended that you restore the related access control database file (e.g. access.db) from backup. The warning message when you open the PDB will persist until a user is added or removed, unless the allusers.ser file was also restored (from backup or from allusers.old).
The results produced by the difference tool can be affected by the order in which the files are selected. This has been fixed.
A long path (over 200 characters) to a Version Manager configuration file may cause operations to fail. This has been fixed.
The Development Interface does not work correctly with SCC and Eclipse IDEs on Windows NT systems. This has been fixed.
If a reference directory is defined for a project but that directory does not exist, you will not be able to add files to source control for that project. This has been fixed.
Visual Studio .NET web projects located on remote servers end up with flat file structures when added to source control. This has been fixed.
If a reference directory is defined for a project but that directory does not exist, you will not be able to add files to source control for that project. This has been fixed.
On Windows, if a CodePage other than 1252 is used, the German umlaut characters are not displayed correctly. This has been fixed.
NOTE: You can change or query your CodePage from a Command Prompt using the command chcp.
If a user is not defined in the access control database for a project and that user double-clicks a project to open it, the GUI locks up and displays the error message: "Access to this project has been denied because your login account is invalid". This has been fixed.
If you enter the name of an existing promotion group in an attempt to rename that promotion group using Configure Project, the GUI gets stuck in a loop and locks up. This has been fixed.
There was no way to turn off the display of the Banner Header when running a PCLI command. This is now possible by passing PCLI the option -nb (No Banner), or by assigning a value to the environment variable PVCS_NO_BANNER. This new environment variable is honored by all Version Manager commands.
The nfsmap file is not used by the command-line executables vcompress, vdel, vdiff, vsql, readdb, and makedb. This has been fixed.
If you merely lock an archive, rather than doing a checkout with a lock, and then browse to a different file at check-in, Version Manager checks in the file without a warning. This has been fixed.
If you check out files in a project to different locations, either manually or by using different workspaces, you cannot check them in as a group; Version Manager defaults to the workfile location for the project and does not use the check-out location embedded in the archive. This has been fixed.
The command ss dir $/pinned returns a list of items in the project specified. When a file is pinned, the file name is returned with a semicolon and a number to append to it. This has been fixed.
In previous versions of Version Manager, it was nearly impossible to promote a revision or assign a promotion group from within a PCLI script. The commands AssignGroup, ChangeGroup, DeleteGroup and PromoteGroup have been added to PCLI to fix this. See the readme file for a description and syntax of these commands.
If a file was checked out using the root workspace setting, then the user switched to a new workspace and checked the file out again, Version Manager produced two locks with workfiles in different locations. When checking in the file, Version Manager did not know which workspace was used to check out the archive and might check in the wrong version. This has been fixed.
The PCLI DeleteUser and AddUser commands takes any quotation marks around a name, making it impossible to create or delete certain valid names. This has been fixed.
If you modify an existing change description, the journal file entry is limited to 200 characters. This produces errors when you run the journal report causing, in some cases, an "Unknown Exception" error. This has been fixed.
When a user types a file basename (a name without a path) in the From field of the Add Workfiles dialog box, Version Manager creates a project with the name of that file. This has been fixed.
If branch revisions between the trunk and tip are deleted, the trunk is not able to attach itself to a branch. The VSS Converter tool is unable to build a branch. This has been fixed.
Tracker and Version Manager automatically pop up marketing messages in the What's New and What's Coming topics after a fresh installation. It is possible to turn off these help messages. Contact Answerline for assistance.
When users made changes to the configuration files, disallow statements were appended to the configuration file. The customer would need to remove the disallow statements that were appended to the configuration file, but when a change was made, the disallow statements were appended again. This has been fixed.
Version Manager on Windows platforms could fail a project move operation because the directory being moved was "in use", resulting in error messages such as: "Could not rename "\\server\share\...\old_dir\P2tkjy.prj" to "\\server\share\...\new_dir\P2tkjy.prj". This has been fixed.
If iPlanet 6.0 files are set up incorrectly, users would receive Init links in the wrong file and partial tag definitions. This has been fixed.
The web server error log recorded the error: "file does not exist <path>BKGRD.gif". This file was called by a number of pages and the log could grow very large affecting performance. This has been fixed.
VM I-Net would produce the error: "Could not find a revision assigned with the version label, 1.*, in the archive <path><file name-arc>" when users would try to run a diff report. This has been fixed.
When you use Apache with VM I-Net, the attempt to hit the servlet or "install program" generates a segmentation violation in the active Apache thread. It reports the error: "[warn] Loaded DSO <Pathname_to_mod_jk> uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI)"
This has been fixed.
If a user's workstation display settings were set to "high contrast black", the names of the projects were not visible with the black background. This has been fixed.
A user may connect to the target machine and deliver several requests with invalid chunked coded body. VM I-Net now includes mod_jk 1.2.1, which no longer suffers from this problem.
The tomcat.sh script did not calculate JAVACMD if the environment variable already existed. If a user already had this variable, VM I-Net would not use Merant's JVM. This has been fixed.
The remove command in the pvcsstart.sh script that clears Tomcat's work directory would require a response if any file in that directory is read-only. This has been fixed.
When you test the connection to large LDAP databases, the test may fail and return a "Sizelimit Exceeded" error. This has been fixed.
If the path to the journal file is incorrect or if the journal file is missing, an error may appear which does not mention the journal file. This has been fixed.
The command-line strips the leading slash from quoted UNC paths. This has been fixed. NOTE: This fix is still compatible with old scripts that use extra slashes in order to compensate for the previous behavior.
The correct VB include file is now in the DTK installation.
If you use PCLI to expand an empty @file list, it will produce a Java exception error. This has been fixed.
"PCLI list -caDefaultVersion" does not give the correct value if the default label is defined for the parent project. This has been fixed.
This has been fixed.
An invalid tool tip sometimes appears when you resize panes. Attempting to drag this window causes a core dump. This has been fixed.
PCLI fails to pass exit codes back to the environment. This has been fixed.
If you browse for the directory to "Copy To" during a check-out or get operation and the default directory does not exist, the operation may fail. This has been fixed.
There is not an easy way to save the output of the Results dialog box. This has been fixed. One can now copy the entire output or multi select individual items to be copied.
The installer did not accept 14-digit serial numbers. This has been fixed.
If the boolean function in the PCLI if command failed (without returning a value), a Null Pointer exception could result. This has been corrected.
Running the PCLI IsDifferent command used to result in many temporary files being created and left behind. This has been corrected.
If the source directory for a workstation installation was read-only, the VM install program did not correctly identify the options available for installation from that directory. This has been fixed: You can now write-protect the source directory for workstation installs.
If you specified a journal file name while running a Journal Report from the VM GUI, VM would just look in the application binary directory for the journal files, not in each archive directory as it should have. Correct location for the Journal files are searched, and Journal reports now contain all the appropriate info.
If PCLI VMCopy was called with no parameters, an exception was reported. This has been fixed.
Documentation about how to enable daemons was clarified / corrected.
If your project database has multiple configuration files and you use a recursive view in the VM GUI and also apply a filter to that view, the display is updated too frequently. This has been fixed.
Cannot not install the integration to Eclipse/WSAD by itself. This has been fixed.
This has been fixed. NOTE: See the Version Manager readme file for information about using Sun's 1.4.0x JRE and Internet Explorer with TrackerLink.
Users may be locked out of a project database when all of the following occur:
This scenario can no longer occur.
readdb outputs user ID expiration dates in a different format than that expected by makedb. This has been fixed.
From time to time, the \tomcat\work\localhost8080 directory must be cleaned out or VM I-Net will no load correctly. This has been fixed. The directory is now regenerated whenever VM I-Net Server is restarted.
Viewing file properties of archives created with Version Manager 3.2 or older will result in an error. This has been fixed.
If you set a value for TOMCAT_INSTALL or CLASSPATH in your environment, those values could interfere with the correct operation of VM I-Net. The VM I-Net startup scripts have been modified to prevent this problem from occurring.
End Release Notes
Copyright © 2003–2005 Serena Software, Inc. All rights reserved.
$Revision: 1.97 $