ADF 11gR2 and Maven

[rutwik ::]

Hi,

My client have developed suite of applications in ADF 10g, which are build and deployed using Ant build script and Hudson.

Now we are moving towards 11gR2. All the post in this forum related to how to structure the project etc have been very useful in this exercise.

In 10g we have been using CVS to store and distribute likes of third party jars and our common framework artefacts across projects.

It seems Maven is better suited for this purpose.

By looking at emails from the group, people seems have mixed opinion on use of Maven for 11g. 

Do the improvements in 11gR2, on the Maven front, have made it a better option to use Maven for 11gR2 build/deployments?

Anyone in this forum using Maven to store and distribute Oracle ADF framework and organisation framework libraries?

If so, can you please point to any documentation / links to help us take-up Mavel for our 11g projects.

--
thanks
- rutwik :)
Smile: A curve that can set a lot of things straight

[Jan Vervecken]

hi rutwik

As related to your question, see also this forum message by Brian Fry
(Oracle) on Sep 30, 2011
starting with "A couple (or more) words on Maven and ojdeploy..."
at https://forums.oracle.com/forums/message.jspa?messageID=9907587#9907587

success
Jan Vervecken

[John Stegeman]

> Do the improvements in 11gR2, on the Maven front, have made it a better option to use Maven for 11gR2 build/deployments?

In my opinion (I've stated my reasons in various places, including this group) - yes, it's better than before, but still requires a good deal of effort to set up (particularly for the ADF framework JARs). If you invest the effort in both setup and process enforcement, then you can make it work, but for me to say that Maven is "ready-for-prime-time" with ADF, there's more to be done on the IDE side.

John

[D0natas]

Hi rutvik,

We have been using Maven as a primary tool in our environment
(multiple ADF projects + Artifactory as repository manager) for
some time.

The basic procedure (without a Maven support in JDeveloper) was:

1. discover (and "disassemble") all dependencies JDeveloper creates
when creating a project
2. write down dependencies discovered into poms.
3. install all jars into repository
4. discover and "disassemble" the "automagic":
JDeveloper makes changes and creates additional artifacts
sometimes when application is deployed in IDE. Write down the
"automagic" discovered into files used in a maven build (web.xml,
.adf , weblogic.xml and so on..)

The steps have to be repeated , when JDeveloper version changes (once
a year i think in average, we have been using Maven with ADF for
almost 4 years till now). It is basically manual effort every time,
with some scripting.

Maven support introduced with new Jdeveloper provides IDE support for
steps 1 to 3 for you (Synchronisation of dependencies between
JDeveloper project configuration and pom).
The "automagic" is still there, so one have still to discover it
somehow manually, unless documented.

I would describe "Automagic" this way: if some application build with
maven doesn't behave the same like in JDeveloper, don't believe what
JDeveloper shows to you (for example web.xml) , but take a look at it
here (example):

06:26:51 PM] Wrote Web Application Module to
C:\JDEV_USER_HOME\system11.1.2.1.38.60.81\o.j2ee\drs\YourApplication\YourWebApp1.war
[06:26:52 PM] Wrote Web Application Module to
C:\JDEV_USER_HOME\system11.1.2.1.38.60.81\o.j2ee\drs\YourApplication\YourWebApp2.war
[06:26:54 PM] Wrote Enterprise Application Module to
C:\JDEV_USER_HOME\system11.1.2.1.38.60.81\o.j2ee\drs\YourApplication

Hopefully it helps you and others when you read the post from Brian
Fry and the discussion in OTN.

The effort you put once to configure poms (might take some week for 1
member in a project) provide a stable environment for the rest of the
time (months or years) and for all members of a project.
As a side effect, you are forced to discover the "automagic" and after
that you can look at documentation in order understand it, if it is
still not clear whats going on.

Regards, Donatas

2012/2/8 rutwik :: <rut...@gmail.com>:

> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodolo...@googlegroups.com
>
> All content to the ADF EMG lies under the Creative Commons Attribution 3.0
> Unported License (http://creativecommons.org/licenses/by/3.0/). Any content
> sourced must be attributed back to the ADF EMG with a link to the Google
> Group (http://groups.google.com/group/adf-methodology).