Am 2016-12-10 um 16:18 schrieb Christian Schulte:
It would be cool if someone could answer the questions I raised in this
<http://www.mail-archive.com/[email protected]/msg111298.html>
thread. I would still need to remove those system properties from the
'DefaultModelBuilder', for example.
<http://www.mail-archive.com/[email protected]/msg111325.html>
<http://www.mail-archive.com/[email protected]/msg111326.html>
IMHO, introduce that damn 'include' scope in 3.4, and be done with it.
We cannot change the 'import' scope behaviour for model version 4.0.0
that way but most of the users using that 'import' scope find it useless
sooner or later and will probably upgrade to use the 'include' scope
sometime in the future, when that is available. Just someone answer the
questions. Maybe discuss this at PMC level because the reporters
+1 if PMCs having a problem making import scope work as advertised. I
still think is that if this is broken -- against the spec -- it must be
fixed.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
