Tom Morris wrote:
(...)
I found an Eclipse launch definition for the C++ tests, so I didn't
need to resort to Linus' suggestion of renaming directories. At first
glance I'd say that the tests are probably creating multiple projects
(and associated extents) and not being careful to keep all related
elements in the same project (ArgoUML still has lots and lots of
places that assume a single project, so it probably should only be
using a single project for now). I can improve buildClass(element) so
that it creates the new Class in the same extent as target (instead of
the default extent as it does now), which may help, but probably won't
fix the root cause.
Tom
Thanks for your hints Tom, I'll try to change the tests setup code so
that the profile initialization is performed first and the project's
model element afterwards.
I think that improving buildClass(element) would not be enough, because
we would have problems in other parts of the API. Maybe for 0.28 we look
into this more carefully, but, for now this seams to be a problem only
in the test code and in the argouml-cpp project in specific, so, the fix
should be done in this test code.
Thanks,
Luís
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
