[JBoss JIRA] Created: (ARQ-200) Change number scheme for containers
by Dan Allen (JIRA)
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
14 years, 5 months
[JBoss JIRA] Created: (ARQ-213) Export archive to unique file name
by Dan Allen (JIRA)
Export archive to unique file name
----------------------------------
Key: ARQ-213
URL: https://jira.jboss.org/browse/ARQ-213
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha2
Reporter: Dan Allen
Fix For: 1.0.0.Alpha3
Currently, the archive is written to a file in the export directory with the same name as the archive. However, many of the test archives are named "test.war". So when a suite is run, the only exported archive that remains is the last one exported.
Instead, the file should be prefixed with the full qualified test class name, which is customary for other files such as surefile results.
For example, if the test is com.acme.SampleTest and the archive is named test.war, the following file would be created in the export directory:
com.acme.SampleTest.test.war
--
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
14 years, 5 months