<div class="gmail_quote">On Thu, Nov 26, 2009 at 10:45 AM, Aslak Knutsen <span dir="ltr"><<a href="mailto:aslak@conduct.no">aslak@conduct.no</a>></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;">
As of now, EmbeddedAS needs to point to a full Jboss 6.0 installation using ie $JBOSS_HOME.<div><br></div><div>What the "Automation via Maven" wiki explains is how to add a maven dependency so you don't have to pre-install a full jboss, maven will download and unpack it for you. But you still need to bootstap Embedded AS as a part of your test suite. As long as you do that, "mvn test" should work.</div>
<div><br></div><div>Arquillian on the other hand does the whole shebang for you.. and then some.. <a href="http://www.jboss.org/community/docs/DOC-14376" target="_blank">http://www.jboss.org/community/docs/DOC-14376</a></div>
</blockquote><div><br>Right, right. We were thinking along the same lines there. The point is, right now, the embedded AS is meant to be booted by a test in some way.<br><br>That's a great step. But what would really score with developers is if you can do:<br>
<br>mvn jbas:run<br><br>Note the change from jboss to jbas. Personally, I think we should consider (maybe a vote) using this new abbreviation to help distinguish JBoss from JBoss AS. Just throwing it out there. If not, "jboss:run" will do.<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>