Maven and JDeveloper ADF projectsThis is a featured page

This page's contents have been moved to the ADF Enterprise Methodology Group's Google group.


chriscmuir
chriscmuir
Latest page update: made by chriscmuir , May 14 2009, 8:39 AM EDT (about this update About This Update chriscmuir Moved content. - chriscmuir

9 words added
769 words deleted

view changes

- complete history)
Keyword tags: maven jdeveloper adf
More Info: links to this page
Started By Thread Subject Replies Last Post
aino Comments on project structure 4 Feb 5 2009, 8:09 AM EST by smuller
Thread started: Feb 4 2009, 11:32 AM EST  Watch
Hi Sandra,

I strongly oppose separate test packages because it makes protected and 'no qualifier' methods more difficult to test. Since the testcases are in a separate directory and a separate JDev project they do not clutter the project navigator
In addition we recommend a separate ear project to build the ear deliverable; Maven cannot do both the ear and war in one project. We also use a separate deployment project for deployment to the appserver and a separate project for integration tests like JMeter or Selenium or others).
Why do you have all the jpr's in the application's directory?
Do you use one pom or multiple?

We consider the model and viewController and other projects as modules / subprojects, each with their own pom file.

Ciao
Aino
Do you find this valuable?    
Show Last Reply
janveck see also forum thread "Maven Support in JDeveloper 11.1.1" 0 Feb 2 2009, 3:55 PM EST by janveck
Thread started: Feb 2 2009, 3:55 PM EST  Watch
hi

The JDeveloper forum thread "Maven Support in JDeveloper 11.1.1" has some pointers to Maven-related forum threads, and also Frank Nimphius asks about "requirements on your wish list" for Maven support.
http://forums.oracle.com/forums/thread.jspa?threadID=827732

regards
Jan Vervecken
1  out of 1 found this valuable. Do you?    
Keyword tags: JDeveloper Maven
Showing 2 of 2 threads for this page