February 2014 - arquillian-issues

[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 resolved ARQ-1648. -------------------------------- Resolution: Done > 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

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

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1648: ---------------------------------- Summary: 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

[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 resolved ARQ-1608. -------------------------------- Resolution: Done > 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-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 resolved ARQ-1458. -------------------------------- Resolution: Done > 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-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 updated ARQ-1458: ------------------------------- Fix Version/s: 1.1.3.Final > 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 updated ARQ-1608: ------------------------------- Fix Version/s: 1.1.3.Final > 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-1496) Add a Tomcat 8 embedded container

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1496?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1496. ------------------------------ > Add a Tomcat 8 embedded container > --------------------------------- > > Key: ARQ-1496 > URL: https://issues.jboss.org/browse/ARQ-1496 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: tomcat_1.0.0.CR6 > > > {{arquillian-tomcat-embedded-7}} is not compatible with Tomcat 8 due to {{org.apache.catalina.startup.HostConfig}} does not declare {{appBase()}} method anymore. It seems {{host.getAppBaseFile()}} should be used instead. -- 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-1456) Unable to authenticate to Tomcat 7 - illegal characters in header

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1456?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1456. ------------------------------ > Unable to authenticate to Tomcat 7 - illegal characters in header > ----------------------------------------------------------------- > > Key: ARQ-1456 > URL: https://issues.jboss.org/browse/ARQ-1456 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Martin Gencur > > I'm constantly getting the following exception when starting a managed Tomcat container (Tomcat 7): > {code} > java.lang.IllegalArgumentException: Illegal character(s) in message header value: Basic YWRtaW46YWRtaW4= > at sun.net.www.protocol.http.HttpURLConnection.checkMessageHeader(HttpURLConnection.java:482) > at sun.net.www.protocol.http.HttpURLConnection.isExternalMessageHeaderAllowed(HttpURLConnection.java:434) > at sun.net.www.protocol.http.HttpURLConnection.setRequestProperty(HttpURLConnection.java:2752) > at org.jboss.arquillian.container.tomcat.CommonTomcatManager.execute(CommonTomcatManager.java:214) > at org.jboss.arquillian.container.tomcat.CommonTomcatManager.list(CommonTomcatManager.java:116) > at org.jboss.arquillian.container.tomcat.CommonTomcatManager.isRunning(CommonTomcatManager.java:123) > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:85) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} > The configuration of the container in arquillian.xml looks like this: > {code} > <container qualifier="server1" default="true"> > <configuration> >  > <property name="jmxPort">8089</property> > <property name="bindHttpPort">8080</property> > <property name="catalinaHome">${tomcat.home}</property> > <property name="user">admin</property> > <property name="pass">admin</property> > </configuration> > </container> > {code} > and I indeed configured the right credentials in tomcat-users.xml: > {code} > <tomcat-users> > <role rolename="manager-script"/> > <user username="admin" password="admin" roles="manager-script"/> > </tomcat-users> > {code} > It does not matter which username or password I use as long as they're the same in arquillian.xml and tomcat-users.xml > I found a similar problem and possible solution at https://forums.oracle.com/thread/2200463?start=0&tstart=0 -- 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-1496) Add a Tomcat 8 embedded container

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1496?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1496: ------------------------------- Fix Version/s: tomcat_1.0.0.CR6 (was: tomcat_1.0.0.Final) > Add a Tomcat 8 embedded container > --------------------------------- > > Key: ARQ-1496 > URL: https://issues.jboss.org/browse/ARQ-1496 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: tomcat_1.0.0.CR6 > > > {{arquillian-tomcat-embedded-7}} is not compatible with Tomcat 8 due to {{org.apache.catalina.startup.HostConfig}} does not declare {{appBase()}} method anymore. It seems {{host.getAppBaseFile()}} should be used instead. -- 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-1647) Allow Executor to set process exit code

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1647?page=com.atlassian.jira.plugin.s... ] Karel Piwko commented on ARQ-1647: ---------------------------------- INFO: Latest commit in aerogear/openshift-origin-cartridge-aerogear-push branch master was a2e343d1a287c794375972db912f9757d84dc8c8 (rhc):Application 'footest' not found. (rhc): Exception in thread "main" org.arquillian.spacelift.process.ProcessExecutionException: Invocation of [Ljava.lang.String;@83754a8 failed with 101 at org.arquillian.spacelift.process.impl.ProcessExecutorImpl.execute(ProcessExecutorImpl.java:154) at org.arquillian.spacelift.process.impl.ProcessExecutorImpl.execute(ProcessExecutorImpl.java:216) at com.redhat.jboss.mobile.cli.AppCartridgeCreateCommand.run(AppCartridgeCreateCommand.java:61) at com.redhat.jboss.mobile.cli.PerfTestEnvCli.main(PerfTestEnvCli.java:16) {code} > Allow Executor to set process exit code > --------------------------------------- > > Key: ARQ-1647 > URL: https://issues.jboss.org/browse/ARQ-1647 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > > Currently, it is not possible to setup exit code for external process. This makes handling of execution failure quite complicated. > Figure out what API should be used to let user define allowed exit values. 0 is to be kept as default value. Additionally, there might be multiple values to be set. -- 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