sigtest checks signatures of many classes at once. It presents a problem during simultaneous development and evolution of specs and TCK. A change in a single signature causes the whole sigtest fail and there is no way to exclude this one signature
from checking. It would be good to have ability to exclude some signatures from checking. The number of such excluded signature could be from 10 to 1000 or from 1% to 10% (evntually sigfiles should be updated to be in accordance with changed specs)
from checking. It would be good to have ability to exclude some signatures from checking. The number of such excluded signature could be from 10 to 1000 or from 1% to 10% (evntually sigfiles should be updated to be in accordance with changed specs)
- relates to
-
CODETOOLS-6421738 SigTest: need to provide signature exclusion mechanism
-
- Closed
-