alexander krohn wrote:
(...)
[...]
I'll check this out tonight, but, we must be careful not to break
backwards compatibility of persisted models with ArgoUML 0.24.
Probably it will have to include some optional matching of the
OLD_PROFILE_BASE_URL.
honestly i don't care that much about breaking files, argouml from
trunk does this from time to time on my files anyway, unfortunately
not in a reproducable way :(
Breaking persistency of trunk isn't a big deal, but, breaking it for a
previously released version is becoming nasty for our users and for
ourselves. A zargo saved with ArgoUML 0.24 and before must be supported
in 0.26.
Concerning the problems you have with persistency, are these really
persistence related? I wasn't expecting that there was instability in
the persistency or zargo or XMI files...
[...]
i attached a newer version of the patch. it's still a hack but i looks
something more like a solution ;)
it should work with all profiles from modules, but i only tested the
default-uml and the c++-profile.
Thanks for your effort, but, this second patch introduces a dependency
from argouml-mdr to argouml-app, by importing stuff from
org.argouml.profile. I executed the automated tests with your first
patch with success. I also opened some old big model of mine without
problems. It should be possible to remove the problems you referred to
without having to use the org.argouml.profile classes.
Regards,
Luís
PS: probably only on Saturday or Sunday night I'll get back online again
to send news and to process your reply.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
