ca software change manager · 6 plug-in for eclipse release notes chapter 3: documentation 19 where...

CA Software Change Manager

Plug-In for Eclipse Release Notes r12

This documentation and any related computer software help programs (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies.

The right to print copies of the documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end user’s applicable license agreement.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2008 CA. All rights reserved.

CA Product References This document references the following CA products:

■ CA Software Change Manager (CA SCM)

■ CA Harvest Change Manager (CA Harvest)

Contact CA Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.

Provide Feedback

If you have comments or questions about CA product documentation, you can send a message to [email protected].

If you would like to provide feedback about CA product documentation, please complete our short customer survey, which is also available on the CA Support website.

http://www.ca.com/support

mailto:[email protected]

http://tinyurl.com/6j6ugb

http://tinyurl.com/6j6ugb

Contents

Chapter 1: Welcome 7 What the Release Notes Covers................................................................. 7 International Support .......................................................................... 7 Published Fixes ................................................................................ 8

Chapter 2: New Features and Enhancements 9 Refactoring Support ........................................................................... 9 Check In New Items to a Branch............................................................... 10 Placement Options............................................................................ 10 Edit Without Checkout ........................................................................ 10 Background Add to WorkSpace ................................................................ 11 Commit to Repository (Sync + Commit)........................................................ 11 Update from Repository (Sync + Get).......................................................... 12 Explorer View ................................................................................ 12 Show Files in Explorer Tree.................................................................... 12 Quick Status Package Indicators ............................................................... 12 Package-Centric Visualization of the Explorer View.............................................. 13 Packages View ............................................................................... 13 Versions View ................................................................................ 13 Find Versions................................................................................. 13 View Snapshots that Contain a Selected Version ................................................ 14 Life Cycle Diagram............................................................................ 14 History Diagram .............................................................................. 14 Show Stored As Attribute Type ................................................................ 14 Save List As.................................................................................. 15 Find Forms ................................................................................... 15 Form Details Report .......................................................................... 15 New Form Editor.............................................................................. 15 Form Template Enhancements................................................................. 16 External Compare/Merge Tools ................................................................ 16 Help ......................................................................................... 16 Delete Package Process and Privilege .......................................................... 17 CA SCM Reports .............................................................................. 17 Miscellaneous Enhancements .................................................................. 17 Coexistence With r7.1 ........................................................................ 18

Contents 5

6 Plug-In for Eclipse Release Notes

Chapter 3: Documentation 19 Where to Find Documentation ................................................................. 19 Documentation PDF Names.................................................................... 19 How to View PDFs ............................................................................ 19

Chapter 4: System Information 21 Eclipse Requirements ......................................................................... 21 Windows 32-Bit Clients ....................................................................... 22 Java Runtime Requirement.................................................................... 22 Operating System Support .................................................................... 22 Microsoft Windows Operating Systems ......................................................... 23 Web Browsers ................................................................................ 23

Chapter 5: Installing the Plug-in for Eclipse 25 How to Upgrade From r7.1 .................................................................... 25 How to Perform a First-Time Installation ....................................................... 26 Install the CA SCM Plug-in for Eclipse .......................................................... 27 Coexist With r7.1 ............................................................................. 28

Chapter 6: General Considerations 31 Code Refactoring in Eclipse.................................................................... 31 Java Package Movement ...................................................................... 31

Chapter 7: Known Issues 33 Get Contents Remains Enabled ................................................................ 33 Refresh Status ............................................................................... 34 Check-In of Removed Item Fails ............................................................... 34 Resharing a Project Created from Root View Path ............................................... 34 Conflict Status Not Shown..................................................................... 35 Synchronization With File-Level Packages ...................................................... 35 User Guide and Online Help - Refresh Checked-Out Status ...................................... 35

Chapter 1: Welcome

Welcome to CA Software Change Manager (CA SCM) Plug-In for Eclipse. The Release Notes provide operating system support, system requirements, installation considerations, and related information for the plug-in r12 only.

Note: For similar information for CA SCM r12 components, see the CA Software Change Manager Release Notes.

This integration lets CA SCM integrate into development environments using Eclipse. Although you install and maintain the plug-in separately from the product components, you must install the core r12 client (Workbench or command line) prior to installing the plug-in to configure your base CA SCM environment.

Note: For CA SCM installation information, see the CA Software Change Manager Implementation Guide.

This section contains the following topics:

What the Release Notes Covers (see page 7) International Support (see page 7) Published Fixes (see page 8)

What the Release Notes Covers The Release Notes provides you with information that helps you install and use this release of CA SCM Plug-In for Eclipse.

Note: At publication time, the plug-in supports the operating systems, and the third-party software, including DBMS software, and web browsers, listed in the CA SCM Release Notes and the CA SCM Plug-in for Eclipse Release Notes. For the latest information, including any updates that may have occurred after publication, contact Technical Support at http://ca.com/support and request to view the CA SCM Compatibility Matrix.

International Support An internationalized product is an English product that runs correctly on local language versions of the required operating system and required third-party products, and supports local language data for input and output. Internationalized products also support the ability to specify local language conventions for date, time, currency and number formats.

Chapter 1: Welcome 7

http://ca.com/support

http://ca.com/support

Published Fixes


A translated product (sometimes referred to as a localized product) is an internationalized product that includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.

In addition to the English release of CA SCM, CA supports only those languages listed in the following table.

Language Internationalized Translated

Brazilian-Portuguese Yes No

Chinese (Simplified) Yes No

Chinese (Traditional) Yes No

French Yes No

German Yes No

Italian Yes No

Japanese Yes No

Korean Yes No

Spanish Yes No

Note: If you run CA SCM in a language environment not listed in the table, you may experience problems.

Published Fixes For all published fixes for CA SCM, see the Published Solutions provided by Technical Support at http://ca.com/support.



Chapter 2: New Features and Enhancements


Refactoring Support (see page 9) Check In New Items to a Branch (see page 10) Placement Options (see page 10) Edit Without Checkout (see page 10) Background Add to WorkSpace (see page 11) Commit to Repository (Sync + Commit) (see page 11) Update from Repository (Sync + Get) (see page 12) Explorer View (see page 12) Show Files in Explorer Tree (see page 12) Quick Status Package Indicators (see page 12) Package-Centric Visualization of the Explorer View (see page 13) Packages View (see page 13) Versions View (see page 13) Find Versions (see page 13) View Snapshots that Contain a Selected Version (see page 14) Life Cycle Diagram (see page 14) History Diagram (see page 14) Show Stored As Attribute Type (see page 14) Save List As (see page 15) Find Forms (see page 15) Form Details Report (see page 15) New Form Editor (see page 15) Form Template Enhancements (see page 16) External Compare/Merge Tools (see page 16) Help (see page 16) Delete Package Process and Privilege (see page 17) CA SCM Reports (see page 17) Miscellaneous Enhancements (see page 17) Coexistence With r7.1 (see page 18)

Refactoring Support New life cycle processes support refactoring processes. The processes are rename path, remove path, move path, and move item—for moving an item to a different path. In addition, both rename item and remove item processes are extended to support changes on the branch.

Chapter 2: New Features and Enhancements 9

Check In New Items to a Branch

Check In New Items to a Branch Parallel development allows developers to create an item or item path on a branch. This enhancement allows developers to use a check-in process with the New Items or New and Existing Items option to check in a new item or item path to a branch. After a new item or item path has been checked in to a branch, most applicable package-based operations will behave as they would for an initial 0-mapped version.

This enhancement is important because by allowing a branch option for new item check-ins, the work can be kept private in a package until it is ready to be merged to the trunk.

Placement Options The placement of items, during operations such as check-out and refactoring, can be specified to be on the trunk or branch. Users can configure the placement settings for these processes using the Administrator application. In addition, both options can be specified, which lets the user select which one to use at a particular time. The Plug-in for Eclipse now offers placements options on the Workspace Context dialog for a shared workspace project.

Edit Without Checkout A new “Allow editing without checkout” preference is now offered in CA SCM preferences. When selected, users may modify files in their Workspace without the need to check out at the time of modification. This is similar to the Offline mode of operation available in the plug-ins used with CA SCM r7.1, but alleviates the need to transition from to or from Offline Mode while working in Eclipse.


Background Add to WorkSpace

Background Add to WorkSpace When performing an Add to Workspace operation the Plug-in for Eclipse will open a progress dialog with a “Run in Background” button. Pressing this button dismisses the progress dialog and allows the Add to Workspace operation to continue its execution as a background process. You can view the progress of this operation by opening the Eclipse Progress view. While the operation is executing, you are free to perform other operations within Eclipse.

If you want to always execute this process in the background, select the “Always Run in Background” option in Eclipse General preferences. Note that this change will affect all Eclipse processes that offer a background execution option.

While Add to Workspace is executing in the background, you may be prompted with a dialog asking to confirm the overwrite of existing files. If you prefer to always allow the process to overwrite existing files, select the “Always overwrite files without asking” option on the Add to Workspace wizard’s Checkout Options page prior to clicking Finish in the wizard.

Commit to Repository (Sync + Commit) A Commit to Repository action has been added under the Team menu. This action combines the operations of Synchronize and Commit (formerly called Release) into a single workflow. This combined action is simply a usability enhancement which benefits you the most when you need to make a quick change and check it in to repository. The implementation behind the Synchronize and Commit remains the same as the separate action.

This action only commits nonconflicting changes to the repository and never commits any conflicting changes. If any conflicts are found, they are shown in the Synchronizer View. The user then follows the normal procedure for merging conflicts in the Synchronizer View.


Update from Repository (Sync + Get)

Update from Repository (Sync + Get) An Update from Repository action has been added. Update from Repository combines the operations of Synchronize and Get from Repository into a single workflow. The implementation behind the Synchronize and Get remains the same as the separate actions.

This action updates the local workspace with changes from the repository only if there are no conflicts. It never automatically overwrites any changes made in the local workspace. Any conflicts found are shown in the Synchronizer View. The user then follows the normal procedure for merging conflicts in the Synchronizer View.

Explorer View You can use the Explorer View (replaces the Harvest Repositories View in prior versions) to explore CA SCM brokers and perform CA SCM activities. All CA SCM processes are executable from the Explorer View based on the configuration and access permissions set up by your CA SCM administrator.

Show Files in Explorer Tree The new Plug-in for Eclipse contains a host of preferences which allow you to customize how you work and visualize data. For example, the Show Files in Tree option under Explorer preferences provides users the choice of whether files are shown in the Explorer View.

Quick Status Package Indicators Package status indicators are visual cues that give you useful information about packages and the objects they use. After you set preferences to show indicators, package status indicators will appear in the Plug-in for Eclipse Explorer View. Indicators appear on a package icon to denote the following conditions:

■ A package needs approval before it can be promoted.

■ A package contains reserved tag versions of files.

■ A package contains unmerged versions of files.


Package-Centric Visualization of the Explorer View

Package-Centric Visualization of the Explorer View At the top of Explorer View, you can select a package from the Package drop-down list. This package list applies to the current state context in your tree selection. If you select a package, the tree automatically rearranges itself to show versions belonging to the package at the latest version node level. While a package is selected, you can create a new path on the branch and it will appear immediately in the tree. The working view root node is also updated to reflect the default package. The Explorer View works in the traditional trunk-oriented way when you do not select a package.

Packages View A new Packages View lets you execute complex filtering operations to locate packages with common attributes. You can save your frequently used queries to the file system for reuse. Two default filters are provided with the view: All Packages and My Assigned Packages. Additional filtering criteria are provided under the Advanced Search.

Versions View A new Versions View lets you execute complex filtering operations to locate versions with common attributes. The search criteria are identical to the Find Version dialog, with the added convenience of saving your frequently used queries to the file system for reuse. The following default filters are provided with the view:

■ All Versions

■ My Reserved Versions

■ My Unmerged Versions

Find Versions The Find Version dialog lets you select item versions from the repository. The various options on this dialog work with one another to let you select versions according to multiple criteria. In addition, you can use the Find Version dialog simply to obtain version information.

New search criteria let you do the following:

■ Locate versions based upon a word/phrase in a file

■ Locate a file that it stored in the repository (binary or text)

■ Locate a version that was modified, based upon a range months.


View Snapshots that Contain a Selected Version

View Snapshots that Contain a Selected Version You are now able to select a version and view the snapshots that contain the selected version.

Life Cycle Diagram The life cycle diagram gives you a graphical view of the development life cycle defined for a specific CA SCM project. The diagram appears in the Plug-in for Eclipse. Project states are depicted as boxes in colors that depict the view types associated with the states. In addition, states are listed with the state name, view name, number of packages, modifier, and last modified date displayed in each box. Promote and demote processes are represented as connecting, directed colored lines. Icons in the state boxes represent approval processes. The visual display for a life cycle diagram can be customized in Preferences.

History Diagram A new history diagram gives you a graphical view of the history of a file or folder. Versions are depicted as boxes with the version name, package name, modifier, and last modified date displayed in each box. Trunk and branch versions show their relationships using connecting, directed lines.

You can open any number of diagrams. They display side-by-side with each diagram occupying its own tab in Eclipse. You can display files or folders in the diagram. For example, you can use the history diagram to view the versions of a directory that occurred as the result of a refactoring operation. From within the diagram, you can execute an action by right-clicking a diagram node. A menu related to the node appears and includes all actions available for the item.

Show Stored As Attribute Type To help you quickly determine how an item is stored in the repository, the attributed “Stored As” is now displayed in the Properties Sheet and in the List View. The value of this attribute will be either text or binary.


Save List As

Save List As You can save the Lists View or results view table contents to a file on the file system. You can save the selected data or the entire list of results in either ASCII text or Comma Separated Value (CSV) format, and specify to include column labels.

Find Forms The Find Form dialog lets you execute complex filtering operations to locate forms with common attributes. You can also use the Find Form dialog to select forms according to their association with packages, as well as specifying specific content values of the form type. New search criteria for forms let you do the following:

■ Locate a form that was created or modified by a specific user, based upon a specified date range, or range in number of days/months.

■ Locate a form based upon the type of attachment it contains (file, URL, any)

■ Locate a form based upon whether it contains attachments.

Note: When finding forms with attachments, the type (as noted above) is also used.

Form Details Report Form Details are generated in an HTML report and displayed in the default browser.

New Form Editor A new forms editor uses XML form templates that are now stored on the r12 server. There is no longer any need to distribute form templates to individual client computers. You can view or edit a form by using an Edit Form action. The form opens in an editor within the tabbed editor area of the Plug-in for Eclipse, alongside other text editors or diagrams. You can edit any number of forms side-by-side. The tabbed editor lets you easily view multiple forms or copy and paste text between forms. You can also modify, save, print form content, as well as attach file or URL attachments. The form merge tool lets you merge your changes with changes of another user for the same form.

Note: CA SCM Web Interface (Harweb) is no longer required in the plug-in. Actions previously available through the plug-in’s embedded Harweb are now native to the plug-in, for example, viewing and updating forms.


Form Template Enhancements

Form Template Enhancements New enhancements have been made to form templates to allow the following capabilities:

■ Required fields

■ Pattern-based field validation

■ Multiple column layout of fields

■ Image field—graphical images can now be displayed on the form

■ Hyperlink field

■ Rich text labels

■ JavaScript—the editor requires script-based customizations to be implemented in JavaScript. The formerly used Visual Basic script is not platform-independent and restricts operation on non-Windows platforms.

Note: The CA Software Change Manager Administrator Guide contains detailed information on customizing your form templates and using JavaScript.

External Compare/Merge Tools External compare/merge tools can now be configured in CA SCM preferences. This allows users to override the default compare tool used for comparisons invoked from Explorer View or History Diagram. It also allows users to override the default merge tool used for Interactive Merge invoked from Explorer View.

Help The new CA SCM Plug-in for Eclipse contains an HTML, task-based help system. The CA SCM Plug-in for Eclipse provides context-sensitive help when you click the “?” icon on a dialog. The help system is also available in PDF format (Plug-in for Eclipse User Guide).


Delete Package Process and Privilege

Delete Package Process and Privilege CA SCM administrators can control which user groups can delete packages through a new delete package process. The new process type named Delete Package is introduced in r12 to address the access control needs for deleting packages. This lets Administrators configure users who can edit a package from those who are allowed to delete a package. Users belonging to user groups who are allowed to execute a delete package process associated with a package state are allowed to delete forms associated with the package, and to delete the packages themselves.

Note: For information about the delete package process and privilege, see the CA Software Change Manager Administrator Guide.

CA SCM Reports The SCM plug-in r12 allows access to the BusinessObjects InfoView as a business intelligence (BI) portal to collect, consolidate, and present your organization’s CA SCM data. Reports include existing Dashboard, CA SCM reports, and new reports that cover security, audit, project change activity, package change activity, and source item change activity. The reports are useful for administrators, managers, quality assurance testers, and developers.

The plug-in offers a preference for configuring the URL to the Business Objects Infoview. Go to Windows, Preferences, Team, CA SCM, Business Objects to see the URL set for Business Objects.

Note: For information about CA SCM Reports, see the documentation on the CA SCM Reports installation media.

Miscellaneous Enhancements The Plug-in for Eclipse includes the following miscellaneous enhancements:

■ A Team, Locate in Explorer action is available for all shared file resources.

Invoking this action will activate the Explorer View and select the version (as a child of a package) associated with the shared file resource.

■ CA SCM Version properties page has been added for shared file resources.

The properties dialog for a shared file resource now contains a new SCM Version page that displays the properties of the CA SCM version associated with the version resource.


Coexistence With r7.1


■ Package State column has been added to resource Compare list views.

Invoking Compare, or Replace With Version in CA SCM actions from a shared resource now displays a list view that includes a new Package State column. This column represents the state in which the package which contains the version currently resides.

■ The CA SCM Team preference Show Package State Column for Versions in Lists View has been added. If this new preference is selected, the CA SCM Lists View will display an additional Package State column for versions. This column represents the state in which the package which contains the version currently resides.

Note: When this preference is selected, the performance refreshing the Lists View for versions will be slower because it will require additional server transactions. By default, this preference is unselected.

■ Package State and Package Name are now displayed in left/right compare panes within Incoming/Outgoing Mode View. When differences are displayed in the Incoming/Outgoing Mode view, the compare labels for the left/right panes now include package state and name. The label format is now of the form VersionName:VersionNumber (StateName:PackageName). The state name represents the state in which the package currently resides.

■ A new Show Package and State in Tree preference is now available within Incoming/Outgoing Mode View. This new preference is accessible from the Incoming/Outgoing Mode view’s toolbar. When Show Package and State in Tree is selected, incoming files are displayed with the package and state appended to the version name, in the form VersionName (StateName:PackageName). The state name represents the state in which the package currently resides. Changes to this preference are stored between Eclipse sessions.

Note: If this preference is selected, the performance building the synchronize tree will be slower because it will require additional server transactions. By default, this preference is unselected.

■ List Other Versions action has been added for shared resources. This action will open the Lists View to show all other versions related to the shared resource’s CA SCM item.

Coexistence With r7.1 You can install the r12 Eclipse Plug-in on a system that has an existing r7.1 installation and corresponding r7.1 Eclipse plug-ins.

More information:

Coexist With r7.1 (see page 28)

Chapter 3: Documentation


Where to Find Documentation (see page 19) Documentation PDF Names (see page 19) How to View PDFs (see page 19)

Where to Find Documentation You can access the documentation in the following locations:

■ The Docs directory on the CA SCM Plug-In for Eclipse installation media

■ Online help that is automatically installed with the CA SCM Plug-in for Eclipse

■ CA SCM Eclipse Plug-in Update Site at http://supportconnectw.ca.com/public/harvesteclipse/.

■ Technical Support at http://ca.com/support

Documentation PDF Names The file names for the CA SCM Plug-In for Eclipse PDF guides are as follows:

Guide Name File Name

CA SCM Plug-In for Eclipse User Guide CA_SCM_Plugin_Eclipse_ENU.pdf

Release Notes CA_SCM_Plugin_Eclipse_RelNotes_ENU.pdf

How to View PDFs To view PDF files, you must download and install Adobe Reader from the Adobe website if it is not already installed on your computer.

Chapter 3: Documentation 19



Chapter 4: System Information


Eclipse Requirements (see page 21) Windows 32-Bit Clients (see page 22) Java Runtime Requirement (see page 22) Operating System Support (see page 22) Microsoft Windows Operating Systems (see page 23) Web Browsers (see page 23)

Eclipse Requirements Install any of the following releases of Eclipse Foundation's Eclipse Development Platform on the supported platforms of your client computer:

■ Eclipse 3.4 (Ganymede)

– Eclipse IDE for Java EE Developers

– Eclipse Classic

– Eclipse IDE for Java Developers

Note: CA SCM Plug-in for Eclipse r12 has been tested with the Eclipse 3.4 Classic configuration only.

■ Eclipse 3.3 and 3.2.2

Note: Eclipse 3.2.0 and 3.2.1 are not supported.

■ IBM Rational Application Developer 7.0 (This application is built on Eclipse 3.2.2.)

There are various configurations of the supported Eclipse releases available on http://www.eclipse.org (Classic, Java EE, and so on). Download the appropriate Eclipse configuration depending upon the type of Eclipse projects or applications being developed.

The r12 Eclipse plug-in is not supported on the 64-bit version of the Eclipse IDE. You must download the win32-bit version of the IDE.

Your Eclipse installation must include the Eclipse Graphical Editing Framework (GEF) plug-in. If your Eclipse distribution does not include GEF, you will need to install GEF prior to installing the CA SCM Plug-in for Eclipse.

Note: For information about GEF, see http://www.eclipse.org/gef/ GEF downloads and installation instructions.

Chapter 4: System Information 21

Windows 32-Bit Clients

Important! Make sure to download the version of the Eclipse GEF plug-in that corresponds to the release of Eclipse that you are using.

If your target integrated development environment (IDE) is IBM Rational Application Developer 7.0, you do not need to install a separate version of Eclipse. Eclipse is installed as part of that IDE.

Windows 32-Bit Clients CA SCM Plug-in for Eclipse r12 has the following system requirements for Windows 32-bit clients:

■ 1 CPU—Pentium IV 1.3 GHz

■ 1 GB RAM

■ 250 MB free hard disk space

Java Runtime Requirement Eclipse does not come with a Java virtual machine (JVM), so one must be downloaded and installed separately prior to installing the plug-in. The following versions of the JRE are supported:

■ Java 5 JRE (Sun)

■ Java 6 JRE (Sun)

■ IBM JRE is already included with IBM Rational Application Developer 7.0

Operating System Support The following platforms are supported by the CA SCM Plug-in for Eclipse. CA supports these platforms for the duration of their life cycle, as determined by their manufacturer, or until CA announces that we are no longer supporting them.

Note: For the latest information about supported platforms, contact Technical Support at http://ca.com/support.




Microsoft Windows Operating Systems

Chapter 4: System Information 23

Microsoft Windows Operating Systems The CA SCM Plug-in for Eclipse supports the following Microsoft Windows operating systems:

Platform Release

x86 and x86-64 XP (x86 only)

2003

Vista

Note: This release of the CA SCM Plug-in for Eclipse is a 32-bit application. The r12 Plug-in for Eclipse does not run on the 64-bit version of the Eclipse IDE.

Web Browsers The following Web browsers are supported:

■ Microsoft Internet Explorer 6.0 and 7.0

■ Firefox 3.0

Chapter 5: Installing the Plug-in for Eclipse


How to Upgrade From r7.1 (see page 25) How to Perform a First-Time Installation (see page 26) Install the CA SCM Plug-in for Eclipse (see page 27) Coexist With r7.1 (see page 28)

How to Upgrade From r7.1 If you have an existing Eclipse plug-in on your computer, perform the following tasks before installing the r12 Plug-in for Eclipse:

1. Check in or commit your Eclipse project changes to the repository before your server is upgraded to r12.

You will need to recreate your projects using the Add to Workspace wizard after the r12 plug-in is installed. If you want to continue using your existing Eclipse workspace, then delete all Eclipse workspace projects that were previously shared with Harvest r7.1. Alternatively, you can start Eclipse with an entirely new workspace location.

2. Install the r12 CA SCM client (Workbench or command line) on each computer where the plug-in will be installed.

Note: For installation instructions, see the CA Software Change Manager Implementation Guide.

3. Ensure that you have a supported version of the Java Runtime (JRE) installed on the client.

4. Ensure that you have a supported version of Eclipse installed.

Note: If you want to upgrade to a newer version of Eclipse, you can download it from http://www.eclipse.org.

5. If the Eclipse Graphical Editing Framework (GEF) feature is not already installed in your Eclipse component, you need to install it. If you do not have it installed, you will receive an error message during the plug-in installation and not be allowed to continue.

Note: For installation instructions, see http://www.eclipse.org/gef/.

Chapter 5: Installing the Plug-in for Eclipse 25

How to Perform a First-Time Installation

6. Consider whether you will run r7.1 and CA SCM r12 on the same client computer. If you plan to run both the r7.1 and r12 client/plug-ins on the same computer, review and perform the coexistence steps (see page 28) prior to installing the r12 plug-in. For this configuration, you need separate installations of Eclipse for r7.1 and r12 plug-ins, respectively.

7. If you have the r7.1 plug-in installed in an existing Eclipse installation and do not plan to run both r7.1 and r12, you should uninstall the r7.1 plug-in from your Eclipse installation, using the Eclipse Configuration Manager as follows:

a. Select Help, Software Update, Manage Configuration.

b. Expand tree and select prior AllFusion Harvest Feature.

c. Click Uninstall.

d. Click Yes when asked to Restart Eclipse.

8. Proceed to install the CA SCM Plug-in for Eclipse.

More information:

Eclipse Requirements (see page 21)

How to Perform a First-Time Installation If you are installing the Eclipse plug-in for the first time, perform the following pre-installation tasks:

1. Install the CA SCM client (Workbench or command line) on each computer where the plug-in will be installed.

Note: For installation instructions, see the CA Software Change Manager Implementation Guide.

2. Install the Java Runtime (JRE) on your computer.

3. Install Eclipse in a location that will be used specifically for your r12 plug-in. It should not be used with any prior release plug-in.

Note: The Eclipse version must be downloaded from http://www.eclipse.org and installed on the target systems prior to installing the plug-in.

4. If the Eclipse Graphical Editing Framework (GEF) feature is not already installed in your Eclipse component, you need to install it. If you do not have it installed, you will receive an error message during the plug-in installation and not be allowed to continue.

Note: For installation instructions, see http://www.eclipse.org/gef/.


Install the CA SCM Plug-in for Eclipse

5. Consider whether you will run r7.1 and CA SCM r12 on the same client computer. If you plan to run both the r7.1 and r12 client and plug-in on the same computer, review and perform the coexistence steps (see page 28) prior to installing the r12 plug-in. For this configuration, you will need separate installations of Eclipse for r7.1 and r12 plug-ins, respectively.

6. Proceed to install the CA SCM Plug-in for Eclipse.

More information:

Eclipse Requirements (see page 21)

Install the CA SCM Plug-in for Eclipse The CA SCM Plug-in for Eclipse is installed using the Eclipse Update Manager, a feature provided by Eclipse. The Eclipse Update Manager is a built-in plug-in installation and update manager that simplifies the installation process and lets you manage various plug-in instances.

Note: For details on managing your configuration, see the Eclipse help.

To install the CA SCM Plug-in for Eclipse using Eclipse 3.2.2 or 3.3

1. In Eclipse, select Help, Software Updates, Find and Install.

The installation wizard appears.

2. Select Search for new features to install, and click Next.

3. Click New Remote Site.

The New Remote Site dialog appears.

4. In the Name field, enter SupportConnect.

5. In the URL field, enter the following URL:

http://supportconnectw.ca.com/public/harvesteclipse/.

This default URL points to the CA update site for the CA SCM Plug-in for Eclipse.

6. Click OK.

The new SupportConnect site is added to the update sites list.

7. Select the check box next to the remote site created, and click Next or Finish.

The Search Results dialog appears.

8. Expand the site and expand the Eclipse category node.


Coexist With r7.1

9. Select the check box next to the 12.0 plug-in version, and click Next to continue through the wizard to install the plug-in.

10. When prompted to restart Eclipse, click Yes.

The CA SCM Plug-in for Eclipse is installed.

To install the CA SCM Plug-in using Eclipse 3.4

1. In Eclipse, select Help, Software Updates.

The installation wizard appears.

2. Select the Available Software tab.

3. Click Add Site.

The Add Site dialog appears.

4. In the Location field, enter the following URL:

http://supportconnectw.ca.com/public/harvesteclipse/

This default URL points to the CA update site for the CA SCM Plug-in for Eclipse.

5. Click OK.

The new SupportConnect site is added to the list of available software sites, and is automatically scanned for possible updates.

6. Select the check box next to the 12.0 plug-in version, and click Install to install the plug-in.

7. When prompted to confirm the installation, click Finish.

8. When prompted to restart Eclipse, click Yes.

The CA SCM Plug-in for Eclipse is installed.

Coexist With r7.1 You can install the r12 Plug-in for Eclipse on a computer that has an existing CA SCM r7.1 installation and existing plug-ins, for example, 7.20.x and 6.20.x. The following considerations apply to the coexistence:

■ Eclipse Installation—If you want to use both r7.1 and r12 Eclipse plug-ins, the recommended approach is to install two separate instances of the Eclipse application, one using the r7.1 Plug-in and the other using the r12 plug-in.

■ Eclipse Launch—When launching Eclipse, the PATH environment variable must include the appropriate Harvest/SCM home path prior to any other Harvest/SCM paths. To alter the path prior to launching Eclipse, alter the PATH variable in a command prompt and launch Eclipse from that same command prompt.


Coexist With r7.1


To launch Eclipse for either r12 or r7.1

1. Open a Windows command prompt.

2. Execute the following to setup the PATH environment variable for your CA SCM/Harvest version you want.

■ For r12, execute the command:

set PATH=%CA_SCM_HOME%;%PATH%

■ For r7.1, execute the command: set PATH=%HARVESTHOME%;%PATH%

3. Change directory to your Eclipse home folder and launch the Eclipse application (from the command shell), for example:

cd c:\eclipse eclipse.exe

Chapter 6: General Considerations 31

Chapter 6: General Considerations


Code Refactoring in Eclipse (see page 31) Java Package Movement (see page 31)

Code Refactoring in Eclipse When performing code refactoring in Eclipse, we recommend that you select the “Allow editing without checkout” option in the CA SCM preferences.

If this preference is not selected, some refactoring operations (such as Java package renaming and deletion) will not be fully supported.

Java Package Movement When a Java package is moved from one Eclipse source path to another using Package Explorer, Eclipse does not actually move the folder. It instead deletes and creates the package's folder structure. Thus, the Synchronizer View reflects this as an Outgoing Deletion rather than a changed status.

If you perform the move in the Navigator View, the folder history will be maintained; however, this is not Java Refactoring and Eclipse will not update the references to moved classes.

Chapter 7: Known Issues

This section lists the most prominent known issues for CA Software Change Manager r12 at publication time. For other known issues, contact Technical Support at http://ca.com/support.


Get Contents Remains Enabled (see page 33) Refresh Status (see page 34) Check-In of Removed Item Fails (see page 34) Resharing a Project Created from Root View Path (see page 34) Conflict Status Not Shown (see page 35) Synchronization With File-Level Packages (see page 35) User Guide and Online Help - Refresh Checked-Out Status (see page 35)

Get Contents Remains Enabled The Get Contents function remains enabled for the latest revision time in the History view after you perform Compare with, Local History or Team, Show Local History. While performing Get Contents for the latest revision as follows, the item content becomes empty.

1. In the Navigator view, edit an item.

2. Right-click the modified item and perform Compare with, Local History or Team, Show Local History or Replace with, Local History.

3. From the History view, select the latest revision, and perform Get contents.

4. Click Yes when you are prompted for "Do you wish to overwrite the current revision with selected revision?".

5. Open the latest revision to see the content.

The content is empty.

The content should not be empty.

Chapter 7: Known Issues 33


Refresh Status

Refresh Status Symptom:

If a reserved-tag of an item in the repository is deleted as a result of the deletion of the refactored parent item path, the plug-in will not refresh the status of its corresponding file in the workspace.

Solution:

There is no direct workaround available for this issue. Do the following to refresh status:

1. Commit any other changes in the workspace.

2. Delete the project from the workspace.

3. Add the same project back to the workspace.

Check-In of Removed Item Fails Symptom:

I cannot check in a new file to a branch if the item with same name exists on the trunk and a removed (D-tagged) branch version exists in the package I use for the check-in.

Solution:

Check in the new file using the CA SCM Workbench.

Resharing a Project Created from Root View Path If a project is created from the root level view path initially and then unshared, the project cannot be shared to the root level view path again.


Conflict Status Not Shown

Chapter 7: Known Issues 35

Conflict Status Not Shown Symptom:

If you delete an item from the Navigator view and then modify, move, or rename the associated item in the repository, a later Synchronize may show an Outgoing Deletion for the item rather than a Conflict.

Solution:

If the deletion is no longer wanted, use the Team, Restore from Local History action to retrieve the version you want.

Synchronization With File-Level Packages Symptom:

When you invoke the Team, Synchronize action at a project or folder resource level, incoming versions are shown with respect to the Project-level package. If you have specified different file-level packages for individual files, branch versions in those packages will not appear as incoming changes.

Solution:

As a workaround, invoke Team, Synchronize at the file resource level for single or multiply-selected file resources. When invoked in this manner, the Synchronizer view will recognize file-level package settings and show branch versions in these packages as incoming changes.

User Guide and Online Help - Refresh Checked-Out Status The following updates are for the Plug-in for Eclipse documentation (User Guide and Online Help):

■ Disregard the Refresh Status topic, and use the procedure documented in the Refresh Checked-Out Status topic to update the workspace with the R-tag status from the repository.

■ For the Edit Resources Offline topic, replace the following sentences:

In the Navigator View, you can refresh status of file-, folder-, and project-level objects. Select the object, right-click, and select Team, Refresh status from the shortcut menu.

with:

In the Navigator View, you can refresh status of file-, folder-, and project-level objects. Select the object, right-click, and select Team, Refresh checked-out status from the shortcut menu.

ca software change manager · 6 plug-in for eclipse release notes chapter 3: documentation 19 where...

Documents