February 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reopened ARQ-1071: -------------------------------- > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final > Reporter: Rick-Rainer Ludwig > Fix For: 1.0.4.Final > > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1651) No console logging with managed karaf container

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1651: ----------------------------------- Summary: No console logging with managed karaf container Key: ARQ-1651 URL: https://issues.jboss.org/browse/ARQ-1651 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1650?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on ARQ-1650: ------------------------------------- As a workaround you can add this to your arquillian.xml {code} <property name="javaVmArguments">-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=${tomcat.home}/conf/logging.properties</property> {code} > Managed container bypasses tomcat jul setup > ------------------------------------------- > > Key: ARQ-1650 > URL: https://issues.jboss.org/browse/ARQ-1650 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: tomcat_1.0.0.Final > > > This code from the catalina startup script is not done in the manged deployable container > {code} > # Set juli LogManager config file if it is present and an override has not been issued > if [ -z "$LOGGING_CONFIG" ]; then > if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then > LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" > else > # Bugzilla 45585 > LOGGING_CONFIG="-Dnop" > fi > fi > if [ -z "$LOGGING_MANAGER" ]; then > LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" > fi > {code} > As a result, tomcat logging does not work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1650?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated ARQ-1650: -------------------------------- Fix Version/s: tomcat_1.0.0.Final > Managed container bypasses tomcat jul setup > ------------------------------------------- > > Key: ARQ-1650 > URL: https://issues.jboss.org/browse/ARQ-1650 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: tomcat_1.0.0.Final > > > This code from the catalina startup script is not done in the manged deployable container > {code} > # Set juli LogManager config file if it is present and an override has not been issued > if [ -z "$LOGGING_CONFIG" ]; then > if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then > LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" > else > # Bugzilla 45585 > LOGGING_CONFIG="-Dnop" > fi > fi > if [ -z "$LOGGING_MANAGER" ]; then > LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" > fi > {code} > As a result, tomcat logging does not work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1650: ----------------------------------- Summary: Managed container bypasses tomcat jul setup Key: ARQ-1650 URL: https://issues.jboss.org/browse/ARQ-1650 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR5 Reporter: Thomas Diesler This code from the catalina startup script is not done in the manged deployable container {code} # Set juli LogManager config file if it is present and an override has not been issued if [ -z "$LOGGING_CONFIG" ]; then if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" else # Bugzilla 45585 LOGGING_CONFIG="-Dnop" fi fi if [ -z "$LOGGING_MANAGER" ]; then LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" fi {code} As a result, tomcat logging does not work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1650?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reassigned ARQ-1650: ----------------------------------- Assignee: Thomas Diesler > Managed container bypasses tomcat jul setup > ------------------------------------------- > > Key: ARQ-1650 > URL: https://issues.jboss.org/browse/ARQ-1650 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > This code from the catalina startup script is not done in the manged deployable container > {code} > # Set juli LogManager config file if it is present and an override has not been issued > if [ -z "$LOGGING_CONFIG" ]; then > if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then > LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" > else > # Bugzilla 45585 > LOGGING_CONFIG="-Dnop" > fi > fi > if [ -z "$LOGGING_MANAGER" ]; then > LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" > fi > {code} > As a result, tomcat logging does not work -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1649) FrameworkMBean.installBundle() uses URL to local maven repo

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1649: ----------------------------------- Summary: FrameworkMBean.installBundle() uses URL to local maven repo Key: ARQ-1649 URL: https://issues.jboss.org/browse/ARQ-1649 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: osgi_2.0.0.Final Auto install of the arquillian-bundle may fail on remote target containers. The target container is given an URL to the arquillian-bundle that may point to the client's local maven repo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1458) Arquilian tests failed with RuntileException Could not inject members

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1458?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1458. ------------------------------ > Arquilian tests failed with RuntileException Could not inject members > --------------------------------------------------------------------- > > Key: ARQ-1458 > URL: https://issues.jboss.org/browse/ARQ-1458 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.4.Final, 1.1.0.Final, 1.1.1.Final > Environment: Linux, JEE6, Embedded Glassfish 3.1.1, JPA, CDI, Arquilian 1.0.4 & Arquilian 1.1.0 > Reporter: Thomas Lallart > Fix For: 1.1.3.Final > > > When running more integration tests with Arquilian on Embedded Glassfish, some tests failed with message : > java.lang.RuntimeException: Could not inject members > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135) > at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78) > at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) > ... > Caused by: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001324 Argument bean must not be null > at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:744) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:138) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:872) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:884) > at org.jboss.weld.manager.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:120) > See also https://community.jboss.org/message/830718 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1608) Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1608?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1608. ------------------------------ > Invoke extensions related to AnnotationDeploymentScenarioGenerator in order of deployments > ------------------------------------------------------------------------------------------ > > Key: ARQ-1608 > URL: https://issues.jboss.org/browse/ARQ-1608 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Environment: Win7, Java 6 > Reporter: Robert Panzer > Fix For: 1.1.3.Final > > > Currently there is no order in which for example ProtocolArchiveProcessors are called in case a test class provides multiple deployments. > It would be nice if the extension related to the AnnotationDeploymentScenarioGenerator were called in the same order. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1648) Upgrade ShrinkWrap (Archive, Resolver, Descriptors)

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1648?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1648. ------------------------------ > Upgrade ShrinkWrap (Archive, Resolver, Descriptors) > --------------------------------------------------- > > Key: ARQ-1648 > URL: https://issues.jboss.org/browse/ARQ-1648 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Base Implementation > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.3.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 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 2014