PS -- This means use a parallel test package structure :) sorry, missed the point for a second!<br><br><div class="gmail_quote">On Thu, Apr 29, 2010 at 1:00 AM, Lincoln Baxter, III <span dir="ltr">&lt;<a href="mailto:lincolnbaxter@gmail.com">lincolnbaxter@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yeah, that&#39;s right. Maven ensures that classes under the src/main/test/ folder are never included in the final packaged build. So using a parallel package structure to src/main/java, for example, keeps things nice and separate :)<br>

<br>You can take a look at the Faces module for some more examples, but it looks like I18N is right on.<br><font color="#888888"><br>--Lincoln</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Wed, Apr 28, 2010 at 9:44 PM, Ken Finnigan <span dir="ltr">&lt;<a href="mailto:ken.finnigan@sorstech.com" target="_blank">ken.finnigan@sorstech.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">


  

<div bgcolor="#ffffff" text="#000000">
Lincoln,<br>
<br>
Great first cut on testing for modules.<br>
<br>
One question, one comment Pete made about some testing code I had
committed for the i18n module was that classes for tests should be in a
&quot;test&quot; package as opposed to being in the same package as the main
source.  Are we going with that approach or having test classes in the
same package but only under different source tree?<br>
<br>
Ken<div><div></div><div><br>
<br>
<br>
On 26/04/2010 18:57, Lincoln Baxter, III wrote:
</div></div><blockquote type="cite"><div><div></div><div><a href="http://seamframework.org/Seam3/ModuleHandbook" target="_blank">http://seamframework.org/Seam3/ModuleHandbook</a><br>
  <a href="http://seamframework.org/Seam3/ModuleTesting" target="_blank">http://seamframework.org/Seam3/ModuleTesting</a><br>
  <br>
This includes a few guidelines, plus step-by-step instructions for
getting started writing JUnit and Arquillian tests. Please review and
add/comment.<br>
  <br>
Thanks,<br clear="all">
  <br>
-- <br>
Lincoln Baxter, III<br>
  <a href="http://ocpsoft.com" target="_blank">http://ocpsoft.com</a><br>
  <a href="http://scrumshark.com" target="_blank">http://scrumshark.com</a><br>
&quot;Keep it Simple&quot;<br>
  </div></div><pre><fieldset></fieldset>
_______________________________________________
seam-dev mailing list
<div><a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a>
</div><div><a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a>
  </div></pre>
</blockquote>
</div>

</blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com" target="_blank">http://ocpsoft.com</a><br><a href="http://scrumshark.com" target="_blank">http://scrumshark.com</a><br>
&quot;Keep it Simple&quot;<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>&quot;Keep it Simple&quot;<br>