On Wed, Sep 21, 2011 at 10:34, Aslak Knutsen <email@example.com> wrote:
Usecase for Only Container Extension is where Arquillian work as a
pure common integration layer between the different Containers, write
once deploy run anywhere. A Example here is Arquillian Maven, JBoss
Forge, JBoss Tools. Possible other use cases would be some
provisioning / deployment tool.
The current brand focus up til today has been on "Testing with
Containers" and that Arquillian is one thing. But reality is
Arquillian is becoming the umbrella project that "JBoss Testing Lab"
was suppose to be, and we're slowly moving outside the boundries of
the Testing realm with efforts like Arquillian Maven and Forge / Tools
integration. This is also why i've started to talk about Arquillian as
I would say, let's stick with one strong brand around this and point
out the different angles, instead of multiple smaller obscure brands
that happen to work together in random locations. It simplifies docs,
promotion, recognition, inter operability, consistency.