This build can take some time to run, as it has to do a clean followed by server and client build, in order to identify all dependencies. The target also does the validations for several artifact types.
Although the deprecationreport target generates the deprecation build log, it is not always necessary to rerun the entire build in case it fails. If the build fails due any validation, the validation target can be ran in isolation. After fixing all the validation issue, deprecationreport target should be executed to ensure the deprecation build log is complete.
The deprecationreport calls the validation target. For example: The deprecationreport will fail if validateallworkflows target will report an error, as the build output from other builds is not available.
[deprecation] The client has not been built and therefore it
cannot be determined if UIM pages referenced are
deprecated.
By default the Java compiler limits the number of compiler warnings displayed. The Cúram build specifies this limit as 10,000, which means that the compiler will display 10,000 warnings followed by a message that, there were further warnings. This value can be overridden by passing -Dcmp.maxwarnings to the build.
IEG scripts can also contain dependencies on server and/or client artifacts that have become deprecated. However, this scenario is not covered by validation targets at this time. If you have IEG scripts, you will need to manually inspect UIM page and server interface references to identify any dependencies on deprecation pages or interfaces.
Note: Since some warnings can be broken over more than one line, it is useful to hold on to the original deprecation.log as well.