Maven support in 11.1.1.2 / repository question

Question

Oracle team,
Great job on 11.1.1.2, nice to see the developer preview of Maven support. I am still in the process of downloading it; while it's coming down, I thought I'd post a question..
I really like Maven, and I'd like to use it for ADF projects. With what looks like nice basic Maven support in JDev, there is only one thing that holds me back at the moment, and that is having the Oracle ADF libraries in a repository. Yes, it's quite easy for me to put them in my own repository, and that is something I'd like to move forward with. However, in order to make that process more resilient, it would be nice if Oracle published a recommended structure for the artifact names; in that way, I could be more or less sure that I won't have to re-do everything in the future. I've even considered (if Oracle does publish a recommended taxonomy) writing an extension that would snarf all of the JDeveloper library definitions and publish them to a repository, and furthermore to change the local library definitions to point to my local Maven copy.
Thoughts on this?
John

Answer 1

Muhammed,
I'm not clear on your question, but here is an example. We have a project that uses ADF BC4J.
Here is a example of a dependency specification from the project pom:
<dependency>
<groupId>com.oracle.jdeveloper.library</groupId>
<artifactId>BC4J_Runtime</artifactId>
<version>${jdev.release}</version>
<type>pom</type>
<exclusions>
<exclusion>
<groupId>com.oracle.jdeveloper.jars.lib</groupId>
<artifactId>xmlparserv2</artifactId>
</exclusion>
<exclusion>
<groupId>com.oracle.jdeveloper.jars.lib</groupId>
<artifactId>xml</artifactId>
</exclusion>
<exclusion>
<groupId>com.oracle.jdeveloper.jars.jlib</groupId>
<artifactId>oracle-el</artifactId>
</exclusion>
<exclusion>
<groupId>com.oracle.jdeveloper.jars.jlib</groupId>
<artifactId>jsp-el-api</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.oracle.jdeveloper.library</groupId>
<artifactId>BC4J_Oracle_Domains</artifactId>
<version>${jdev.release}</version>
<type>pom</type>
<exclusions>
<exclusion>
<groupId>com.oracle.jdeveloper.jars.BC4J_jlib</groupId>
<artifactId>bc4jdatum</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.oracle.jdeveloper.library</groupId>
<artifactId>ADF_Model_Runtime</artifactId>
<version>${jdev.release}</version>
<type>pom</type>
</dependency>
And here is a fragment from the mvn dependency:tree command:
[INFO] +- com.oracle.jdeveloper.library:BC4J_Runtime:pom:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.BC4J_lib:adfshare:jar:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.BC4J_lib:bc4jmt:jar:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.BC4J_lib:collections:jar:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.BC4J_lib:bc4jct:jar:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.jlib:jdev-cm:jar:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.jlib:ojmisc:jar:10.1.3.4.0:compile
[INFO] | \- com.oracle.jdeveloper.jars.jlib:commons-el:jar:10.1.3.4.0:compile
[INFO] +- com.oracle.jdeveloper.library:BC4J_Oracle_Domains:pom:10.1.3.4.0:compile
[INFO] | \- com.oracle.jdeveloper.jars.BC4J_lib:bc4jdomorcl:jar:10.1.3.4.0:compile
[INFO] +- com.oracle.jdeveloper.library:ADF_Model_Runtime:pom:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.BC4J_lib:adfm:jar:10.1.3.4.0:compile
[INFO] | +- com.oracle.jdeveloper.jars.BC4J_jlib:adfui:jar:10.1.3.4.0:compile
[INFO] | \- com.oracle.jdeveloper.jars.BC4J_lib:adfbinding:jar:10.1.3.4.0:compile
Note that the top level is a pom that relates to a JDeveloper Library, which is then composed of JARs. The intention was to maintain as close to a one to one mapping between the JDeveloper definitions and the maven artifacts. So, JDeveloper Libraries become maven poms.