Hi,
I am trying to see what it is possible to do with Hismo. After building a ModelHistory, I tried to inspect different entities here. The first problem that I bumped into is with NamespaceHistory. If I try to call allClassHistories on a NamespaceHistory instance, it tries to call #computeSubHistories:computedForEachVersionAs:withDescription:, which does not seem to be implemented anywhere.
Any clues on how to make this work? The purpose of this is to be able to build package histories from namespace histories of Java systems (for instance, org.bla.foo namespace will produce three nested packages).
I am working with the more-or-less-latest version of Moose, in VW7.5.
Thanks, Ricky
Hi Ricky,
Indeed, this was a bug due to an old code. It is fixed now in MooseDevelopment 3.2.14.
If you want to make nested namespaces work, first you need to have the "belongsTo" relationship at the version level between namespaces, and then the nesting at the history level is automatic. Take a look at: HismoTest>>testNamespaceInNamespaceHistories
Let us know if you have further questions.
Cheers, Doru
On May 18, 2007, at 12:01 PM, Richard Wettel wrote:
Hi,
I am trying to see what it is possible to do with Hismo. After building a ModelHistory, I tried to inspect different entities here. The first problem that I bumped into is with NamespaceHistory. If I try to call allClassHistories on a NamespaceHistory instance, it tries to call #computeSubHistories:computedForEachVersionAs:withDescription:, which does not seem to be implemented anywhere.
Any clues on how to make this work? The purpose of this is to be able to build package histories from namespace histories of Java systems (for instance, org.bla.foo namespace will produce three nested packages).
I am working with the more-or-less-latest version of Moose, in VW7.5.
Thanks, Ricky _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Tudor Girba www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/
"In a world where everything is moving ever faster, one might have better chances to win by moving slower."
Thanks, Doru.
Could you also provide in Hismo the same that you have done for FAMIXNamespace to the FAMIXPackage, with respect to #packagedIn? I am interested in creating packages in the single version MooseModels and to fix their packagedIn relation and when I create a ModelHistory from a number of versions, I get the same relation among PackageHistories?
Cheers, Ricky
On May 18, 2007, at 1:39 PM, Tudor Girba wrote:
Hi Ricky,
Indeed, this was a bug due to an old code. It is fixed now in MooseDevelopment 3.2.14.
If you want to make nested namespaces work, first you need to have the "belongsTo" relationship at the version level between namespaces, and then the nesting at the history level is automatic. Take a look at: HismoTest>>testNamespaceInNamespaceHistories
Let us know if you have further questions.
Cheers, Doru
Done. You now have support for packagedIn in version 3.2.15.
Cheers, Doru
On May 18, 2007, at 6:00 PM, Richard Wettel wrote:
Thanks, Doru.
Could you also provide in Hismo the same that you have done for FAMIXNamespace to the FAMIXPackage, with respect to #packagedIn? I am interested in creating packages in the single version MooseModels and to fix their packagedIn relation and when I create a ModelHistory from a number of versions, I get the same relation among PackageHistories?
Cheers, Ricky
On May 18, 2007, at 1:39 PM, Tudor Girba wrote:
Hi Ricky,
Indeed, this was a bug due to an old code. It is fixed now in MooseDevelopment 3.2.14.
If you want to make nested namespaces work, first you need to have the "belongsTo" relationship at the version level between namespaces, and then the nesting at the history level is automatic. Take a look at: HismoTest>>testNamespaceInNamespaceHistories
Let us know if you have further questions.
Cheers, Doru
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Tudor Girba www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/
"Problem solving efficiency grows with the abstractness level of problem understanding."