Cross platform Maven ADF 12c JDeveloper projects

When you create a new ADF project on JDeveloper 12c that supports Maven or convert a new project to support maven the JDeveloper wizard will add to project or application pom files ojmake and ojdeploy plugins for compile source code and generate jar, adf library jars, view controller war or ear file. If you are in a windows machine the JDeveloper create a plugin entry like the following:

&lt;plugin&gt;
&lt;groupId&gt;com.oracle.adf.plugin&lt;/groupId&gt;
&lt;artifactId&gt;ojmake&lt;/artifactId&gt;
&lt;version&gt;12.1.3-0-0&lt;/version&gt;
&lt;configuration&gt;
&lt;ojmake&gt;
${oracleHome}/jdeveloper/jdev/bin/ojmake.exe
&lt;/ojmake&gt;
&lt;files&gt;
${basedir}/test-maven.jws
&lt;/files&gt;
&lt;usemaven&gt;
true
&lt;/usemaven&gt;
&lt;/configuration&gt;
&lt;executions&gt;
&lt;execution&gt;
&lt;phase&gt;compile&lt;/phase&gt;
&lt;goals&gt;
&lt;goal&gt;compile&lt;/goal&gt;
&lt;/goals&gt;
&lt;/execution&gt;
&lt;/executions&gt;
&lt;/plugin&gt;

for Linux or Mac JDeveloper create the following:

&lt;plugin&gt;
&lt;groupId&gt;com.oracle.adf.plugin&lt;/groupId&gt;
&lt;artifactId&gt;ojmake&lt;/artifactId&gt;
&lt;version&gt;12.1.3-0-0&lt;/version&gt;
&lt;configuration&gt;
&lt;ojmake&gt;
${oracleHome}/jdeveloper/jdev/bin/ojmake
&lt;/ojmake&gt;
&lt;files&gt;
${basedir}/Model.jpr
&lt;/files&gt;
&lt;usemaven&gt;
true
&lt;/usemaven&gt;
&lt;/configuration&gt;
&lt;executions&gt;
&lt;execution&gt;
&lt;phase&gt;compile&lt;/phase&gt;
&lt;goals&gt;
&lt;goal&gt;compile&lt;/goal&gt;
&lt;/goals&gt;
&lt;/execution&gt;
&lt;/executions&gt;
&lt;/plugin&gt;

This files are depend to platform. This creates problems in multi platform development groups. For example if a developer creates a project from a windows machine and then commit in an SCM (svn, git etc) and one other developer checkout the project from a mac or linux machine the project will not run because jdeveloper will look for ojmake.exe and ojdeploy.exe.
ADF projects that jdeveloper creates depends on a parent pom called adf-parent pom. In that pom file the ojdeploy and ojmake are declared in the correct way for support multiplatform developer groups. The following is a part of that pom file that explains that maven can find the platform commands with no platform issues:

&lt;profile&gt;
&lt;id&gt;windows&lt;/id&gt;
&lt;activation&gt;
&lt;os&gt;
&lt;family&gt;Windows&lt;/family&gt;
&lt;/os&gt;
&lt;/activation&gt;
&lt;build&gt;
&lt;pluginManagement&gt;
&lt;plugins&gt;
&lt;plugin&gt;
&lt;groupId&gt;com.oracle.adf.plugin&lt;/groupId&gt;
&lt;artifactId&gt;ojmake&lt;/artifactId&gt;
&lt;version&gt;12.1.3-0-0&lt;/version&gt;
&lt;configuration&gt;
&lt;ojmake&gt;${oracleHome}/jdeveloper/jdev/bin/ojmake.exe&lt;/ojmake&gt;
&lt;files&gt;${basedir}/${project.artifactId}.jws&lt;/files&gt;
&lt;usemaven&gt;true&lt;/usemaven&gt;
&lt;/configuration&gt;
&lt;executions&gt;
&lt;execution&gt;
&lt;phase&gt;compile&lt;/phase&gt;
&lt;goals&gt;
&lt;goal&gt;compile&lt;/goal&gt;
&lt;/goals&gt;
&lt;/execution&gt;
&lt;/executions&gt;
&lt;/plugin&gt;
&lt;plugin&gt;
&lt;groupId&gt;com.oracle.adf.plugin&lt;/groupId&gt;
&lt;artifactId&gt;ojdeploy&lt;/artifactId&gt;
&lt;version&gt;12.1.3-0-0&lt;/version&gt;
&lt;configuration&gt;
&lt;ojdeploy&gt;${oracleHome}/jdeveloper/jdev/bin/ojdeploy.exe&lt;/ojdeploy&gt;
&lt;workspace&gt;${basedir}/*.jws&lt;/workspace&gt;
&lt;profile&gt;${project.artifactId}-${project.version}&lt;/profile&gt;
&lt;usemaven&gt;true&lt;/usemaven&gt;
&lt;/configuration&gt;
&lt;executions&gt;
&lt;execution&gt;
&lt;phase&gt;package&lt;/phase&gt;
&lt;goals&gt;
&lt;goal&gt;deploy&lt;/goal&gt;
&lt;/goals&gt;
&lt;/execution&gt;
&lt;/executions&gt;
&lt;/plugin&gt;
&lt;/plugins&gt;
&lt;/pluginManagement&gt;
&lt;/build&gt;
&lt;/profile&gt;
&lt;profile&gt;
&lt;id&gt;unix&lt;/id&gt;
&lt;activation&gt;
&lt;os&gt;
&lt;family&gt;unix&lt;/family&gt;
&lt;/os&gt;
&lt;/activation&gt;
&lt;build&gt;
&lt;pluginManagement&gt;
&lt;plugins&gt;
&lt;plugin&gt;
&lt;groupId&gt;com.oracle.adf.plugin&lt;/groupId&gt;
&lt;artifactId&gt;ojmake&lt;/artifactId&gt;
&lt;version&gt;12.1.3-0-0&lt;/version&gt;
&lt;configuration&gt;
&lt;ojmake&gt;${oracleHome}/jdeveloper/jdev/bin/ojmake&lt;/ojmake&gt;
&lt;files&gt;${basedir}/${project.artifactId}.jws&lt;/files&gt;
&lt;usemaven&gt;true&lt;/usemaven&gt;
&lt;/configuration&gt;
&lt;executions&gt;
&lt;execution&gt;
&lt;phase&gt;compile&lt;/phase&gt;
&lt;goals&gt;
&lt;goal&gt;compile&lt;/goal&gt;
&lt;/goals&gt;
&lt;/execution&gt;
&lt;/executions&gt;
&lt;/plugin&gt;
&lt;plugin&gt;
&lt;groupId&gt;com.oracle.adf.plugin&lt;/groupId&gt;
&lt;artifactId&gt;ojdeploy&lt;/artifactId&gt;
&lt;version&gt;12.1.3-0-0&lt;/version&gt;
&lt;configuration&gt;
&lt;ojdeploy&gt;${oracleHome}/jdeveloper/jdev/bin/ojdeploy&lt;/ojdeploy&gt;
&lt;workspace&gt;${basedir}/${project.artifactId}.jws&lt;/workspace&gt;
&lt;profile&gt;${project.artifactId}-${project.version}&lt;/profile&gt;
&lt;usemaven&gt;true&lt;/usemaven&gt;
&lt;/configuration&gt;
&lt;executions&gt;
&lt;execution&gt;
&lt;phase&gt;package&lt;/phase&gt;
&lt;goals&gt;
&lt;goal&gt;deploy&lt;/goal&gt;
&lt;/goals&gt;
&lt;/execution&gt;
&lt;/executions&gt;
&lt;/plugin&gt;
&lt;/plugins&gt;
&lt;/pluginManagement&gt;
&lt;/build&gt;
&lt;/profile&gt;

So the JDeveloper wizards create platform dependent poms for ADF projects.
To create a cross platform ADF maven enabled project you need to remove the ojmake and ojdeploy paths from project pom files. JDeveloper can still find the commands on file system using the ADF parent pom file.
As an example for ojmake we need to remove this code part from ADF project pom or ADF application pom file:

&lt;ojmake&gt;
${oracleHome}/jdeveloper/jdev/bin/ojmake.exe
&lt;/ojmake&gt;

Author
Recent Posts

Chris Vezalis

Senior Software Engineer at Nodalpoint

Active in IT since 2000.
My areas of expertise are Oracle Middleware Products (WebLogic, ADF, SOA Suite), Linux, JAVA, JavaScript and DevOps.