Version 5.0.5021

Applies to Collaborator 14.7
Collaborator 14.7 (latest version)Collaborator 14.6Collaborator 14.5Collaborator 14.4Collaborator 14.3Collaborator 14.2Collaborator 14.1Collaborator 14.0Collaborator 13.12Collaborator 13.11Collaborator 13.10Collaborator 13.9Collaborator 13.8Collaborator 13.7Collaborator 13.6Collaborator 13.5Collaborator 13.4Collaborator 13.3Collaborator 13.2Collaborator 13.1Collaborator 13.0Collaborator 12.5Collaborator 12.4Collaborator 12.3Collaborator 12.2Collaborator 12.1Collaborator 12.0Collaborator 11.5Collaborator 11.0Collaborator 10.xCollaborator 9.xCollaborator 8.xCollaborator 7.xCollaborator 6.x
, last modified on March 06, 2025

This topic describes the changes made to Collaborator 5.0.5021. For information on the changes made to other versions of the product, see Version History.

  • added — log author prep time while in planning phase (Case 47593)

  • fixed — Check for compatible product version before trying to restore from a dump file (Case 47869)

  • fixed — Upgrade to JavaMail for defect causing email notifications to stop (Case 45913)

  • fixed — Report filters display incomprehensible error messages (Case 47768)

  • fixed — server should install license file with the EULA (Case 47946)

  • fixed — Handle Perforce SubmitOptions: revertunchanged (Case 47488)

  • fixed — Remove Restore Defaults button from Server Connection preferences page (Case 47950)

  • fixed — Error adding a Subversion revision with Eclipse plugin

  • fixed — Typo in the mandatory subscriptions error message (Case 47469)

  • fixed — do not specify "-Q utf8" when the customer specifies "p4commandcharset none" (Case 47032)

  • fixed — Unrecognized TFS date format for zh_TW locale (case 47813)

  • fixed — Spurious P4V addons message at end of the install process on when Perforce is not installed

  • fixed — Updated jdpdfimages binaries to fix null pointer when uploading PDF and subsequent PDF rendering problem (case 47879)

See Also

Version History

Highlight search results