The Perforce Plug-in for Eclipse and WebSphere Studio

P4WSAD, the Perforce Plug-in for Eclipse and WebSphere Studio, enables you to access Perforce from within the Eclipse IDE and the Rational/WebSphere Studio WorkBench family of products, including:

  • 3.2.x through 3.5.x (Release Builds only)
  • IBM Rational Application Developer 7 (based on Eclipse 3.2)

The P4WSAD 2006.2 release is still available for Eclipse 2.x and IDEs based on Eclipse 2.x. See the Release Notes for details.

P4WSAD Features

  • Support for all basic Perforce file operations.
  • Views for pending changelists, submitted changelists, revision histories, and a Perforce console.
  • Synchronize view to display incoming, outgoing, and conflicting changes.
  • Batch resolve of files.
  • Built-in differencing, job support, rename, and move.
  • Support for automatic file checkout and numbered changelists.
  • Decorations for Perforce-managed files, including indicators for files that are synced, opened, locked, or unresolved.
  • UTF-8 is supported for Unicode-enabled servers.
  • Work offline when the connection to the Perforce Server is not available.
  • Check Consistency Option: You can check your workspace for files not under Perforce control, files that are changed but not open for edit, and files that are missing but not open for delete. This is especially useful when reconnecting after having worked offline.

New Features included for Release 2009.1

  • Support for renaming and moving files multiple times prior to submitting.
  • Support for adding and editing jobs, browsing labels and branch-based integrations.
  • Integration with Perforce Visual Client tools: Time-lapse View, Revision Graph, and P4Merge.
  • New P4 Connection wizard verifies server availability, creates new Perforce client workspaces, and imports projects from the depot..
  • See the Release Notes for a complete list.

New Features included for Beta Release 2009.2

  • P4WSAD now has a full Eclipse-based Time-lapse View (TLV). This view displays detailed change history of text files that are stored in the depot. TLV can leverage various Eclipse built-in capabilities for language specific highlighting when using Eclipse 3.4+.
  • Added support for the new shelving server feature, which enables you to store work-in-progress files in the server without submitting them. Other users have access to your shelved files.
  • Improved history view now uses the standard Eclipse history view.
  • New Branches view enables you to manage Perforce branch specifications in Eclipse.
  • See the Beta Release Notes for a complete list.

Perforce Compatibility

  • P4WSAD 2009.1 can be used with Perforce Server versions 2005.2 and above. Optionally, the plug-in requires a p4 command line client of version 2005.2 or later.
  • P4WSAD is supported only on Windows XP/2003/Vista, Mac OS 10.5, and Linux (x86/GTK 2).

Installation

  • Please uninstall any previous version of P4WSAD prior to installing this version. Uninstall instructions can be found in the P4WSAD Release Notes.
  • To install P4WSAD 2009.1, open the Software Updates from Eclipse or IBM Rational and create a new site bookmark with the following URL:
    http://www.perforce.com/downloads/http/p4-wsad/install/
  • A zip file for local installation can be found on our ftp site. Please see the Release Notes for installation instructions.
  • For further details and complete installation instructions, see the Release Notes.
  • P4WSAD 2009.2 is currently in beta. See the Beta Release Notes for details.
    To install the beta version select from the sites below based on your installed version of Eclipse:
    • Eclipse 3.5
      http://www.perforce.com/downloads/http/p4-wsad-beta/install/3.5
    • Eclipse 3.4
      http://www.perforce.com/downloads/http/p4-wsad-beta/install/3.4
    • Eclipse 3.3
      http://www.perforce.com/downloads/http/p4-wsad-beta/install/3.3
    • Eclipse 3.2
      http://www.perforce.com/downloads/http/p4-wsad-beta/install/3.2

Please contact Perforce Technical Support with any P4WSAD questions.

All trademarks used herein are either trademarks or registered trademarks of their respective owners.