ocl4java lets you add special Java 5 annotations containing OCL expressions with pre/post conditions and invariants to your code, and have source code to check them inserted automatically by ant. Upon failing an assertion, an AssertionError, exception, log message, or user-defined handler may be called. You can use it as an Ant task, Eclipse plugin, or standalone on the command-line.
|Tags||Software Development Quality Assurance|
|Operating Systems||OS Independent|
Release Notes: A bug where assertion-style selection in annotation was ignored was fixed. A StackOverflow in user-defined Handlers was fixed. Typos were fixed. The usefulness of warning messages was increased. Many bugfixes and speed improvements were done in the Eclipse plugin, which now has reached version 2.1.7.
Release Notes: ocl4java has seen a lot of bugfixing and speed-improvements as well as the capability to defer actual source-manipulation for better locking. The plugin has reached version 2.0.0 with a large number of quick-assists to help you write correct ocl-code by hand.
Release Notes: ocl4java has finally proven stable enough over the last weeks to be called version 1.0. A lot of localization and minor modifications were done to make it more bullet-proof. You can add listeners to be informed about OCL parse errors with line-numbers now. The Eclipse plugin has reached version 1.2.3 and is undergoing rapid enhancements too.
Release Notes: @pre is now supported in postconditions. Major bugfixes were made in handling collections. Major refactoring was done to clean up the code. Code formatting and comments remain the same, and new code does not affect line-numbers. OCL-statements from superclasses/interfaces are now used for overloaded/implemented methods.
Release Notes: The code can fall back to Reflection if needed. The generator runs on itself. Function-calls and static methods can be handled in OCL. The user can choose between java-assert, Exceptiom, commons-logging, or System.err to handle OCL-failure.