Releases: groboclown/p4ic4idea
0.6.5 Environment host bug fixes
Version 0.6.5 of the P4 plugin for IDEA community edition is now available. It includes several bug fixes, including flexibility around the client host name value, and fixes for the upcoming IDEA 15 (142) release. You can download it from the IntelliJ plugin interface, or from github.
- Added new 'P4HOST' setting (#61).
- It overrides the JVM discovery of the client hostname.
- It will be read from the environment settings, and from the P4CONFIG
file (it cannot be altered if you use the "Client Password"
or "Authorization Ticket" connection methods).
- Bug fixes.
- If the JVM reports the hostname as including the full domain name, then
it will be stripped down to just the hostname (#61). - Fixed an IDEA 15 API incompatibility issue with file refreshing.
TheVcsFileUtil.refreshFiles(Project, Collection<VirtualFile>)
is no
longer in the API.
- If the JVM reports the hostname as including the full domain name, then
0.6.4.1 P4 Host Issues
This is a patch release of the P4 IDEA plugin, intended to debug issues in #61. It is not made available through the JetBrains plugin site.
0.6.4 IDEA 15 Bug Fixes
Version 0.6.4 of the P4 plugin for IDEA community edition is now available. It includes several bug fixes, including fixes for the up coming IDEA 15 (142) release. You can download it from the IntelliJ plugin interface, or from github.
0.6.3 SSL Fingerprints
Version 0.6.3 of the P4 plugin for InteliJ community edition is now available. It includes support for SSL fingerprints when connecting to a SSL-enabled perforce server, and several bug fixes. You can download it from the IntelliJ plugin interface, or from github.
v0.6.2 Connection fixes
Version 0.6.2 of the P4 plugin for InteliJ community edition is now available. It includes several bug fixes. You can download it from the IntelliJ plugin interface, or from github.
- Bug fixes.
- If the user's P4CONFIG environment variable or windows registry setting is set,
it can still be loaded, even if the user doesn't want to use those settings.
This isn't a problem unless a relative path is used, in which case a strange
"FileNotFoundException" will be generated. - The default changelist will show up as the synthetic text font (by default, blue),
rather than looking like the active changelist color. This avoids confusion
if the active changelist is not the default changelist. - Relative configs could still report problems on the "check config" button.
- If the user's P4CONFIG environment variable or windows registry setting is set,
0.6.1 Preferences, SSL, and Bugs
Version 0.6.1 of the P4 plugin for InteliJ community edition is now available. It now supports global user preferences, basic SSL support, as well as many bug fixes. You can download it from the IntelliJ plugin interface, or from github.
- Add user preferences (#39)
- User preferences are available on the Perforce configuration
panel, in a new tab. The current options are for setting the maximum
number of open connections to each server, and the maximum timeout
for waiting on those connections.
- User preferences are available on the Perforce configuration
- Begin SSL support (#5)
- Standard Java does not support the 256-bit encryption level ciphers required by the
Perforce server. You must download and install the unlimited strength JCE package
for the IDE's JRE in order to connect to an SSL-enabled Perforce server. - Added support for specifying the Perforce server SSL fingerprint.
- Start of trust support for server connections. Still needs correct
wiring to allow the user to be notified of fingerprint changes, and
for correct authenticating of the fingerprints. It will reuse
the SSL trust ticket if the user has already authenticated (with "p4 trust")
the connection.
- Standard Java does not support the 256-bit encryption level ciphers required by the
- Bug fixes.
- Client selection drop-down is disabled (#53)
- NPE in Authorization Ticket connection when selecting the file chooser (#54)
- Bad display of P4PORT text field tooltip.
- Fixed error if the client is disconnected while refreshing the changelist view.
- Fixed error when choosing "Specific P4CONFIG file" related to incorrect widget
initialization. - De-register VCS module on project close (#55)
0.6.0 Update to revision
Version 0.6.0 of the P4 plugin for InteliJ community edition is now available. It now supports specifying a revision when updating the local files against the depot, as well as many bug fixes. You can download it from the IntelliJ plugin interface, or from github.
- Allow selecting the revision or changelist to sync to (#29).
- Now the menu option "Update files..." brings up a dialog that allows the
user to select which revision to sync to (head, revision#
value,
changelist etc.@
value), as well as whether to force the sync.
- Now the menu option "Update files..." brings up a dialog that allows the
- Synchronizing on a checked-out file does not report future merge problem (#30).
- If a synchronize will cause a future merge issue, you will now see an
error reported with the details. The sync will still happen.
- If a synchronize will cause a future merge issue, you will now see an
- Bug fixes.
- Code cleanup.
- Reduced logging.
0.5.5 Full diff support
Version 0.5.5 of the P4 plugin for InteliJ community edition is now available. It now supports performing a diff against any version of the file in the branch history. You can download it from the IntelliJ plugin interface, or from github.
- Full file history support (#47).
- File history used to not show branching history if it went outside the current client. Now, it will show
a full history of the file, and allow for diffing against any part of the depot in which the user has
read access. It's available through the file context menu, under P4 -> Compare with...
- File history used to not show branching history if it went outside the current client. Now, it will show
- Bug fixes.
- Fixed error when handling deletion of files not owned by Perforce.
- Fixed a lag issue related to saving files when working offline.
- Minor code cleanups.
0.5.4 Stabalization
Version 0.5.4 of the P4 plugin for InteliJ community edition is now available. It includes a major fix to the way in which changelists are reloaded. You can download it from the IntelliJ plugin interface, or from github.
- Bug fixes.
- Changelists refresh event may be incorrectly skipped (#45)
This fix keeps the timeout, but changes it to a cache expiration concept.
IntelliJ can call the changelist refresh multiple times very quickly, so
this addition will maintain a short-lived cache that will be reused as
long as IntelliJ indicates that no IDE-managed files need updates.
When the cache expires (currently set at 10 seconds), the server
will be queried at the next refresh time.
- Changelists refresh event may be incorrectly skipped (#45)
0.5.3 Revert unchanged files Release
Version 0.5.3 of the P4 plugin for InteliJ community edition is now available. It includes adding the ability to revert unchanged files from changelists or files, and adds in synchronize to the file context menu, as well as a few bug fixes. You can download it from the IntelliJ plugin interface, or from github.
- Added "Update files" to file context menu to allow easy synchronization with depot.
- Right click on the Project view file or directory, select the P4 sub-menu,
and the Update files... option will synchronize to the head revision.
- Right click on the Project view file or directory, select the P4 sub-menu,
- Added "Revert unchanged files" to file context menu and changelist context menu.
- Right click on a changelist in the Version Control view, and select "Revert unchanged".
All files in the changelist, for all clients, will be reverted if they have not
been altered from the depot version. - Right click on selected files in the project view, and select "Revert unchanged".
All files in the changelist, for all clients, will be reverted if they have not
been altered from the depot version.
- Right click on a changelist in the Version Control view, and select "Revert unchanged".
- Bug fixes.
- Improved support for rollback of files that aren't explicitly checked out by Perforce.
- Add missing tooltips on UI elements (#43)