On Wed, Aug 10, 2011 at 15:01, Ken Finnigan <span dir="ltr">&lt;<a href="mailto:ken@kenfinnigan.me">ken@kenfinnigan.me</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Shane,<br><br>Jason&#39;s correct, the main extrapolation point at the moment is pulling the container-boms I&#39;ve created into a location that all modules can use, and expanding them to include the ones that Dan has put together.<br>

</blockquote><div><br></div><div>Good. I gave a stab at the container-boms idea in the Arquillian showcase to prototype this for Seam. Maven is very unfriendly to this idea (I should blog what I wrote to Aslak about this), but it&#39;s at least manageable.</div>

<div><br></div><div>I do have one question. Can the tests still be run in the IDE without any commandline build step. I think that&#39;s essential for maximizing the friendliness of the Arquillian environment. That&#39;s one of the biggest complaints I had about Solder. It was doing some really strange stuff to pull in the final artifact JAR, which lengthened the testing cycle. Arquillian should be edit-save-test. If that&#39;s preserved already, excellent.</div>

<div><br></div><div>-Dan</div><div><br></div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>

<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>