title: Maven vs. Eclipse Project Facets for Java EE 6
body: <p>I have created Maven projects inside Eclipse with these archetypes:</p>
  
  <ul>
  <li>ejb-javaee6</li>
  <li>webapp-javaee6</li>
  </ul>
  
  <p>The projects were created without facets.</p>
  
  <p><strong>Does it make sense to convert such Maven projects into faceted form?</strong></p>
  
  <p><strong>Which facets would be helpful and which ones could cause trouble for a Maven project?</strong></p>
  
  <p>Specifically: Would any of the following project facets be in conflict with something that is in the responsibility of Maven?</p>
  
  <ul>
  <li>Java</li>
  <li>JavaScript</li>
  <li>EJB Module</li>
  <li>Dynamic Web Module</li>
  <li>GlassFish Deployment Descriptors Files</li>
  <li>JavaServer Faces</li>
  </ul>
  
  <p>I have the impression that converting a Maven project to faceted form would mean mixing two worlds. Therefore I tend to NOT enable ANY project facets.</p>
  
  <p>But where I work we have examples of Maven projects that are in faceted form and I was wondering whether there might be (risk-free) benefits to it.</p>