Dear EPF Committers and Users.
As reported yesterday, we discovered
bugs in the persistency code for processes in M5 and RC1. These bugs
have now been fixed in RC2 and a new build is available for you to download
from here:
If you are planning to make any changes
to the OpenUP capability patterns or delivery process (or processes in
your own libraries) it is important to upgrade to this version of the tool.
I fixed and verified all OpenUP processes
in CVS, so there is no further action necessary.
How can you find out that process in
your own libraries are broken and need fixing?
- Open your processes in the editor
one by one and see if you get a warning that there are unresolved references.
If not open the top-level activity diagram and check for the same thing.
- If you get the warning, do the following
to fix the problem:
- Select Cancel in the
warning dialog
- Select this option under
Windows --> Preferences: Method Authoring --> Library Options:
Discard Unresolved References
- Open your process. When
you see the warning press OK this time.
- Make a change in your
process such as add and delete an Activity to force a Save.
- Save the process and
exit the tool.
- Start the tool again
and check that the problem is gone.
If this did not fix it then find or
open the Problems view (menu Window-->Show View-->Other..: General-->Problems).
If you see entries listed there do the following:
- right-click one or more issues in
the Problems view and select Quick Fix
- a dialog opens asking you if it should
attempt to fix: select OK
PETER HAUMER, Dr. rer. nat.
Rational Method Composer | Eclipse Process Framework
Rational Software | IBM Software Group
Tel.: +1 408 863-8716
______________________________________________________________