On 26 Nov 2009, at 16:05, Dan Allen wrote:
On Thu, Nov 26, 2009 at 10:45 AM, Aslak Knutsen
<aslak(a)conduct.no> wrote:
As of now, EmbeddedAS needs to point to a full Jboss 6.0 installation using ie
$JBOSS_HOME.
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.
Arquillian on the other hand does the whole shebang for you.. and then some..
http://www.jboss.org/community/docs/DOC-14376
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.
That's a great step. But what would really score with developers is if you can do:
mvn jbas:run
This is a slightly different use case from the one ALR has concentrated on to start with,
and tbh is something solely in the domain of tooling (e.g. maven plugin, ant task).
http://jira.codehaus.org/browse/MJBOSS-39
We should fill out what the various user-facing commands (like run etc.) should look like,
with either a description of their behavior, or links to similar plugins.