Bug #3977
closedDevlop test for ptII overrides in the system
0%
Description
Standard releases of Kepler can contain no overrides because it may cause problems with loading additional modules in the future. We need a test in the build system that looks for overrides and points them out when building the release so we can be sure they do not exist in the code base. This should be pretty easy. just look for classes that claim to be in the ptolemy.* package then check to see if they have the same name as the class in the ptII tree. A cruder test would be to change the classpath so that the ptolemy jars/classes come first, hence preventing any overrides.
Updated by David Welker about 15 years ago
I am confused by the rationale here for not having overrides in the release. How could it cause problems loading additional modules?
That said, we do have a command for showing overrides. For example if I change to kepler-trunk and then issue the command "ant report-overrides" I get the following result:
report-overrides:
[report-overrides] Overrides:
[report-overrides]
[report-overrides] ptolemy.domains.sdf.kernel.SDFDirector
[report-overrides] util --> ptolemy
[report-overrides]
[report-overrides] ptolemy.vergil.actor.ActorController
[report-overrides] util --> ptolemy
[report-overrides]
[report-overrides] ptolemy.vergil.basic.BasicGraphController
[report-overrides] util --> ptolemy
[report-overrides]
[report-overrides] ptolemy.vergil.actor.ActorGraphFrame
[report-overrides] util --> ptolemy
[report-overrides]
[report-overrides]
[report-overrides] Number of overrides: 4
Updated by David Welker about 15 years ago
There are no overrides amongst the core modules of Kepler. (However, there are overrides of parts of Ptolemy.)
Updated by Chad Berkley about 15 years ago
David developed a test in the build system for this. You can run 'ant report-overrides' to see a list.