[arquillian-issues] [JBoss JIRA] Commented: (ARQ-200) Change version scheme for containers

[Dan Allen (JIRA)]

    [ https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12537248#action_12537248 ] 

Dan Allen commented on ARQ-200:
-------------------------------

Excellent. I updated the package for the Jetty Embedded 6.1.x container to be:

org.jboss.arquillian.jetty.embedded_6_1

So I'm happy with the package scheme.

I'd like to make a different proposal for the artifactId scheme (sorry to flip-flop on this, but it's important to get this right). I think we should use a dots in the container version number, with the version offset by either an underscore or a hyphen.

Instead of:

jbossas-remote-5_1 (producing an artifact named arquillian-jbossas-remote-5_1-1.0.0.Alpha3.jar)
jetty-embedded_6_1

I propose either:

jbossas-remote-5.1 (producing an artifact named arquillian-jbossas-remote-5.1-1.0.0.Alpha3.jar)
jetty-embedded-6.1

or

jbossas-remote_5.1 (producing an artifact named arquillian-jbossas-remote_5.1-1.0.0.Alpha3.jar)
jetty-embedded_6.1

The underscore is consistent with how the JBoss spec POMs are named [1]. However, I personally think that adding an underscore makes it hard to remember. So I prefer using the hyphen to offset the version number.

[1] https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/javax/

> Change version scheme for containers
> ------------------------------------
>
>                 Key: ARQ-200
>                 URL: https://jira.jboss.org/browse/ARQ-200
>             Project: Arquillian
>          Issue Type: Task
>          Components: GlassFish Containers, JBoss Containers, OpenEJB Containers, OpenWebBeans Containers, Weld Containers
>    Affects Versions: 1.0.0.Alpha3
>            Reporter: Dan Allen
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira