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?) _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Sent from my iPhone On Aug 17, 2011, at 18:46, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: > 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? I think most are using JUnit. I found ftests that use testng though. > 2) Do we use mockito? Not yet, don't think, but a good idea for quick testing in api or impl > 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? Got me on that one.

> 4) org.apache.openjpa:openjpa-all - what uses this? Persistence testing with another provider? > 5) org.hsqldb:hsqldb - do we use this? Again, perhaps persistence does > 6) org.subethamail:subethasmtp - where is this used? Cody answered that > 7) com.sun.jersey:jersey-bundle and > com.sun.jersey.contribs:jersey-multipart - what are these/where are they > used? Glassfish testing with the remote 3.1 client > 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? I would assume that's the case > 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?) Maybe we should look into the arquillian jocono (sp?) stuff instead.

> > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Is that the only place it's used? If so, it should probably go into seam-bom. On 18/08/11 10:48, Cody Lerum wrote: > 6. Is used in mail > > On Wed, Aug 17, 2011 at 6:46 PM, Shane Bryzak&lt;sbryzak(a)redhat.com&gt; wrote: >> 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?) >> >> >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >> _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Is that the only place it's used? If so, it should probably go into seam-bom.

On Wed, Aug 17, 2011 at 20:56, Jason Porter <lightguard.jp(a)gmail.com&gt;wrote: > On Aug 17, 2011, at 18:46, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: > > > 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? > > I think most are using JUnit. I found ftests that use testng though. > That will go away when we switch to Arquillian Drone. The precursor to Drone was bound to (or worked more comfortably) with testng. That's not the case any longer. JUnit is a much better choice with Arquillian, atm. The intention is to have an equal experience with both, but we are still facing some SPI challenges w/ TestNG. Sadly, that knocks out groups. However, we have plans to put a filtering feature at a higher level, in Arquillian itself.

-Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://www.google.com/profiles/dan.j.allen#about http://mojavelinux.com http://mojavelinux.com/seaminaction