The issue refers to the container naming standards, which are defined in the arq ref guide, containers chapter.

Most important is that jboss as is written jbossas and not jboss or jboss-as.

I think the artifact pattern is

vendor-type-compatversion

ex.

jbossas-remote-6

For packages, it's

vendor.type_compatversion

ex.

jbossas.remote_6

The version should mirror the version Arquillian defines. The version is the min container version that is compatible. For instance, 6 covers 6.0.0 and 6.1.0. If we had a jbossas-remote-6.2 it would mean you need this adapter if you are on 6.2 or higher.

In other words, we introduce a new adapter version when the existing adapter no longer works with the newer version of the container.

Let's make sure we link the arq plugin refguide to the relevant section in the arq refguide, as it pertains to this topic.

- Dan Allen

Sent from my Android-powered phone:
An open platform for carriers, consumers and developers

On Sep 10, 2011 10:33 AM, "Aslak Knutsen" <aslak@4fs.no> wrote:
> which naming standards are you refering to ?
>
> -aslak-
>
> On Sat, Sep 10, 2011 at 12:14 AM, Lincoln Baxter, III
> <lincolnbaxter@gmail.com> wrote:
>> Hey Aslak,
>>
>> Do you know where we can find these naming standards? I put this in here
>> because of something Dan or Andrew mentioned to me. Thanks!
>>
>> https://issues.jboss.org/browse/SEAMFORGE-153
>>
>>
>>
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.com
>> http://scrumshark.com
>> "Keep it Simple"
>>