<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
After consultation with Aslak, it was agreed that a single testsuite
project was the best way to implement this, with separate profiles
used for each container. See
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://github.com/seam/solder/tree/develop/testsuite">https://github.com/seam/solder/tree/develop/testsuite</a>
as an example of the new structure. No action is required on this,
our QA team is taking care of updating all modules to the same
structure.<br>
<br>
On 18/10/11 11:57, John D. Ament wrote:
<blockquote
cite="mid:CAOqetn9FKT9CQp-NxZMqRfCbMKGqV_zQc4fv7h=OBifF5O3doA@mail.gmail.com"
type="cite">Folks,<br>
<br>
Was there another change in the test suite structure that I
missed? I went through a few emails, didn't see anything about it;
but it looks like we're back to a single test suite?<br>
<br>
John<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
seam-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>