This content has been marked as final. Show 2 replies
I am going to assume it has been replaced by empdk validate_plugin, as shown in the Extensibility Programmer's Reference, page 13-6.
Additional advantage: my client ‘gets’ it too :-)
C:\Users\abc\Downloads\Oracle>empdk validate_pluginvalidate_plugin command usage:
empdk validate_plugin -stage_dir <staging directory>
[-tmp_dir <temporary working location>]
[-out_dir <output directory>]
[-conn_desc <Connect descriptor to em repository>]
[-repos_user <EM repository owner>]
[-debug [<file to output debug information>]]
-tmp_dir : Specify some existing directory else will give error. If not specified then out directory will be used for temp location.
-out_dir : by default report file will be generated in the current directory
-debug :Specify some file name where you want to store the debug information. if not specified the default log file (validateplugin.log<time>) will be created in the out directory and will store only warning and error message. if specified then it will store all the debugging information to that log file
-format : If format is not specified, it defaults to text.
-validationType : If validationType is not specified validation of all types are performed.
-conn_desc, -repos_user: If -validationType option has one of sql,all or -validationType is not specified, then these are mandatory.