Explanation is not clear. I hope that PR 465 solves the issue.

In fact this issue is not so easy to solve.

There are two container relationships between Package and Type (or Class). So there are two ways to get the classes from the package, using childEntities or types. And symetrically, it is possible to reach a package from a class using parentPackage or typeContainer. Depending how the model is built only one is used.

There are different possibilities to solve this issue:

• derive one relation from the other, but a package can also contain Packages and a Class can be contained by Methods or Types. So not easy to choose which relation to derive.
• remove the fact that a Package is a TWithTypes, which will remove the typeContainer relationship between a class and its package. It is certainly the better solution, but we need to check if it is compatible with VerveineJ.

@NicolasAnquetil @aranega @badetitou

OK so PR #465 did not solve the issue apparently because the CI refused it

As we are using traits, we could redefine the #types method to call #childEntities+appropriate select but not sure it is worth the effort