UML-to-Java transformation Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Known problems and workarounds
   1.1 Reapplication of the UML-to-Java Transformation can result in previous files not being cleaned up

1.0 Known problems and workarounds

1.1 Reapplication of the UML-to-Java transformation can result in previous files not being cleaned up

The UML-to-Java transformation may not clean up files previously generated if they are the result of an "orphaned package" or a package that was generated previously but no longer exists in the model. This could be the result of a package in the model being deleted/renamed or the result of files that have been remapped to a new package though the mapping service.

Workaround: You must manually clean up these files.