Status: Closed (View Workflow)
Affects Version/s: 1.0.0.Alpha2
Fix Version/s: 1.0.0.Alpha3
Affects:Documentation (Ref Guide, User Guide, etc.), Release Notes, Interactive Demo/Tutorial, Compatibility/Configuration
Container versions are currently identified by appending an abridged version number to the end of the container's groupId. Examples include:
Remote JBoss AS 6.0.0 == jbossas-remote-60
Remote JBoss AS 5.1.0 == jbossas-remote-51
Remote GlassFish 3.0 == glassfish-remote-30
Embedded Weld == weld-embedded
While these versions seem obvious now, as we accumulate more and more containers, it's going to become less clear how the abridged version numbers map to real version numbers.
I recommend that we match the real version number more closely by simply replacing dots (.) with underscores (_). We should also use the least specific version number and establish the convention that any Arquillian container version <= the target container version will work (i.e., we add a version when there is a breaking change in the API of the target container or we switch to a new management API).
Remote JBoss AS 6.0.0 == jbossas-remote-6
Remote JBoss AS 5.1.0 == jbossas-remote-5_1
Remote JBoss AS 5.0.0 == jbossas-remote-5
Remote GlassFish 3.0 == glassfish-remote-3
Remote GlassFish 3.1 == glassfish-remote-3_1
Embedded Weld == weld-embedded-1
An open question is whether the minor version should be included for the first major version of a container (e.g., jbossas-remote-6 or jbossas-remote-6_0)
This task requires renaming and repackaging most of the existing containers. We should do this as early as possibly, preferrably before 1.0.0.Alpha3.