(Please also add bug reports to our issue tracker. For this one, I
. It makes things
easier for us to manage.)
The problem was in how we compute historical identity. Currently, it
is based on the method historicalUniqueName which by default returns
mooseUniqueName. mooseID would not help here, because you will not
get the same mooseID in two different versions, so you cannot
identify an entity based on that.
Furthermore, a FAMIXPackage is pacakgedIn in another package and that
has no impact on the mooseUniqueName. So, in your case, CodeCity
would appear with the same historicalName.
I fixed the problem (MooseDevelopment 3.2.31) by changing the
FAMIXPackage>>historicalUniqueName to take into account packagedIn. I
also added a test for that.
On May 28, 2007, at 8:09 PM, Richard Wettel wrote:
I have a slight problem with Hismo. I have a bundle with name
CodeCity and in that bundle I have several packages, one of which is
also called CodeCity.
After creating a History from several versions of the system, I
realized that somehow Hismo is not able to distinguish between the
two. Although in the MooseModels of the versions there are 2
FAMIXPackages that are related to each other (one of them belongsTo
the other), after creating a history I end up having one single
PackageHistory called CodeCity. Somehow, Hismo flattens the two...
I guess this is also because the bundles and packages in Smalltalk
are both modeled by the FAMIXPackage in Moose, but I would expect it
to take the mooseID into account on this one. Could you please fix
Moose-dev mailing list
"Every successful trip needs a suitable vehicle."