[seam-dev] seam-parent overhaul

[Shane Bryzak]

I've done some work to seam-parent already, removing weld-parent from 
the hierarchy, updating all the plugin versions and some general 
cleanup.  I have a bunch of questions though, if anyone can answer any 
of these it will save me a lot of time:

1) Do we require both junit and testng?

2) Do we use mockito?

3) We have a number of Weld dependencies: weld-api, weld-core, weld-se, 
weld-se-core, weld-servlet - where/how are these being used?

4) org.apache.openjpa:openjpa-all - what uses this?

5) org.hsqldb:hsqldb - do we use this?

6) org.subethamail:subethasmtp - where is this used?

7) com.sun.jersey:jersey-bundle and 
com.sun.jersey.contribs:jersey-multipart - what are these/where are they 
used?

8) Container-related:
     org.jboss.jbossas:jboss-server-manager
     org.jboss.jbossas:jboss-as-client
     org.mortbay.jetty:jetty
     org.mortbay.jetty:jsp-2.1-jetty
     org.mortbay.jetty:jetty-naming
     org.mortbay.jetty:jetty-plus
     org.eclipse.jetty:jetty-webapp
     org.eclipse.jetty:jetty-plus
     org.glassfish.deployment:deployment-client

     - Are these dependencies here purely for testing purposes?

9) There are two emma plugins - org.codehaus.mojo:emma-maven-plugin and 
org.sonatype.maven.plugin:emma4it-maven-plugin, do we need both?
    (actually, i think one is used for instrumentation, and one for 
reporting - can someone pls confirm this?)