July 2010 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-204) GlassFish remote container expose GlassFish dependencies

by Aslak Knutsen (JIRA)

GlassFish remote container expose GlassFish dependencies -------------------------------------------------------- Key: ARQ-204 URL: https://jira.jboss.org/browse/ARQ-204 Project: Arquillian Issue Type: Bug Components: GlassFish Containers Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Alpha3 Containers should not expose a specific v. of a lib to the user. The user should be in control of the classpath. -- 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-188) Support for embedded and remote OSGi bundle testing

by Thomas Diesler (JIRA)

Support for embedded and remote OSGi bundle testing --------------------------------------------------- Key: ARQ-188 URL: https://jira.jboss.org/browse/ARQ-188 Project: Arquillian Issue Type: Feature Request Reporter: Thomas Diesler -- 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

13 years, 11 months

2
5
0 / 0

[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

13 years, 11 months

2
17
0 / 0

[JBoss JIRA] Created: (ARQ-159) Container Reference for JBoss AS Local 5.1 and 60 points to remote container in maven setup example

by Aslak Knutsen (JIRA)

Container Reference for JBoss AS Local 5.1 and 60 points to remote container in maven setup example --------------------------------------------------------------------------------------------------- Key: ARQ-159 URL: https://jira.jboss.org/browse/ARQ-159 Project: Arquillian Issue Type: Bug Components: Documentation Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Aslak Knutsen -- 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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-203) ThreadLocal leak during TestExecution

by Aslak Knutsen (JIRA)

ThreadLocal leak during TestExecution ------------------------------------- Key: ARQ-203 URL: https://jira.jboss.org/browse/ARQ-203 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha1 Reporter: Aslak Knutsen Fix For: 1.0.0.Alpha3 Arquillian leaks state on ThreadLocal variables. Every ThreadLocal variable should be cleaned up after use. Not doing so will cause memory issues in the container not being able to clean up ClassLoaders etc properly. JUnit: - Arquillian.caughtTestException - Arquillian.lastCreatedRunner - Arquillian.deployableTest TestNG - Arquillian.deployableTest -- 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

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-147) Add support for performance check on methods

by St?le Pedersen (JIRA)

Add support for performance check on methods -------------------------------------------- Key: ARQ-147 URL: https://jira.jboss.org/browse/ARQ-147 Project: Arquillian Issue Type: Feature Request Components: Extension - Performance Reporter: St?le Pedersen Assignee: St?le Pedersen First supported feature is the ability to set the maximum time a test method can take before an exception will be thrown. -- 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

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-182) Should be able to restart Container between N number of deployments

by Aslak Knutsen (JIRA)

Should be able to restart Container between N number of deployments ------------------------------------------------------------------- Key: ARQ-182 URL: https://jira.jboss.org/browse/ARQ-182 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Assignee: Aslak Knutsen It should be possible to configure Arquillian to force a container restart during the test run. This will clean up memory and resources. Create a Handler that restarts the Container pr N number of Deployments. -- 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

13 years, 11 months

1
2
0 / 0

[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

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-169) XmlConfiguration should use setter methods to assign configuration properties

by Dan Allen (JIRA)

XmlConfiguration should use setter methods to assign configuration properties ------------------------------------------------------------------------------ Key: ARQ-169 URL: https://jira.jboss.org/browse/ARQ-169 Project: Arquillian Issue Type: Bug Components: Configuration Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen Attachments: ARQ-169-patch.txt Currently, XmlConfiguration is using the method Class#getDeclaredField(String) to find the field that matches the configuration property. For one, this breaks if the field is inherited from a base class. But rather than scanning through the inheritance hierarchy, XmlConfiguration should be looking for a public setter field that corresponds to the property name. For example: httpPort --> setHttpPort() -- 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

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-209) Apply naming scheme to Protocols

by Aslak Knutsen (JIRA)

Apply naming scheme to Protocols -------------------------------- Key: ARQ-209 URL: https://jira.jboss.org/browse/ARQ-209 Project: Arquillian Issue Type: Feature Request Components: Test Protocol SPIs and Implementation Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen Fix For: 1.0.0.Alpha3 Protocols should use the version as part of their name like the Containers do. servlet_2_5 servlet_3 -- 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

13 years, 11 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2010