The problem with ojdeploy is that it is being invoked several times during building process which contributes significantly to overall building time. To solve this problem Oracle provided for us a service-like utility which is called ojserver. This command line tool should be started first with the following command:
it starts listening on localhost:2010 (this can be changed through parameters) for build tasks flowing from ojdeploy, which this time should be invoked with two additional parameters:
-ojserver -address localhost:2010
so that brings us back to our pom.xml. In order to use that two parameters in your plugin configuration you should add them in the following way:
Using this approach during my tests I have managed to shorten the overall building time almost twice so this option is definitely worth considering. If you want to learn more about ojserver I recommend an interesting article available here.