Confusing support for qualified EPackage names

[tfonda-fbk]

Hi,
I noticed that the standard Ecore model editor shows an error if one names an EPackage something like foo.bar.baz (as defined in EcoreValidator#validateENamedElement_WellFormedName()). However, class ModelImporter contains some code that handles such names while generating the .genmodel file from an Ecore model, see here.
In particular, if an Ecore model contains an EPackage with a name containing at least one dot:

• the genmodel generation process shows at least one error dialog, but it succeeds
• the Ecore file is modified as part of the process (this also happens in some other scenarios/corner cases, and indeed I think it is a confusing side effect). As part of this modification, an EPackage named as in my example above has its name set to baz, while the foo.bar prefix is moved into the Base Package name field in the genmodel file.

Is this inconsistency intended?
Cheers!

[merks]

EMF is very old. I would neither change the validator nor remove things from the importer at this point. Better to avoid anything that's diagnosed as an error or warning (even if the importer handles it somewhat gracefully) and use GenModel annotations (a somewhat newer feature to support Xcore) if you want to set things in the Ecore model that end up directly setting some Gen* property value.