1:51 a.m.
Change number 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
1:53 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Dan Allen updated ARQ-200:
--------------------------
Summary: Change version scheme for containers (was: Change number scheme for
containers)
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
4:18 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-200:
-------------------------------
We also need to workout how to name the packages. For instance:
org.jboss.arquillian.container.jetty.embedded6_1.JettyEmbeddedContainer
or
org.jboss.arquillian.container.jetty.embedded_6_1.JettyEmbeddedContainer
?
I think we need the version in the package because the XML-based configuration namespaces
are based on packages.
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
9:15 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-200:
-----------------------------------
org.jboss.arquillian.container."name"."type"_"major"[_minor]
sounds good to me. make a clear seperation between name, type and version.
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
10:07 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
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/j...
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
2:27 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-200:
-----------------------------------
You missed ARQ-174 in your jetty naming.. :)
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
4:14 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-200:
-------------------------------
Ah. Actually, I just typed it wrong in the comment:
org.jboss.arquillian.container.jetty.embedded_6_1
Just to be sure:
http://anonsvn.jboss.org/repos/common/arquillian/trunk/containers/jetty-e...
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
11:30 a.m.
New subject: [JBoss JIRA] Updated: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen updated ARQ-200:
------------------------------
Fix Version/s: 1.0.0.Alpha3
Affects Version/s: 1.0.0.Alpha2
(was: 1.0.0.Alpha3)
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.Alpha2
Reporter: Dan Allen
Fix For: 1.0.0.Alpha3
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
8:26 p.m.
New subject: [JBoss JIRA] Assigned: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen reassigned ARQ-200:
---------------------------------
Assignee: Aslak Knutsen
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
8:30 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-200:
-----------------------------------
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
8:34 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-200 at 6/29/10 2:33 PM:
------------------------------------------------------------
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
container/folder:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
container/folder: jbossas-remote-6
type: embedded | managed | remote
was (Author: aslak):
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
8:34 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-200 at 6/29/10 2:34 PM:
------------------------------------------------------------
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
container/folder:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
type: embedded | managed | remote
was (Author: aslak):
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
container/folder:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
container/folder: jbossas-remote-6
type: embedded | managed | remote
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
8:36 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-200 at 6/29/10 2:34 PM:
------------------------------------------------------------
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
containers/ svn name:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
type: embedded | managed | remote
was (Author: aslak):
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
container/folder:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
type: embedded | managed | remote
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
8:36 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-200 at 6/29/10 2:36 PM:
------------------------------------------------------------
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
containers/ svn name:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
type= embedded | managed | remote
version= earlies working version and working up to next container version of same type
was (Author: aslak):
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
containers/ svn name:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
type: embedded | managed | remote
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
8:38 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-200 at 6/29/10 2:37 PM:
------------------------------------------------------------
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
containers/ svn name:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-5.1
package: org.jboss.arquillian.container.jbossas.remote_5_1
containers/ svn name: jbossas-remote-5.1
type= embedded | managed | remote
version= earlies working version and working up to next container version of same type
was (Author: aslak):
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
containers/ svn name:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
type= embedded | managed | remote
version= earlies working version and working up to next container version of same type
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
8:42 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen edited comment on ARQ-200 at 6/29/10 2:41 PM:
------------------------------------------------------------
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
containers/ svn name:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-5.1
package: org.jboss.arquillian.container.jbossas.remote_5_1
containers/ svn name: jbossas-remote-5.1
type= embedded | managed | remote
version= earliest working version and working up to next container version of same type
was (Author: aslak):
Naming scheme
groupId: org.jboss.arquillian.container
artifactid:
arquillian-"name"-"type"-"major"[."minor"][."point"]
package:
org.jboss.arquillian.container."name"."type"_"major"[_"minor"][_"point"]
containers/ svn name:
"name"-"type"-"major"[."minor"][."point"]
Example
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-6
package: org.jboss.arquillian.container.jbossas.remote_6
containers/ svn name: jbossas-remote-6
groupId: org.jboss.arquillian.container
artifactid: arquillian-jbossas-remote-5.1
package: org.jboss.arquillian.container.jbossas.remote_5_1
containers/ svn name: jbossas-remote-5.1
type= embedded | managed | remote
version= earlies working version and working up to next container version of same type
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
11:23 a.m.
New subject: [JBoss JIRA] Resolved: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen resolved ARQ-200.
-------------------------------
Resolution: Done
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
2:10 a.m.
New subject: [JBoss JIRA] Closed: (ARQ-200) Change version scheme for containers
[
https://jira.jboss.org/browse/ARQ-200?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen closed ARQ-200.
-----------------------------
1.0.0.Alpha3 has been released. Closing all issues.
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.Alpha2
Reporter: Dan Allen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
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
5085
days inactive
5117
days old
arquillian-issues@lists.jboss.org
17 comments
2 participants
participants (2)
-
Aslak Knutsen (JIRA) -
Dan Allen (JIRA)