Comments on: Maven2 and JDeveloper Friends of Oracle and Java Sat, 01 Aug 2015 11:10:05 +0000 hourly 1 By: Mucahid Uslu Wed, 18 Feb 2009 15:49:59 +0000 We wanna use maven2 on jdeveloper11g. But it doesnt seem to suit yet.

By: Aino Andriessen Tue, 06 Feb 2007 12:01:01 +0000 Hi Jim,

Good point. Unfortunately, JDeveloper is not very well suited for using Maven. It does not provide any integration with maven, so you have to define external tools or use ant wrappers, which is what we do. Than, the result will be displayed in the ant output dialog; but with minimal interactive options.
Another issue is, still, the library management. Since JDeveloper cannut use variables for the path, the references to the libraries in the projectfiles are still to absolute paths, which means that all developers must have the same project directory and maven repository directory. That is if you share projectfiles.
In the meantime JDeveloper continues with its stubborn library management and new libraries will continue to pop-up in the project dependencies. Another nuisance is that the plugin cannot handle tha project and maven repository on different drives.

Our main goal with mavenizing an adf project is for project automation, i.e. perform automatically all the development lifecycle goals and not have the developer performing them manually and to be able to perform then on a seperate, integration environment. The integration with JDeveloper is currently a secondary goal, although we were able to accomplish, more or less, that for a customer by defining a standard developer environment.

Concerning the projectfiles, I get the impression that it is quite possible to not share the projectfiles and to (re)generate them when relevant changes have been made in the pom file.


By: Jim S. Sat, 03 Feb 2007 08:23:50 +0000 If anyone is still following this… Forgive my newby question please. So this plugin generates the JDev jpr file, creating entries in the Libraries list, so that I’m not drowning in red underlines in the text editor, so I have my right-click to source/javadoc/etc. But, it appears that the build is still done w/ the JDev-specified JDK, JDev dependency mechanism, etc, which subverts the whole Maven ‘continuous build’ process? So should I setup External Tools to run mvn w/ various goals from within JDev? Should I setup Ant tasks of some sort? In either of these approaches, how do I then (or can I even) get JDev to parse the resultinig output to provide me the ‘jump to source error’ capability that I usually get in the Compiler Log tab? Also, if I make changes to my pom, do I need to re-run the mvn jdev:jdev command in order to update my JDev Library entries? Any other tricks, hints, tips, etc that anyone can share? Thanks!

By: Aino Andriessen Mon, 23 Oct 2006 23:44:32 +0000 Sorry, I added some xml code, which does not show in the comment. The code can be found at :

By: Aino Andriessen Mon, 23 Oct 2006 23:42:22 +0000 Or add the following to your (parent) project pom.xml :


By: Martin van den Bemt Mon, 24 Jul 2006 11:48:23 +0000 Extra note : the jdev plugin is going to move to the maven project itself (be it or apache maven subversion, so in that case jdev:jdev will start working again :)

By: Martin van den Bemt Mon, 24 Jul 2006 11:37:28 +0000 Hi Maarten,

First of all, maven2 doesn’t use a plugin registry anymore, so the plugin doesn’t need to register.
The problem you are facing is that if you just specify jdev:jdev, internally maven will actually execute org.apache.maven.plugins:jdev:jdev or if that is not working, org.codehaus.mojo:jdev:jdev, which is not where the plugin resides. Even though maven cannot find the plugin it will however create a directory structure with the metadata (don’t have clue why though).
So plugins not in org.apache.maven.plugins or in should be written like this :
groupId:artifactId:goal (in my case I still use the old plugin, which makes it mvn org.apache.myfaces.adfbuild:maven-jdev-plugin:jdev. You can find the groupId and the artifactId in the pom.xml of the plugin though..

By: Maarten Brugman Tue, 11 Jul 2006 17:29:45 +0000 Good stuff!
I’m currently working in a JDeveloper shop and we want to use Maven. This would make the two interoperate much better.

Unfortunately, it does not work on my system.
When I invoke mvn jdev:jdev, I get “The plugin ‘org.apache.maven.plugins:maven-jdev-plugin’ does not exist or no valid version could be found.”
When I look in my local repository, I see a directory /org/apache/maven/plugins/maven-jdev-plugin, and only 1 file in it: maven-metadata-central.xml.
The other plug-ins in the repository contain version directories.
So it seems to me that the jdev plug-in did not get registered correctly, although the installation reported success.
Note: I’m using the latest maven, 2.0.4.
Any thoughts or help on this would be much appreciated.