Borland^® Together^® 12.0 Release Notes

Last updated: October 1, 2012

This file contains important information that may not appear in the online Help. Please read this file in its entirety.

What's New and Fixed in This Release

System Requirements/Prerequisites

Installation Instructions

Licensing

Known Issues and Limitations

Together Capabilities

Finding Out More

Getting assistance

What's New and Fixed in This Release

This release of Together includes improvements in functionality and fixed bugs since Together 2008 Release 4. The important changes introduced in this release are highlighted below.

Documentation Generation

• Fixed (6362): Generate Documentation: Incorrect generation of *.RTF files.

Source Code Projects

• Fixed (6088): QA Metrics LCOM2 and LCOM3: optionally consider methods indirectly accessing fields via accessors.
• Fixed (6319): Java metrics: CR and TCR metrics for methods calculated incorrectly.

Integrations

• Fixed (6282): SVN: "Compare With | Branch/tag" or "Base revision" fails if preference "Modeling | EMF Model Compare | Model File Compare ... Compare logical structure of model files" is on.

General

• Eclipse platform updated to version 3.8.1 Juno SR1

Back to top

Integrations

Since version Together 2007 integrations with version control systems (StarTeam®) and requirement management products (CaliberRM™, RequisitePro) are not part of Together product. These integrations should be available separately from Borland. The Together 12.0 help still includes information about these integrations. However, newer versions of integrations may have some changes in functionality, so it is recommended that you check the release notes that are provided with each integration package.

Back to top

System Requirements/Prerequisites

Following are the system requirements for installing and running Borland Together 12.0:

Back to top

Installation Instructions

Together 12.0 can be installed to an existing instance of Eclipse SDK version 3.8.1 from the online or archived update site. Therefore Eclipse SDK as well as Java Virtual Machine needed to run it should be already installed prior to installing Together. If you have both installed please omit the following two subsections and jump right to the subsection Installing Together.

Installing Java Virtual Machine

If you already have an instance of Eclipse 3.8.1 installed you must have the JVM needed to run it installed as well. You may want to verify that the recommended version of JVM is used by Eclipse at the configurations details: once Eclipse is running invoke Help -> About from the main menu, then press Installation Details button, switch to Configuration page and look for java.home, java.version lines.

Together shares the requirements of Eclipse; namely it needs Java 5 update 22, or Java 6 update 27. Note that later updates of Java 6 contain the important fixes, so the latest available Java 6 update is recommended.

If the appropriate JVM version is not installed, please download the latest one from the Java downloads area at the Oracle web site. If you need Java 5, you may download JRE 5 update 22 from the Archive area. Installing JVM is pretty straightforward, however if you need help please refer Installation Instructions at the Oracle web site.

Installing Eclipse SDK

If there is no any instance of Eclipse 3.8.1 on your system, please visit Eclipse Project 3.x Stream downloads page at the Eclipse web site and download Eclipse classic 3.8.1 package. The installation is as simple as unpacking the archive to the folder of your choice.

If you would like to add Together to an existing Eclipse installation, note that Together needs Eclipse SDK. Thus please make sure your Eclipse contains the Eclipse SDK feature.

• Choose About ... items at the Help menu (Note: depending on the current configuration the ending of the item may be different). About dialog will appear.
• Click Installation details button.
• At the Installed software tab there is list of installed features.
• Make sure the Eclipse SDK is listed there.

If it is not the case perform the following steps prior installing Together:

• Invoke Help -> Install New Software ...
• It is recommended to uncheck option Contact all update sites during install to find required software in order to speed up the installation process.
• In the Work with combo box choose The Eclipse Project Updates - http:// ... item.
  Note: is this the main Eclipse update site. You may know other reliable sources containing the same software. So you may use the one you prefer, provided it contains the appropriate version of Eclipse SDK.
• Once the list of available software displayed check the Eclipse SDK item in the list.
• Click Next to continue installation.
• Follow the prompts of Eclipse update manager to complete the installation. Particularly you will need to review and confirm your choice, read and accept the software license agreement and restart Eclipse.

If it appears you have several JVMs installed, note that it is possible to enforce Eclipse to use a particular Java Machine. It is necessary to add -vm <path to JVM> parameter in eclipse.ini files, for example:
Original file:

-startup
...
--launcher.defaultAction
openFile
-vmargs
...

-startup
...
--launcher.defaultAction
openFile
-vm
C:\Program Files\Java\jre1.5.0_22\bin
-vmargs
...

Without these parameters Eclipse will first try to look for a Java machine in the ./jre subfolder of its home folder. If there is not one it will use the JVM installed in your system. In the later case, to check what version of JVM going to be used you may run the console at the Eclipse home folder and execute the command:

java -version

Installing Together

For installing Together in an existing Eclipse instance, use Borland Together 12.0 archived update site or Borland Eclipse 3.8 online update site.

• Run the target Eclipse, invoke Help > Install New Software....
• It is recommended to uncheck option Contact all update sites during install to find required software in order to speed up the installation process. Both online and archived update sites contain all the needed components.
• Use Add... button to add new update site. Type URL of online Borland Update Site http://altd.borland.com/update/eclipse3.8/together or press Archive... button to locate Together 12.0 archived site (together2008r4_size.zip), which is available for download. Assign some friendly name to this site at the Name field.
• Once site added look for Together 12.0 category.
• You may choose to install the whole set of features by checking the root node Together 12.0.
• Alternatively you may select only features you want to install. Keep the root node unchecked, expand it and check the features you need. Please pay attention to required/optional markers. The feature Together Classic Modeling is required and must be always installed.
• Once selection is made click Next to continue installation.
• Follow the prompts of Eclipse update manager to complete the installation. Particularly you will need to review and confirm your choices and read and accept the software license agreement.
  Note: Please ignore the warnings regarding the unsigned content referencing features with com.borland.* IDs and some other which may appear when Update Manager validates the features to be installed.
  Note: With some older Java machines you may also get the prompt about trust code signing certificate Microfocus;IT;Microfocus issued by Thawte, Inc. Please make sure you select the suggested certificate in the list and agree to continue installation.
• At the end you will be prompted to restart Eclipse. Note that Together installs additional launchers and Together executable. When working with Together it is recommended you use the Together executable instead of the Eclipse one. That will provide the proper defaults for the User Interface like perspectives, views, branding, etc.

Adjusting parameters in Together.ini and command line launchers

If you have several JVMs installed and need Together to use a particular one, you may want to edit Together.ini file. Please refer to the instructions and the example provided above in the section Installing Eclipse SDK for the eclipse.ini file. Perform similar operations for Together.ini in order to add -vm <path to JVM> parameter Without this parameter Together looks for a Java Virtual Machine first in a ./jre directory in the root of Eclipse and then on the search path.

Together command line launchers look for a java virtual machine first in a ./jre directory in the root of Eclipse, and then use the JAVA_HOME environment variable. You can adjust the JAVA_HOME environment variable in your system settings or edit command line launcher files specifying the path to the location where the required JVM is installed. For example at gendoc.cmd:
REM Unless you have a JRE installed in the Eclipse home, please define JAVA_HOME ...
set JAVA_HOME=C:\Program Files\Java\jre1.5.0_22

Note: Please refer the System Requirements section for the information about the required JVM version.

Together.ini and command line launchers are preconfigured to work with Eclipse version 3.8.1 and so refer to Equinox launcher (org.eclipse.equinox.launcher) and launcher library of explicit versions 1.3.0.v20120522 and 1.1.200.v20120522 respectively. Other versions of Eclipse may have a different version of this plugin. If you choose to install Together in an Eclipse version other than 3.8.1 you may need to replace all occurrences of the Equinox plugin version in the Together.ini and command line launchers with the actual version.

Back to top

Licensing

Once you have a serial number for your order please visit the following page to obtain license keys for Together: http://supportline.microfocus.com/licensing/borlandactivatelic.aspx.
Depending on the type of license you ordered you will be prompted for additional information to get your license keys.

Existing customers with active support contracts please contact Support Line to request your new license keys. License keys from previous versions are not suitable for Together 12.0.

If you requested a trial license key and got your activation file by e-mail please save that file on your hard drive. Then register from the running product using Help -> Borland Licensing -> Register Borland Together, choose Have Activation File path, complete the registration by following the prompts.

More details about Together licensing are available at the RegisteringTogether.html document located in the ./docs folder of the product installation.
Note: Please don't confuse the serial number from the order (a 10 to 12 digit string) and the serial number which is part of the serial/key pair.
The latter is a string of 4 dash-separated character groups like XXXX-XXXXXX-XXXXXX-XXXX supplied with a key like XXX-XXX.

For the license keys that need registration from the product UI using Help -> Borland Licensing -> Register Borland Together please make sure to switch to the Modeling Perspective using Window -> Open Perspective... -> Modeling. If Modeling is not shown in the list you may need to choose Other... and check Show all. Without the Modeling perspective active the needed menu items may be not available.

Back to top

Known Issues and Limitations

New issues may be identified and/or resolved after release. Please check the latest version of the Together Release Notes at Together Technical Publications page for changes to the known issues below.

Modeling and Diagrams

• (2352): When the Hide/Show dialog is used to hide attributes in a class diagram, the performance is slow. Use the context menu's Hide command instead of the Hide/Show dialog to avoid this issue.
• (2386, trk#29818): Metrics: The LOC metric does not count the number of lines with package statements and import statements.
• (2387, trk#31782): Sequence/Collaboration14: Cannot hide the message name for messages with operations regardless of the details level.
• (3171): There is no method to add frequently used properties to the context menu of model elements.
• (4891): Line delimiters created in tx* files don't depend on the Eclipse New text file line delimiter option, UNIX style delimiters (\\n) are used always. You can avoid the separators issue by handling ClearCase design files as binary files.
• If the Antialiased Text and Antialiased Graphics options are selected in the Preferences > Modeling> Diagram page, the elements name labels may appear corrupted in the Overview window.
• On some systems, the unexpected program termination may occur when antialiasing features for text and graphics are turned on. Make sure you use the latest drivers for your hardware, or try to turn antialiasing off.
• EMF API provides only read access to source code elements in modeling projects.
• BPMN diagrams (graphical part - positions, colors) are not available through the API.
• EMF API does not provide the possibility to get parameters and return the result for Operations in UML 1.4 Java modeling projects.
• EMF API does not provide the possibility to get the typed elements type in UML 1.4 Java modeling projects.

• You can view but should not edit design diagram files as text files. (These files are automatically created/updated by Together and visible in the UML Explorer when the filter is off.) If edited and saved in this manner, the diagram can be lost.

• BPMN simulation in step-by-step mode goes one step further than required. The problem is caused by using the standard DESMO-J library and should be fixed by a future release of Together. Note that the simulation report is calculated correctly.
• (346): Navigation to source code with the Open context menu action does not work if the diagram editor is maximized.

• (4688): Data Modeling, Microsoft SQL Server 2005: Secondary XML indices are not supported. The DDL parser can navigate through the construct [ USING XML INDEX xml_index_name [ FOR { VALUE | PATH | PROPERTY } ] ], but there is no support in an ERDB model.
• (4451): Data modeling: The Together ER physical metamodel is a general domain model and supports only "common" DDL objects (tables, views, table columns, indexes, constraints, etc.). It is not designed to support server-specific DDL objects such as Oracle's SEQUENCE. You can design a UML 2.0 profile and support objects specific to Oracle and associations between UML 2.0 and Data Modeling projects by using hyperlinks.
• Patterns with some metaclasses (for example, the TemplateSignature metaclass) cannot be applied.
• (5794): If a diagram in project A is changed and there is a dependency from project B, the "ghost" read-only occurrence of this diagram in the project B will not reflect the changes until F5 is pressed to refresh its diagram editor view.

Together OCL and QVT

• Though you can use the allInstances() OCL operation in Constraints, code generated for this operation is incorrect. Java runtime does not support the generated code and currently there is no standard way to get a collection of all instances of a given class.

• Together does not support code generation for isSent/message (^,^^) operators. The corresponding error message is displayed in the "Code Generation Log" view.

• OCL parser allows only infix form for mod and div standard operations. You can write 'a div b', 'c mod d', but not 'a.div(b)', 'c.mod(d)'.

• Together does not support OCL constraints and code generation for UML templates.

• You cannot generate Java code for QVT transformations that use profile metamodels because these metamodels do not have Java implementations. QVT transformations that use profile metamodels can be run in the 'Interpreted' mode.
• There are two different implementations of the OCL and QVT engines. The first version available since Together 2006 refers to the OMG ptc/05-11-01 QVT Specification. Historically it is the primary engine to use with Together models. The other engine Operational QVT deployed in Together 2008 refers to the substantially revised OMG formal/08-04-03 QVT Specification and originally best suited for the DSL Toolkit. Since Together 2008 R2 SP1, Operational QVT is adopted for use with Together models for both read and write. Normally there should be no problems using these engines simultaneously, although the UI may look a bit overloaded. It is recommended that you turn corresponding capabilities on or off as needed (select Window -> Preferences, and then select the General node and the Capabilities node). Note that source artifacts may need adjustment when migrating between these engines because these engines have differences in syntax and behavior. Please refer section Reference / QVT Migration Notes in the help book Borland Together DSL Toolkit Guide for migration guidelines.

C++/IDL Modeling Projects

• Moving C++ classifiers into/from other classifiers is restricted.
• Template specializations are invalidated when changing the name of a specialized template.
• Conditional expressions in #if directive are not supported.
• Links as comments are limited to dependency links based on the commented simple field declarations of a pointer or object types.
• In the generated code, links are represented as pointer type references.
• Parser blueprints for custom links recognition are not supported.
• There is a side effect related to the correction of unsigned modifier processing. When it appears in a method's formal parameter type, the method signature differs now from the one calculated in the English version. It may invalidate references (such as hyperlinks) to affected methods from the design part of the project created with the English-only version of Together 2006 R2 (build #4021.2).
• C++ modeling projects do not function properly if the product is installed in a path containing Japanese characters. Together must be installed in a path that does not contain these characters.
• Navigation to source code form the elements of automatically generated Sequence diagram might be slow depending on the size of involved compilation unit.

Documentation Generation and Printing

• (4303): Icons on diagram elements that are exported to .emf format have black background rather than transparent backgrounds. This affects generated RTF documentation where the .emf format is used for images by default. Consider switching to .GIF format for images in Preferences when generating RTF documentation.
• (4328): GenDoc: Convert &#xxxx; characters into readable characters when generating non-html output. Non-Latin characters are now okay in generation documentation. However, there are still issues with &* HTML entries in generated documentation.

Import Together Project Wizard

• Together cannot process external roots containing project-relative paths.

Referenced Projects

• When you create a Java Modeling project from Java projects that contain cross-project references, restart Together to make clipboard operations (Copy, Cut, and Paste) work correctly with the imported project roots.

• Modeling projects cannot reference non-modeling projects: you cannot add a reference to a non-modeling project to the Model Path project property. The existing Java modeling projects that reference Java projects might work incorrectly.

• You can create C++ projects referencing each other, but source code elements from referenced projects are not available in the model. You can import design elements only.

XMI Import/Export

• Rational Rose cannot import swimlanes from XMI. When activity diagrams with swimlane elements are exported from Together using XMI, the elements do not appear in swimlanes in Rational Rose.

• If you use the XMI feature to import UML 1.4 (OMG) or UML 2.0, no design diagrams will be transferred. All the imported elements will be imported and visible in the Model Navigator. You can then include the imported elements into diagrams.

• While performing XMI import to UML 1.4 or Java modeling projects, 'Replace for packages' does not work correctly. If you want the existing packages to be replaced on import, you should either delete them before the import process, or rename them and then you can delete old packages and change the names of the newly created packages after the import.

DSL Development

• (2694): Domain Editor: Undo operation after refactoring of model element in the Domain editor is available if you switch selection to the DSL Explorer. However, this will only roll-back external references updates, so you should manually rename the element in the editor after the Undo operation. You can also use the rename refactor action in the Project Explorer instead, where the action can be undone.

• (2702): Model Refactoring: Model Refactor does not support a domain’s URI mapping. So if you have ‘platform:’ URI mapping in your Domain model, move or rename operations can cause unpredictable results. It is best to clear such mappings before a move or rename operation and then restore the mappings after the operation.

• (2935): Domain Editor: To avoid validation warnings during domain model resource refactoring, you should close the Domain Editor (Eclipse bug 205426). To avoid validation warnings on model element refactoring, you should close the affected Diagram Editor.

• (2938): Allow main refactoring even if potential references were found in read-only resources. If Model Refactoring finds potential matches in read-only resources, you are prompted to make these resources writeable to apply the entire change. If a potential change of this type is not selected in the preview, the read-only file will not be modified.

Workflow

• Migration of Xtend queries that contain typeSelect operator leads to expressions that cannot be parsed correctly by the OCL edit control. It is recommended to copy these expressions to a standalone .qvto library and reference this library operation from the workflow query.

Miscellaneous

• (273): WS-BPEL 2.0 support delayed until BPMN 2.0 spec is released and evaluated.
• (3207): During a UML1.4 to UML 2.0 conversion, unidirectional hyperlinks that may be a result of manual editing of the model files are lost.
  
• (3221): During a UML1.4 to UML 2.0 conversion, activity nodes used in several activity graphs are placed in the ReusedElements Activity.
• (4209): Rich Text Editor: Keyboard shortcuts do not work on Mac OS X.
• (4358): Exporting a Together UML2.0 project with an EJB Standard profile applied to the Java project requires the J2EE libraries (ejb20.jar, jms.jar, etc.), which are not part of the Together installation. Import the required libraries to avoid problems during code generation.
• StarTeam integration: After checking in newly added modeling resources/elements when there are no difference between local and repository versions, team statuses are shown incorrectly (Conflicting change instead of Current). To avoid this problem, use Forced checkout to bring status to Current.
• Together fails to start and displays message box "JVM terminated. Exit code -1 ..." with all the JVM parameters. This can happen when system memory on a particular machine is loaded with other running software so that JVM cannot reserve enough memory required by the specified parameters. Reduce the values specified for the -Xmx and/or -XX:MaxPermSize parameters in the Together.ini file until the JVM can start normally. The first parameter affects the amount of data JVM can handle at runtime, and the second parameter affects the amount of classes JVM can load.
• When installing from update site Update Manager gives warnings about unsigned content referencing features with com.borland.* IDs. Please ignore these warnings.
• PDF version of Together Modeling Guide is not actualized comparing to the online help. Updated version is to appear on the Technical Publications and SupportLine web pages.

Back to top

Together Capabilities

The default capabilities are different for classic Together Modeling and the DSL Toolkit. Select Window -> Preferences, then select the General node and the Capabilities node. You can click the Advanced button to enable/disable capabilities at a more granular level.

The following table lists the Together capabilities that are enabled and disabled for classic Together Modeling and the DSL Toolkit:

Back to top

Online Help

Together provides online help through your Eclipse help browser. Select Help Contents on the Help menu. When the help browser opens, click Borland^® Together^® Modeling Guide, Borland^® Together^® DSL Toolkit Guide, Borland^® Together^® UML 2.1 Guide, or another online help section.

Online technical publications

The latest versions of Release Notes and product documentation are published at Together Technical Publications page

Back to top

Getting Assistance

Visit Micro Focus SupportLine at http://supportline.microfocus.com, http://support.borland.com/

Visit Borland at http://www.borland.com/

Back to top