System requirements and release notes
For release notes, see the Release Notes text file.
Platform compatibility
P4 for Eclipse 2025.2 is platform independent.
Eclipse compatibility
P4 for Eclipse 2025.2 supports the following Eclipse versions:
-
4.32
-
4.33
-
4.34
-
4.35
-
4.36
-
4.37
Server compatibility
P4 for Eclipse 2025.2 supports P4 Server 2025.2.
Older releases might work but are not supported.
Known limitations
Installation
During installation, P4 for Eclipse requires manual approval of certain dependencies.
This occurs because jarsigner now rejects weaker algorithms (MD2, MD5, RSA keys < 1024 bits, DSA keys < 1024 bits, SHA‑1). As a result, Mylyn and its related dependencies are currently flagged as unsigned.
Unsupported features
P4 for Eclipse does not support:
-
P4CONFIG,P4DIFF, orP4MERGEenvironment variables -
Editing labels
-
Refactoring between projects
Character set configuration
Do not set P4CHARSET before launching P4 for Eclipse.
If a specific character set is required, use the Charset option within the Connection dialog inside P4 for Eclipse.
Encryption requirements
Secure P4 Server require 256‑bit encryption.
However, due to export regulations in certain countries, the standard JDK ships with only 128‑bit cryptographic strength.
Users in eligible countries may enable stronger encryption by installing the Unlimited Strength JCE (Java Cryptography Extension) and replacing the default policy files:
<java-home>/lib/security/local_policy.jar <java-home>/lib/security/US_export_policy.jar
Launching P4V tools
P4 for Eclipse can launch P4V Time-Lapse View and Revision Graph.
However, due to a known Java issue on Windows, these tools cannot open files whose paths contain Unicode (non‑ASCII) characters. When this occurs, the associated actions will be disabled. For details, see the Java bug report.