19 May
2014
19 May
'14
11:34 a.m.
Hello,
I am having a look why do we get several dirty packages because of
FamixDiff. So, when I load FamixDiff in a fresh moose image, the following
are marked as dirty so please have a look:
- FAMIX-Extensions: FamixDiff over-writes FAMIXPackage >>containedEntities
- FamixDiff deletes all test classes in
packages: Moose-TestResources-PackageBlueprint-P2,
Moose-TestResources-PackageBlueprint-P3,
and Moose-TestResources-PackageBlueprint-P4.
Will be great if someone can have a look.
usman
20 May
20 May
2:12 p.m.
The method FAMIXPackage>>containedEntities for FamixDiff considers all
kind of possible sub-entites: classes, global variables, package, functions
The method for Famix-Extension, just considers classes
So it seems our implementation is more generic ...
Further more it seems it is only used in FamixDiff, so I would suggest
to commit our version to Famix-extension ...
Pb with TestResources packages should be corrected now
nicolas
On 19/05/2014 11:34, Usman Bhatti wrote:
Hello,
I am having a look why do we get several dirty packages because of
FamixDiff. So, when I load FamixDiff in a fresh moose image, the
following are marked as dirty so please have a look:
- FAMIX-Extensions: FamixDiff over-writes FAMIXPackage >>containedEntities
- FamixDiff deletes all test classes in
packages: Moose-TestResources-PackageBlueprint-P2,
Moose-TestResources-PackageBlueprint-P3,
and Moose-TestResources-PackageBlueprint-P4.
Will be great if someone can have a look.
usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3869
days inactive
3870
days old
1 comments
2 participants
participants (2)
-
Nicolas Anquetil -
Usman Bhatti