Last
updated: April 5, 2014
This
is a release version of the SDK for use by participants in the SDK forum. Scripts
created with it can be run against StarTeam 2009, 2009R2, 12.0, 12.5, 13.0 and
14.0 Servers.
The
source code in the test suite is distributed as-is, with the intent of
providing coding examples and an opportunity to explore some of the newer SDK features.
The test suite includes no third party software. There is an implicit reliance
on junit (an open source library) & MPX (TIBCO
smart sockets which is distributed with the SDK itself).
The
following links are to the files provided with this field release along with a
brief description of each:
|
PowerPoint
presentation of the namespace changes and new features in the StarTeam 14.0
SDK |
|
|
A document describing
the rationale for the refactoring to the com.starteam namespace |
|
|
32 bit Java runtime
installer for SDK on Windows platforms. |
|
|
Native 64 bit Java
runtime installer for SDK on 64 bit Windows platforms. |
|
|
32 bit .NET runtime
.exe self-installer for SDK on Windows platforms. (automatic GAC
registration) |
|
|
32 bit .NET runtime
.zip (xcopy deployment) for SDK on Windows
platforms. (.NET assemblies and 32 bit native .dll’s) |
|
|
64 bit .NET runtime
.zip (xcopy deployment) for SDK on Windows
platforms. (.NET assemblies and 64 bit native .dll’s) |
|
|
Java runtime .tar.gz
for SDK on Unix/Linux/Solaris (non-Windows) platforms. |
|
|
Source code examples. |
|
|
Java mapping from the
old com.starbase.starteam namespace APIs to the new
com.starteam namespace APIs. Customers with scripts
written to the old namespace are strongly encouraged to port their scripts to
the new namespace. The old namespace has been deprecated since StarTeam 12.0.
There is no bridge for C#.NET. |
|
|
STCMD has been
rewritten. The document explains the new syntax. You can also use com.starteam.CommandProcessor directly (through Ant or
Hudson scripts, or a windows command prompt, using java –jar, for example). A
command line user interface (CUI) creates the command prompt shell and passes
your command to the SDK .jar. |
|
|
This is CUI
documentation about connecting. |
|
|
.zip file containing the entire javadoc
as a set of linked HTML files. |
|
|
.chm file containing
the entire documentation for the C#.NET assembly |
|
|
SDK JavaDoc HTML Help Documentation Online |
|
|
An HTML file describing
class by class signature changes from the 11.0 to 12.0 SDK |
|
|
An HTML file
describing class by class signature changes from the 12.0 to 12.5 SDK |
|
|
An HTML file
describing class by class signature changes from the 12.5 to 13.0 SDK |
|
|
An HTML file
describing class by class signature changes from the 13.0 to 14.0 SDK |
|
|
A small collection of
starter Java and C# samples |
|
|
Basic documents
covering the StarTeam security model |
|
|
StarTeam Architecture
– Parallel and Variant Development Techniques |
The
StarTeam SDK requires a Java Virtual Machine (JVM) version 1.7 or later. You
can use the latest JVM from Oracle. Be sure that a compatible JVM is installed
on your machine before installing the SDK.
StarTeam SDK Path
The
root path of the SDK is determined by the path in the setup.ini file whose content looks like
the following:
On a 32-bit Windows system
[StarTeam SDK Folders]
Programs=C:\Program
Files\Borland
Java=C:\Program
Files\Borland\Java
On a 64-bit Windows system
[StarTeam SDK Folders] //for
32-bit SDK
Programs=C:\Program
Files (x86)\Borland
Java=C:\Program
Files (x86)\Borland\Java
[StarTeam 64-SDK Folder] //for
64-bit SDK
Programs=C:\Program
Files\Borland
Java=C:\Program
Files\Borland\Java
The
setup.ini file can
be found under the All Users and current User profiles directories, for example
on WinXP: %ALLUSERSPROFILE%\Application
Data\Borland\StarTeam, and %USERPROFILE%\Application Data\Borland\StarTeam
Note: You can manually change the path for the SDK
from these two copies of setup.ini. However,
it's not recommended to do so since it may cause failure in applications that
depend on previous installation of SDKs.
The following features and fixes
are contained in build 14.0.2.21:
|
Description |
||
|
Support diff command output through stcmdEx Support reuse of post commit view and revision
labels in a vcm session |
|
|
The following features and fixes
are contained in build 14.0.2.20:
|
Description |
||
|
Introduce a public api
ViewMemberCollection::sort(SortCompare),
so SDK clients can provide their own sorting algorithm |
|
|
The following features and fixes
are contained in build 14.0.2.17:
|
Description |
||
|
9865 |
File Status now works correctly on Unix platforms
when the parent folder path is set to a symbolic link. |
|
|
9931 |
View names now appear in item history, even if
the logged in user has no access to the view. |
|
|
9934 |
stcmd
update-status now displays and reports pre and post status correctly. |
|
|
9938 |
stcmd
now provides a new move command implementation |
|
|
9941 |
Continue to support Windows 2003 platform for
backward compatibility. |
|
|
9944 |
Java SDK .jar now launches correctly on
platforms where the SDK was not installed via the installer |
|
|
9948 |
vcm
p4Merge can now be used as an alternate merge tool instead of DelatII |
|
|
9952 |
Name based folder URLs with spaces are now processed
correctly. |
|
|
9956 |
stcmd
select changes from change package report supports dynamically constructed
embedded query constraints. |
|
|
9957 |
stcmd
select linked-items report supports ‘next build’ label based queries. |
|
|
9959 |
stcmd
select report for clause supports fully qualified folder paths |
|
|
9962 |
stcmd
–s now supports -epwdfile |
|
The following features and fixes
are contained in build 14.0.2.12:
|
Description |
|
First
public 14.0 Update 2 SDK release Includes
all bug fixes from 13.0 & 14.0 Update 1 patch builds |
Copyright © 2014 Borland (A Micro Focus Company). All Borland brand and product names are trademarks or registered
trademarks of Borland (A Micro Focus
Company) in the United States
and other countries. All other marks are the property of their respective
owners.