java - building an existing EAR using Maven2 -

Regarding the creation of an existing EAR in which Maven has been used, which contains several modules, we have an EAR project Including Web and Jar Projects, in which there are a total of 8 projects were created using the ear RAD and hence currently no POML file is being filed in this project. Now I want to use Maven for the project. I want to use the m2eclipse to create and create the POM. The schematic, including the ear project and others, to create a basic project and make modules under it, therefore the effective structure should be in the form of the following

workspace

  & gt; Parents' Projects & gt; Ear project & gt; Web Pros & gt; Jar1 proj & gt; Jar2 proj   
 But I have the ear file in all the files and if I import the ears at the work place then create flate structure for all the projects below  
 Workspace  
  & Gt; Web Pros & gt; Jar 1 project & gt; Jar 2 Pros   
 RAD project setup and cause of concern. Metadata files are created by this in the workspace. If I create a parent project in workspace and then import my problem in parent please advise how I can do the following  
 1> Parent project is addicted to misconduct and there are all the projects in the ear below  
 2> gtc: mediawiki-xid = "p>  
 Hopefully my position and requirment is clear, Please advise on this  
 Thanks Narayana   
 
 
 You should not do this Parent Project In order to import ears, parents should refer to the ear as a module in their palm, and within the parent a guide of the subdirectory Appearance. Maybe I  import . 
 The order to be declared in module palm is the order in which they are created, so the final module should be in the ear list because in it Jar 1, Jar 2 and Web module are in the form of dependencies. The second final module should be in the web list because it probably depends on jar1 or jar2 or both.  
 In M2Eclipse, a multi- Import module project structure The ability to run is described as separate projects within the workspace, by choosing this option prevents you from working on each individual module through the original project and extending all the way down the path. 
 It does not change the nested structure on the disk, it only presents each module as its own project, and the module directory is also visible in the original project. 
 It also allows each module to be made individually, or a complete creation can be done by building the original project.  
 Read about Maven Reactor.  
 I suggest that before you try a quick rootstick to deal with your main project, see  
 The Epiphase Archipelage of Matt Ribble is really a good example To create a skeleton structure, try the following commands:  
  mvn org.apache.maven.plugins: maven-archetype-plugin: 2.0: gener -DgroupId = com Test.archetest -DartifactId = archetest -DarchetypeArtifactId = appfuse-modular-jsf -DarchetypeGroupId = org.appfuse.archetypes   
 Take a look at the general project structure Take it, and then import it using M2 Eclipse will generate Eclipse project files. You can also do this via  mvn eclipse: eclipse , but this allows you to create separate modules in your workspace Some projects, the Eclipse chooses not to do project files, and instead it is generated from POM with the methods given above.  
 If you use the original formatting given above, then you will need to add an ear module to the parent project, this can be done through M2Eclipse.