19 Aug
2007
19 Aug
'07
4:07 p.m.
As you probably saw in the previous mail, adding
EcoreImportExport to
Meta generated some loading problems when loading 'Moose Config',
because you have two classes that are in SCG.Moose namespace.
However, Meta does not depend on Moose, but Moose depends on Meta.
So, no class in the Meta bundle should be in the Moose namespace.
ok! I didn't know :(
I put this classes in SCG.Moose because they generate MooseElements
from a
EMF model... I see several solutions to fix the problem:
- move the classes to the Meta namespace for now, although they do
not belong there
- move the classes to the MooseDevelopment bundle
- move the classes in a separate bundle that has MooseDevelopment
bundle as prerequisite
Personnally, I think that I would choose the first solution. I can
publish a new version of Meta where my two classes will be nested
in Meta
namespace. So, there will be no pb any more when loading Moose.config
However, I need some advices from stef. I need his opinion because
I am
not sure that I choose the best solution :)