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
out of
found this valuable.
Do you find this valuable?
Show Last Reply
|
|
Last Reply:
RE: Comments on project structure
By: ,
Feb 5 2009, 8:09 AM EST
"Hi Sandra,
>> We also use a separate deployment project for deployment to the appserver
>With 10g we did not need that, with 11g we have not succeeded yet to automate the deployment to WLS using maven. Do you have an example you can share?
We do this to be flexible in deploying the application version. We used to do it in the ear file, but that limited us to the current version. Basically we use the exec plugin in combination with the admin_jar utility; I'll post an example later. I haven't tried the new cargo plugin for OC4J and have limited experience with 11g.
>> Why do you have all the jpr's in the application's directory?
>To avoid mixing design time files with files needed for building the application, we keep all files that are only needed for JDeveloper design time in a >separate jdeveloper folder outside of the Model and ViewController projects.
I still don't understand this explanation. Do you use the jpr files in maven execution?
In addition, we use ant build files as wrapper for maven tasks instead of external tools.
Ciao
Aino" > In addition, we use ant build files as wrapper for maven tasks instead of external tools. That is a good idea, can you add how to do that to the wiki?
out of
found this valuable.
Do you find this valuable?
|
