JDeveloper Maven support is so close to being good

[Mark Robinson]

Hey Guys,

I've found some large issues vis-a-vis Maven support in JDeveloper that make it useful for single developers but break horribly when you expand to multiple developers.

1) Maven home directory is hard-coded in .jpr files

So I install JDeveloper to C:\JDev-11.1.1.2.0.0 and you install it to C:\JDeveloper-11.1.1.2.0 we will not be able to share jpr files.  What happens is that if you select "Use application version of maven" in the project properties and use Default Maven version in the Application properties it will put:

     <url n="mavenHome" protocol="file" path="/C:/Oracle/Middleware-11.1.2.0/jdeveloper/apache-maven-2.2.1/"/>

 

in the jpr files.

So everyone has to have the same install scheme for this to work.

2) User settings file can get hard-coded in .jws file.

If the field "Settings file" in the Application Properties dialog is left blank then it defaults to ${user.dir}/.m2/settings.xml.  This is fine, except the next time you open the dialog the field will be populated and if you make any changes it will save it as c:\Users\mrobinson\.m2\settings.xml in the JWS file.  So it works fine, until someone else checks out the project.

The only workaround I have for this is to centralize the settings.xml file somewhere in the project tree.

3) Maven sourced libraries are hard-coded to a specific user.

Adding a library that was pulled in via Maven causes it be saved in the jpr file as:

   <url protocol="file" path="/C:/Users/mrobinson/.m2/repository/org/jdom/jdom/1.1/jdom-1.1.jar"/>

Oops!

The only work-around in the current version is to set the Maven repository to somewhere in the project tree but not check in that folder.


Mark

[Jan Vervecken]

hi Mark

Do you know if enhancement requests (or bugs) exist to improve the
behaviour you describe?
If those don't exist, and if you want this behaviour to change in a
future release, you should probably open an service request on
http://support.oracle.com and request to create one or more
enhancement requests (or bugs) based on the information you have
posted here.
Please post the relevant enhancement request (or bug) numbers here, or
the feedback you might get in the service request on how to avoid the
behaviour you describe (if possible).

success
Jan Vervecken