The following features are new in iQgen 2.1:
The iQgen Eclipse integration has been updated to work with Eclipse 3, the latest version of the leading Open integrated development environment.
Previous versions of iQgen generated files whenever the source model changed. With Smart Generation, iQgen checks whether the file's contents would change when generating, and only updates the file when necessary. While generation is seldomly, if ever, a performance problem, some configuration management systems and almost all build tools mistakenly check only for the timestamp of input files, and performed unnecessary work. With Smart Generation, build and check-in/check-out times are thus significantly reduced in larger projects.
To ease support for CASE tools and other software emitting XMI, the XMI reader associated with a particular XMI generator is configurable in an external XML file.
iQgen 2.1 has been bundled as a Mac OS X application, supporting simple drag & drop installation and the native Mac OS X look & feel (i.e. the menu bar where a Mac user would expect it to be, quit, preferences and about menus in the right places, storage of user preferences in the appropriate location etc.).
The following features are new in iQgen 2.0:
Plugin for the Eclipse platform
Enhanced user interface
Hooks for model validation
Properties to control transformation settings
Improved logging for command line and Ant integration
Updated and enhanced documentation
In addition to the stand-alone user interface, iQgen is now fully integrated with the Eclipse platform. The iQgen Eclipse plugin enables you to edit templates, start the generation process, and edit the resulting artifacts - all without leaving the IDE. Combined with an Eclipse-integrated modeling tool such as TogetherEC, all of your MDA toolset can be combined in a single environment.
We have made numerous improvements to the user interface, including the ability to view stereotypes and tagged values.
Based on customer feedback, we have created hooks that allow iQgen users to validate their UML models, e.g. to check compliance to the UML profile being used. As this is a programmatic interface, there is virtually no limit to what can be checked. Validation errors can be defined to emit warnings, errors or fatal errors (the last of which will terminate the code generation process).
Not all information should be stored in the UML model; with advanced template sets, there is often a need for an easy way to provide parameters. Transformation settings are an easy-to-use solution to this problem.
Log filters that have been available in the UI only in previous versions of iQgen are now usable from both the command line and from Ant scripts that use the iQgen Ant task.