<br><br><div class="gmail_quote">On Wed, Aug 17, 2011 at 8:56 PM, Jason Porter <span dir="ltr"><<a href="mailto:lightguard.jp@gmail.com">lightguard.jp@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
Sent from my iPhone<br>
<div class="im"><br>
On Aug 17, 2011, at 18:46, Shane Bryzak <<a href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>> wrote:<br>
<br>
> I've done some work to seam-parent already, removing weld-parent from<br>
> the hierarchy, updating all the plugin versions and some general<br>
> cleanup. I have a bunch of questions though, if anyone can answer any<br>
> of these it will save me a lot of time:<br>
><br>
> 1) Do we require both junit and testng?<br>
<br>
</div>I think most are using JUnit. I found ftests that use testng though.<br>
<div class="im"><br>
> 2) Do we use mockito?<br>
<br>
</div>Not yet, don't think, but a good idea for quick testing in api or impl<br>
<div class="im"><br>
> 3) We have a number of Weld dependencies: weld-api, weld-core, weld-se,<br>
> weld-se-core, weld-servlet - where/how are these being used?<br>
<br>
</div>Got me on that one.<br></blockquote><div><br>weld-core is used by weld-ee-embedded container. I would imagine that weld-se-core would be used by weld-se-embedded container, possibly others<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
> 4) org.apache.openjpa:openjpa-all - what uses this?<br>
<br>
</div>Persistence testing with another provider?<br>
<div class="im"><br>
> 5) org.hsqldb:hsqldb - do we use this?<br>
<br>
</div>Again, perhaps persistence does<br>
<div class="im"><br>
> 6) org.subethamail:subethasmtp - where is this used?<br>
<br>
</div>Cody answered that<br>
<div class="im"><br>
> 7) com.sun.jersey:jersey-bundle and<br>
> com.sun.jersey.contribs:jersey-multipart - what are these/where are they<br>
> used?<br>
<br>
</div>Glassfish testing with the remote 3.1 client<br>
<div class="im"><br>
> 8) Container-related:<br>
> org.jboss.jbossas:jboss-server-manager<br>
> org.jboss.jbossas:jboss-as-client<br>
> org.mortbay.jetty:jetty<br>
> org.mortbay.jetty:jsp-2.1-jetty<br>
> org.mortbay.jetty:jetty-naming<br>
> org.mortbay.jetty:jetty-plus<br>
> org.eclipse.jetty:jetty-webapp<br>
> org.eclipse.jetty:jetty-plus<br>
> org.glassfish.deployment:deployment-client<br>
><br>
> - Are these dependencies here purely for testing purposes?<br>
<br>
</div>I would assume that's the case<br>
<div class="im"><br>
> 9) There are two emma plugins - org.codehaus.mojo:emma-maven-plugin and<br>
> org.sonatype.maven.plugin:emma4it-maven-plugin, do we need both?<br>
> (actually, i think one is used for instrumentation, and one for<br>
> reporting - can someone pls confirm this?)<br>
<br>
</div>Maybe we should look into the arquillian jocono (sp?) stuff instead.<br></blockquote><div><br>I believe they are used as you describe Shane, but with the new testsuite setup, I haven't confirmed whether their use within the modules works as it used to, code coverage falls into that category as well. Definitely worth looking at jocono. <br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5"><br>
><br>
> _______________________________________________<br>
> seam-dev mailing list<br>
> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br>