Configuring Maven

JDeveloper is a useful Java IDE that enables a Java Developer to  work  on Oracle applications.

 The plugin is available from:

http://maven.apache.org/maven-1.x/plugins/jdeveloper/

Download the latest plugin in the default directory for your Maven plugins.

Mine is in $MAVEN_HOME/plugins/ 

Maven jdeveloper plugin has one goal (jdeveloper) that:

Generates a .jpr file for JDevelopr describing the project and adding the dependencies.

  1. The build source directory
  2. The build unit test source directory
  3. Each Maven project dependency
  4. An output directory for compiled code: target\jdeveloper-classes

 The only tricky part that is not explained that well is setting of the two mandatory properties in build.properties. build.properties files is in your home directory  and should contain plugin settins as descibed in:

http://maven.apache.org/maven-1.x/plugins/jdeveloper/properties.html.

Mine settings are:
maven.jdeveloper.relative.path=../../../../../../..
maven.jdeveloper.maven.home=/home/igor/.maven

 These are absolute paths from the directory where 'jdev' (JDeveloper executable) is installed to the root of my file system and back from the root to the .maven directory where plugin will find local dependent jar files.

 After you invoke

maven jdeveloper,

a new .jpr file is created (which can be done as many times as you want, but some other project settings might get lost) which should point to the correct jar files in the .maven/repository. The dependencies are read from the project.xml file.

You can check if JDeveloper sees the new dependencies in Applications tab, by expanding 'library' icons. The jar files should reveal full content. If you do not see jar files structure check .jpr file for proper library URLs. For example, with targetID 'oracle' and artifactId 'ojdbc', the jdeveloper plugin defined that ojdbc14.jar file is in the .maven/repository/ojdbc/jars, contrary to the definition of targetId as being the directory in repository.

Note: Maven 1.0 plugin is not supported anymore, and I have not seen a new version for Maven 2.0 out there.

  • No labels