- You should not see any deprecation warnings from out-of-the-box Curam files. However, there are instances where a deprecation issue in your custom file can appear, as if it came from an out-of-the-box Curam file. If you overrode a.VIM client file that is being used by an out-of-the-box.UIM page, any warnings from your VIM file will appear as if they came from the out-of-the-box UIM page. This is because the client build imports.VIM content into UIM pages before validating it. If you see deprecation warnings from out-of-the-box UIM pages, please be aware that they may be referring to issues in a custom VIM file.
- If you have included sample components in your build (such as Sample, CPMSample, etc), you may also see deprecation warnings from these components. Curam does not recommend including sample components in your builds.
- You will find [deprecation comment] marker, if the tag @depreceted in documentation field has a comment. This save you having to look up the file and then look up the file it's referencing and then get the comment.
- Please be aware that any deprecation warnings marked [bopigen] in the build log are duplicates of warnings produced earlier in the log and marked as [servercodegenerator]. You can safely ignore deprecation warnings marked as [bopigen].
- Warnings coming from generated java classes (those in build/svr/gen) are by-products of the [customization] warnings produced by the generator and can generally be ignored. Resolving the "[deprecation] [customization]" issues should also resolve these generated file warnings.
Note: It is easier to work with java deprecation warnings in Eclipse, than it is to use the command-line deprecation build logs.