You first need to identify the java file that's causing the issues. When you view the logs again, you'll probably notice the line above will the prefix, INFO [SourceCompiler] after fileObjects . From my experience, these are the java files that compiled successfully. The java file which is being the troublemaker is often not on that list. So it's a good starting point if you have multiple scheduled tasks and/or event handlers

The error, DEBUG [SourceCompiler] Compilation failed. Verify the project classpath. is not necessary a classpath issue but in my experience, a compiling issue of the scheduled tasks and/or event handler. The issue lies with the syntax validation discrepancy with Java Developer and OIM.

I will update this blog progressively over time on new plugin errors though below are my findings to date

You must ensure that within 'for' loops, you're initiating the variable. Java does not require you to enter this information here though it's often an old habit by developers. You must ensure that if you're using the first information before the semi-colon, that you in fact initiate and not just declare the int variable (example below)

This will not cause a Java Developer syntax error though will in fact throw An error occurred while deploying plug-in to OIM error if you tried to deploy the code.

This is an elaboration of the first issue though enhanced for loops are prohibited. Again you can enter in the correct syntax and Java Developer won't say a word, though when it comes to compiling and deploying to OIM, you'll get the error that it could not be deployed along with the 'complication failed' error as above (see error)

About the author