February 2015 - arquillian-issues

[JBoss JIRA] (ARQ-1915) ShrinkWrap Descriptors upgrade 2.0.0-alpha-7

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1915: ---------------------------------- Summary: ShrinkWrap Descriptors upgrade 2.0.0-alpha-7 Key: ARQ-1915 URL: https://issues.jboss.org/browse/ARQ-1915 Project: Arquillian Issue Type: Enhancement Components: Base Implementation Affects Versions: 1.1.6.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.7.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1880) Arquillian core relies on TCCL to load infra

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1880?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1880. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/f0036995df93e0464aa0... > Arquillian core relies on TCCL to load infra > -------------------------------------------- > > Key: ARQ-1880 > URL: https://issues.jboss.org/browse/ARQ-1880 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.2.Final > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 1.1.7.Final > > > While testing FSW product stuff it turns out that test code is executed with a TCCL from the ARQ bundle. If ARQ does not set a TCCL we get > {code} > Caused by: java.lang.ClassNotFoundException: org/jboss/arquillian/test/impl/EventTestRunnerAdaptor > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:105) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:97) > at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.osgi.JUnitBundleTestRunner.execute(JUnitBundleTestRunner.java:34) > {code} > Having a TCCL set is highly problematic in OSGi because it bypasses al user defined wiring rules. When test code calls into API that uses TCCL, that API will try to load types from the ARQ Bundle classloader, which of course has no visibility to the requested types/resources. > The ARQ infra should ideally not have to depend on TCCL for loading its own types. Second best would be to reset the TCCL after all infra stuff is done and before the call into the test case. > The TCCL association is part of the public API. From the perspective of the test case, it needs to be defined and ideally be guaranteed to be null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1818) JUnit @Before/After phase is called after/before Arquillian's Before/After phase

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1818?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1818. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/606b4b29a3a561bc0ea6... > JUnit @Before/After phase is called after/before Arquillian's Before/After phase > -------------------------------------------------------------------------------- > > Key: ARQ-1818 > URL: https://issues.jboss.org/browse/ARQ-1818 > Project: Arquillian > Issue Type: Bug > Components: Test Harness Integration > Affects Versions: 1.1.5.Final, 1.1.6.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Priority: Blocker > Fix For: 1.1.7.Final > > > In < 1.1.5.Final JUnit's @Before and @After was called by Arquillian as part of Arquillian's Before and After phases. This changed by accident during the JUnit Rule support rewrite and @Before is now called after Arquillian's Before and @After phase is now called Before Arquillian's After. > This break down APIs like Deployer/ContainerController as non of the Suite/Class/Test Contexts are active at that point. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1880) Arquillian core relies on TCCL to load infra

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1880?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1880: ------------------------------- Fix Version/s: 1.1.7.Final > Arquillian core relies on TCCL to load infra > -------------------------------------------- > > Key: ARQ-1880 > URL: https://issues.jboss.org/browse/ARQ-1880 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.2.Final > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 1.1.7.Final > > > While testing FSW product stuff it turns out that test code is executed with a TCCL from the ARQ bundle. If ARQ does not set a TCCL we get > {code} > Caused by: java.lang.ClassNotFoundException: org/jboss/arquillian/test/impl/EventTestRunnerAdaptor > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:105) > at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:97) > at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.osgi.JUnitBundleTestRunner.execute(JUnitBundleTestRunner.java:34) > {code} > Having a TCCL set is highly problematic in OSGi because it bypasses al user defined wiring rules. When test code calls into API that uses TCCL, that API will try to load types from the ARQ Bundle classloader, which of course has no visibility to the requested types/resources. > The ARQ infra should ideally not have to depend on TCCL for loading its own types. Second best would be to reset the TCCL after all infra stuff is done and before the call into the test case. > The TCCL association is part of the public API. From the perspective of the test case, it needs to be defined and ideally be guaranteed to be null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1787) Move tests to separate maven module

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1787?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated ARQ-1787: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Done > Move tests to separate maven module > ----------------------------------- > > Key: ARQ-1787 > URL: https://issues.jboss.org/browse/ARQ-1787 > Project: Arquillian > Issue Type: Enhancement > Components: OSGi Containers > Reporter: Stefan Bunciak > Assignee: Thomas Diesler > > Move tests to separate maven module, so that all container adapter share the same set of tests. Container-specific tests can still reside with the container adapter implementation -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1870) Method KarafRemoteContainerConfiguration.validate() does not call super method

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1870?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated ARQ-1870: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Done > Method KarafRemoteContainerConfiguration.validate() does not call super method > ------------------------------------------------------------------------------ > > Key: ARQ-1870 > URL: https://issues.jboss.org/browse/ARQ-1870 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Method {{KarafRemoteContainerConfiguration.validate()}} does not call super method. > Neither {{JMXContainerConfiguration.validate()}} nor {{CommonContainerConfiguration.validate()}} is called. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1856) Remove dynamic import from arquillian-bundle

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1856?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated ARQ-1856: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Done > Remove dynamic import from arquillian-bundle > -------------------------------------------- > > Key: ARQ-1856 > URL: https://issues.jboss.org/browse/ARQ-1856 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: osgi_2.0.0.Final > > > Currently, the arquillian bundle contains a dynamic import "*" which may lead to undesired package wiring. Theoretically, it should possible to embed all required dependencies in the arq-bundle and load the test classes from the test-bundle(s) via Bundle.loadClass(...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1881) Fix starting/stopping of remote karaf container

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1881?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated ARQ-1881: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Done > Fix starting/stopping of remote karaf container > ----------------------------------------------- > > Key: ARQ-1881 > URL: https://issues.jboss.org/browse/ARQ-1881 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Martin Basovnik > Assignee: Thomas Diesler > > Conditions to start and stop remote karaf container are not properly set. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1914) Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1)

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1914?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1914: ------------------------------------ You choose GlassFish Embedded 3.1.1 https://gist.github.com/anonymous/0a476761c8de1bab0d8d#file-pom-xml-L121 > Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1) > ---------------------------------------------------------------------- > > Key: ARQ-1914 > URL: https://issues.jboss.org/browse/ARQ-1914 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: 1.1.6.Final > Reporter: Constantin Weißer > > The arquillian glassfish embedded container (in the newest version 1.0.0.CR4) does simply ignore @Convert annotations (JPA 2.1) which leads to errors when running tests that use the persistence layer. > The error output contains > Internal Exception: Exception [EclipseLink-7155] (Eclipse Persistence Services - 2.2.0.v20110202-r8913) > which would explain, why it does not work. JPA 2.1 features are not implemented in EclipseLink 2.2.0. Why does arquillian-glassfish-embedded use such an outdated version of the persistence service? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1914) Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1)

by Constantin Weißer (JIRA)

[ https://issues.jboss.org/browse/ARQ-1914?page=com.atlassian.jira.plugin.s... ] Constantin Weißer commented on ARQ-1914: ---------------------------------------- That's my poml.xml: https://gist.github.com/anonymous/0a476761c8de1bab0d8d > Arquillian embedded tests do not support @Convert/@Converter (JPA 2.1) > ---------------------------------------------------------------------- > > Key: ARQ-1914 > URL: https://issues.jboss.org/browse/ARQ-1914 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: 1.1.6.Final > Reporter: Constantin Weißer > > The arquillian glassfish embedded container (in the newest version 1.0.0.CR4) does simply ignore @Convert annotations (JPA 2.1) which leads to errors when running tests that use the persistence layer. > The error output contains > Internal Exception: Exception [EclipseLink-7155] (Eclipse Persistence Services - 2.2.0.v20110202-r8913) > which would explain, why it does not work. JPA 2.1 features are not implemented in EclipseLink 2.2.0. Why does arquillian-glassfish-embedded use such an outdated version of the persistence service? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2015