title: Maven GroupID and ArtifactID for J2EE Utility Project
body: <p>I have a collection of 3 existing Eclipse projects that I want to make into Maven projects and I'm having a hard time understanding the relationship between the GroupID, ArtifactID and my Java Packaging, and the different directory structure that is created for Maven vs. Java projects. I'm pretty new to J2EE and completely new to Maven, so any advice is welcome! Let me describe my projects first.</p>
  
  <p>The first project is IDMU_JAR. The base Java packaging is com.foo.util.merge and it contains Java classes like Template and Bookmark and the target jar file is com.foo.util.merge.jar </p>
  
  <p>The second project is IDUM_WAR. The base class in this project is com.foo.util.merge.web and it references the IDMU_JAR project and contains only a few Servlets that expose the functionality in IDMU_JAR. </p>
  
  <p>The third project is IDMU_EAR. Currently this is just a device for creating a deployment EAR that contains IDMU_JAR, WAR and it's dependencies.</p>
  
  <p>My questions are: </p>
  
  <p>Is my J2EE packaging and naming "typical" or have I already gone against best practices?</p>
  
  <p>Am I better off creating the Maven Project and then converting it to a Faceted project and picking the facets, or should I be creating the Java Utility/WAR/EAR projects and then converting them to Maven projects? </p>
  
  <p>This appears to have a big impact on the directory structure of the project, is this important?.</p>
  
  <p>Does my Eclipse Project name have to match the Maven Artifact ID?</p>