1 Reply Latest reply: Nov 14, 2006 8:03 PM by 843844 RSS

    How to extend AVK to scan for other vendor-specific APIs?

    843844
      All--

      How do I extend AVK to scan for other vendor specific APIs.

      I tried adding another <name> element underneath the
      appropriate the <unsupported> tag in the asmt-config.xml file,
      e.g.

      <websphere50>
      <supported>
      </supported>
      <unsupported>
      <name>com.ibm.ws.activity.ActivityConstants</name>
      .......... other <name> elements were left alone ..........
      </unsupported>
      </websphere50>

      But when I scanned the source code it didn't find an import of that API.

      Note: it did find an import of the APIs that were pre-defined in the asmt-
      config file; just not the one that I added.

      Is adding a <name> to the asmt-config.xml file the right approach?

      If so, how does the SourceScan ant task know where to find the asmt-
      config.xml file. Currently, I left it in the %JAVKE_HOME%/config folder.
      Is that the right place for that file?

      Any comments on how to extend AVK to scan for other vendor
      specific APIs would be greatly appreciated.