For performing all the subsequent steps successfully, make sure the following software requirements are met:
ATTENTION: Note that the CVS of the Dresden OCL2 Toolkit is outdated and will be now longer updated. Now, the Dresden OCL2 Toolkit uses SVN. For further details regarding SVN look into the download section.
The following instructions presume usage of a simple command line CVS client. You can of course use your favorite graphical CVS client such as WinCVS instead. When encountering problems, please refer to the documentation on SourceForge on checking out from CVS.
cvs -d:pserver:anonymous@cvs.sourceforge.net: /cvsroot/dresden-ocl logincvs -d:pserver:anonymous@cvs.sourceforge.net: /cvsroot/dresden-ocl checkout src -Pcvs -d:pserver:anonymous@cvs.sourceforge.net: /cvsroot/dresden-ocl checkout build.xml{BASE-DIR} denotes the directory you have checked the sources out into.
If your work directory during the checkout has been c:\dresden-ocl then
that is your base directory.
{BASE-DIR}/ant jar.ocl-togetherocl-together.jar
in {BASE-DIR}/build.
{TOGETHER-BASE-DIR} denotes your copy of Together ControlCenter's
base directory.
dresden-ocl as subdirectory in
{TOGETHER-BASE-DIR}/modules/com/togethersoft/modules (the name
you choose for that directory doesn't really matter).{BASE-DIR}/build/ocl-together.jar into
{TOGETHER-BASE-DIR}/modules/com/togethersoft/modules/dresden-ocl.Tools --> Activate/Deactivate Features and check OCL Editor
and OCL Injector in the Early Access tab.OCL Constraints in the Inspector where you
can now add OCL constraints.