The recent change in Sigtest introduces new names of class constructors used in the signature data file. A constructor name has been changed from the class name form (more or less) to the simple "init" string constant. This change leads to potential problems with tools that use (or are based) on Sigtest like.

Here is the short list of the tools that can be potentially effected by this change:
    - APICover reporting (especailly in text format)
    - JCov signature filtering
    - CCMP tool (a tool owned by the JCK team and using for comparing and validating APICover and JCov coverage reports).

This also makes Sigtest inconsistent with VM spec where constructors have a special name - "<init>".

The better fix for this issue seems to be use the VM notation for constructor names in signature files.