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.

Ciao
Aino

org.apache.myfaces.trinidadbuild
maven-jdev-plugin

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 org.codehaus.org 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..

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.