Patterns and reusable assets - release notes

1.0 Limitations
   1.1 Restart Eclipse after using update manager if RAS was used to import assets containing deployable plugins
   1.2 You can no longer drage pattern parameters from the Pattern Explorer view
2.0 Known problems
   2.1 RAS import might not bring up the Add to Source ClearCase dialog box
   2.2 Restart after you install a RAS asset that contains individual deployable plug-ins

1.0 Limitations

1.1 Restart Eclipse after using update manager if RAS was used to import assets containing deployable plugins

After you import a RAS asset that contains a deployable plug-in, RAS starts the plug-in by using the Eclipse Bundle API directly. The Eclipse Update Manager is not aware of bundles started directly, so it inadvertently uninstalls bundles not under its control. To work around this problem, restart Eclipse if you use the update manager after you import assets that contain deployable plug-ins.
Note: This issue only affects assets that contain "orphaned" deployable plug-ins that are not started from features.

1.2 You can no longer drage pattern parameters from the Pattern Explorer view

Dragging a parameter definition of a pattern template from the Pattern Explorer view to a diagram results in the creation of an instance of the pattern. Subsequent drag operations of the parameter(s) from the Pattern Explorer view create additional instances of the pattern. As a result of this problem, you can now only drag pattern templates from the Pattern Explorer view.

2.0 Known problems

2.1 RAS import might not bring up the Add to Source ClearCase dialog box

If the RAS import does not bring up the Add to Source ClearCase dialog box when you add files, folders, or projects to the workspace under ClearCase source control, you can work around the problem by turning off "on-demand status fetching" in the SCM Adapter's preference page or use the ClearCase menu to "find resources to add to source control" to manually add resources.

2.2 Restart after you install a RAS asset that contains individual deployable plug-ins

After you import a RAS asset that contains a deployable plug-in, the plug-in is started by the RAS tooling using the Eclipse Bundle API. The Eclipse Update Manager is not aware of bundles started in this manner. As a result, it might inadvertently uninstall bundles installed in this manner.
To work around this problem, restart the product before you use the Eclipse Update Manager after you import assets that contain deployable plug-ins.
Note: This only affects assets that contain "orphaned" deployable plug-ins; that is, individual deployable plug-ins that were directly included in the asset and not included in the asset as a result of including a deployable feature that depends on them.

Return to the main readme file