Dear List,
I worked on the Issue #2107 during the Pharo Sprint of today. This issue proposes a minimal infrastructure to control the dependencies of your package. I cleaned the code proposed by Andreas.
I introduced the class PharoCorePackageDependenciesTests. It contains few tests. An example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
testFile
self testPackage: 'Files' dependsOnlyOn:
#( 'Kernel'
'Collections-Strings'
'Compression'
'ToolBuilder-Kernel'
'Tools'
'System-Object Storage'
'Graphics'
'Collections-Sequenceable'
'Collections-Abstract'
'Collections-Streams'
'Collections-Arrayed'
'Multilingual'
'Exceptions'
'System-Support'
'System-FileRegistry'
'Collections-Weak'
'Collections-Unordered'
)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is interesting to see that File refers to the Graphics package! I provide a method to automatically generate this kind of tests. It therefore goes green. You can also inspect what are the dependencies.
By dependencies, I mean static class references.
You can find the code in the inbox:
SLICE-ArchitecturalTests-Alexandre_Bergel.2
Cheers,
Alexandre
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
