[kepler-dev] [Bug 3977] New: - Devlop test for ptII overrides in the system

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3977

           Summary: Devlop test for ptII overrides in the system
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P1
         Component: build system
        AssignedTo: berkley at nceas.ucsb.edu
        ReportedBy: berkley at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


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.