From issues at jboss.org Thu Nov 3 11:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 3 Nov 2016 11:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2029) Tell us the HTTP method in debug mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2029. ------------------------------- > Tell us the HTTP method in debug mode > ------------------------------------- > > Key: ARQ-2029 > URL: https://issues.jboss.org/browse/ARQ-2029 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Reporter: Christian Schulz > Assignee: Christian Schulz > Fix For: warp_1.0.0.Alpha8 > > > Prints parallel to requestUri the method. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 11:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 3 Nov 2016 11:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2014) When warp is on classpath then almost every non-warp arquillian test fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2014. ------------------------------- > When warp is on classpath then almost every non-warp arquillian test fails > -------------------------------------------------------------------------- > > Key: ARQ-2014 > URL: https://issues.jboss.org/browse/ARQ-2014 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Alpha8 > > > Consider a test suite that contains a warp test (so you need to have the warp dependency on your classpath) and some other non-warp arquillian test. Then the non-warp tests fails with various exceptions depending on the type of the test. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 11:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 3 Nov 2016 11:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2013) Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2013. ------------------------------- > Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version > --------------------------------------------------------------------- > > Key: ARQ-2013 > URL: https://issues.jboss.org/browse/ARQ-2013 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Alpha8 > > > Please update to newer versions to use the latest and greatest implementations. > In case of JaCoCo - the current version {{0.6.0.201210061924}} is not compatible with JDK8 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 11:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 3 Nov 2016 11:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1923) Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1923. ------------------------------- > Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8 > --------------------------------------------- > > Key: ARQ-1923 > URL: https://issues.jboss.org/browse/ARQ-1923 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Pavol Pitonak > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Alpha8 > > > # git clone https://github.com/arquillian/arquillian-extension-warp.git > # mvn clean install > result: > * when launched with OpenJDK 8, one test fails TestExecutedMethod.testSerializedAnnotation > {code} > java.lang.IllegalStateException: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:61) > at org.jboss.arquillian.warp.impl.shared.TestExecutedMethod.testSerializedAnnotation(TestExecutedMethod.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > Caused by: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:83) > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:59) > ... 24 more > Caused by: java.lang.IllegalAccessException: Class org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider can not access a member of class org.jboss.arquillian.warp.impl.shared.$Proxy5 with modifiers "public" > at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:101) > at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:295) > at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:287) > at java.lang.reflect.Constructor.newInstance(Constructor.java:398) > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:76) > ... 25 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 11:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 3 Nov 2016 11:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1988) Warp HTTPCore 4.3 dependency conflict with latest Drone Alpha5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1988. ------------------------------- > Warp HTTPCore 4.3 dependency conflict with latest Drone Alpha5 > -------------------------------------------------------------- > > Key: ARQ-1988 > URL: https://issues.jboss.org/browse/ARQ-1988 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: warp_1.0.0.Alpha8 > > > Warp needs to upgrade to HTTPCore 4.4.3 to be compatible with Drone 2.0.0.Alpha5 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 11:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 3 Nov 2016 11:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1237) Warp: use PortProber to determine free ports for proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1237. ------------------------------- > Warp: use PortProber to determine free ports for proxy > ------------------------------------------------------ > > Key: ARQ-1237 > URL: https://issues.jboss.org/browse/ARQ-1237 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Christian Schulz > Priority: Minor > Fix For: warp_1.0.0.Alpha8 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Selenium 2 uses {{PortProber}} to check free ports to run Selenium Server on. > We can leverage that component too for Warp proxy and avoid conflicting ports. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 3 11:01:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 3 Nov 2016 11:01:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1272) Warp: avoid need for user-defined serialVersionUID In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1272. ------------------------------- > Warp: avoid need for user-defined serialVersionUID > -------------------------------------------------- > > Key: ARQ-1272 > URL: https://issues.jboss.org/browse/ARQ-1272 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha8 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > One of the options might be to generate serialVersionUID with Lombok: > http://projectlombok.org/mavenrepo/index.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 4 08:28:00 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Fri, 4 Nov 2016 08:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2052) Profiles in arquillian.xml In-Reply-To: References: Message-ID: Rafael Garcia created ARQ-2052: ---------------------------------- Summary: Profiles in arquillian.xml Key: ARQ-2052 URL: https://issues.jboss.org/browse/ARQ-2052 Project: Arquillian Issue Type: Feature Request Components: Configuration Environment: Hi, Could It set the arquillian.xml file for different environments or profiles?? For example: ${jira.username} ${jira.password} ${jira.url} Before file .properties # JIRA PROPERTIES jira.url=http://XXXXX:8080 jira.username=XXXXX jira.password=XXXXX Reporter: Rafael Garcia Priority: Minor -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 4 08:30:01 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Fri, 4 Nov 2016 08:30:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2052) Profiles in arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Garcia updated ARQ-2052: ------------------------------- Description: Hi, Could It set the *arquillian.xml* file for different environments or profiles?? For example: ${jira.username} ${jira.password} ${jira.url} Before file .properties *# JIRA PROPERTIES* jira.url=http://XXXXX:8080 jira.username=XXXXX jira.password=XXXXX > Profiles in arquillian.xml > -------------------------- > > Key: ARQ-2052 > URL: https://issues.jboss.org/browse/ARQ-2052 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: Hi, > Could It set the arquillian.xml file for different environments or profiles?? > For example: > ${jira.username} > ${jira.password} > ${jira.url} > Before file .properties > # JIRA PROPERTIES > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX > Reporter: Rafael Garcia > Priority: Minor > > Hi, > Could It set the *arquillian.xml* file for different environments or profiles?? > For example: > ${jira.username} > ${jira.password} > ${jira.url} > Before file .properties > *# JIRA PROPERTIES* > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 4 08:33:00 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Fri, 4 Nov 2016 08:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2052) Profiles in arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Garcia updated ARQ-2052: ------------------------------- Description: Hi, Could It set the *arquillian.xml* file for different environments or profiles?? For example: {code:java} ${jira.username} ${jira.password} ${jira.url} {code} On the other hand, we have a properties file with: {code:java} # JIRA PROPERTIES jira.url=http://XXXXX:8080 jira.username=XXXXX jira.password=XXXXX {code} was: Hi, Could It set the *arquillian.xml* file for different environments or profiles?? For example: ${jira.username} ${jira.password} ${jira.url} Before file .properties *# JIRA PROPERTIES* jira.url=http://XXXXX:8080 jira.username=XXXXX jira.password=XXXXX > Profiles in arquillian.xml > -------------------------- > > Key: ARQ-2052 > URL: https://issues.jboss.org/browse/ARQ-2052 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: Hi, > Could It set the arquillian.xml file for different environments or profiles?? > For example: > ${jira.username} > ${jira.password} > ${jira.url} > Before file .properties > # JIRA PROPERTIES > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX > Reporter: Rafael Garcia > Priority: Minor > > Hi, > Could It set the *arquillian.xml* file for different environments or profiles?? > For example: > {code:java} > ${jira.username} > ${jira.password} > ${jira.url} > {code} > On the other hand, we have a properties file with: > {code:java} > # JIRA PROPERTIES > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 4 08:34:00 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Fri, 4 Nov 2016 08:34:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2052) Profiles in arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Garcia updated ARQ-2052: ------------------------------- Environment: Development (was: Hi, Could It set the arquillian.xml file for different environments or profiles?? For example: ${jira.username} ${jira.password} ${jira.url} Before file .properties # JIRA PROPERTIES jira.url=http://XXXXX:8080 jira.username=XXXXX jira.password=XXXXX) > Profiles in arquillian.xml > -------------------------- > > Key: ARQ-2052 > URL: https://issues.jboss.org/browse/ARQ-2052 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: Development > Reporter: Rafael Garcia > Priority: Minor > > Hi, > Could It set the *arquillian.xml* file for different environments or profiles?? > For example: > {code:java} > ${jira.username} > ${jira.password} > ${jira.url} > {code} > On the other hand, we have a properties file with: > {code:java} > # JIRA PROPERTIES > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 4 10:28:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 4 Nov 2016 10:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2052) Profiles in arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13317561#comment-13317561 ] Matous Jobanek commented on ARQ-2052: ------------------------------------- Hi, you can have several arquillian.xml files and invoke them either using the parameter {{-Darquillian.xml=/path/to/arquillian.xml}} or {{maven-surefire-plugin}} configuration in several profiles: {code:xml} maven-surefire-plugin /path/to/arquillian.xml {code} In similar way, you can set the variables you are using in arquillian.xml file > Profiles in arquillian.xml > -------------------------- > > Key: ARQ-2052 > URL: https://issues.jboss.org/browse/ARQ-2052 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: Development > Reporter: Rafael Garcia > Priority: Minor > > Hi, > Could It set the *arquillian.xml* file for different environments or profiles?? > For example: > {code:java} > ${jira.username} > ${jira.password} > ${jira.url} > {code} > On the other hand, we have a properties file with: > {code:java} > # JIRA PROPERTIES > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 9 11:29:00 2016 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 9 Nov 2016 11:29:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2053) Allow Arquillian Core to define a way to execute registration of extensions in order In-Reply-To: References: Message-ID: Alex Soto created ARQ-2053: ------------------------------ Summary: Allow Arquillian Core to define a way to execute registration of extensions in order Key: ARQ-2053 URL: https://issues.jboss.org/browse/ARQ-2053 Project: Arquillian Issue Type: Bug Reporter: Alex Soto Priority: Minor With Arquillian Extensions you are able to override a service that was previously registered by Arquillian Core or by other extensions. The problem is that if if there two extensions that override the same service, it will depend on the order of the registration of the extension that will define which version of the service will be the one used at the end. To avoid this problem this problem the best way would be to be able to set a priority in extension registry so you can set which one is going to be the last one. The best none invasive approach we have found is using an annotation to set the order where the highest number is the last one to execute. In case of not defining a an annotation, the default order number will be 0. So as an example an extension could be defined as: {code:java} @Precendence(100) public class MyExtension implements LoadableExtension {} {code} The higher value of precedence the sooner it will be registered. This means that to ensure that your extension is registered last, it needs a negative value. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 10 09:27:00 2016 From: issues at jboss.org (Alex Soto (JIRA)) Date: Thu, 10 Nov 2016 09:27:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2053) Allow Arquillian Core to define a way to execute registration of extensions in order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2053: --------------------------- Description: With Arquillian Extensions you are able to override a service that was previously registered by Arquillian Core or by other extensions. The problem is that if if there two extensions that override the same service, it will depend on the order of the registration of the extension that will define which version of the service will be the one used at the end. To avoid this problem this problem the best way would be to be able to set a priority in extension registry so you can set which one is going to be the last one. The best none invasive approach we have found is by providing an SPI so any extension can vetoed any service /ResourceProvider/TestEnricher/... to be registered by an extension. This SPI is a file present at META-INF/services directory. The file is named with the service type you want to veto such as (`org.jboss.arquillian.test.spi.enricher.resource.ResourceProvider`) and inside all the implementations you want to veto each one in a new line. So before starting registering the extensions, the vetoed list will be loaded into service registry so they cannot be registered. was: With Arquillian Extensions you are able to override a service that was previously registered by Arquillian Core or by other extensions. The problem is that if if there two extensions that override the same service, it will depend on the order of the registration of the extension that will define which version of the service will be the one used at the end. To avoid this problem this problem the best way would be to be able to set a priority in extension registry so you can set which one is going to be the last one. The best none invasive approach we have found is using an annotation to set the order where the highest number is the last one to execute. In case of not defining a an annotation, the default order number will be 0. So as an example an extension could be defined as: {code:java} @Precendence(100) public class MyExtension implements LoadableExtension {} {code} The higher value of precedence the sooner it will be registered. This means that to ensure that your extension is registered last, it needs a negative value. > Allow Arquillian Core to define a way to execute registration of extensions in order > ------------------------------------------------------------------------------------ > > Key: ARQ-2053 > URL: https://issues.jboss.org/browse/ARQ-2053 > Project: Arquillian > Issue Type: Bug > Reporter: Alex Soto > Priority: Minor > > With Arquillian Extensions you are able to override a service that was previously registered by Arquillian Core or by other extensions. > The problem is that if if there two extensions that override the same service, it will depend on the order of the registration of the extension that will define which version of the service will be the one used at the end. > To avoid this problem this problem the best way would be to be able to set a priority in extension registry so you can set which one is going to be the last one. > The best none invasive approach we have found is by providing an SPI so any extension can vetoed any service /ResourceProvider/TestEnricher/... to be registered by an extension. This SPI is a file present at META-INF/services directory. The file is named with the service type you want to veto such as (`org.jboss.arquillian.test.spi.enricher.resource.ResourceProvider`) and inside all the implementations you want to veto each one in a new line. > So before starting registering the extensions, the vetoed list will be loaded into service registry so they cannot be registered. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 03:33:00 2016 From: issues at jboss.org (Alex Soto (JIRA)) Date: Fri, 11 Nov 2016 03:33:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2053) Allow Arquillian Core to define a way to execute registration of extensions in order In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2053: --------------------------- Description: With Arquillian Extensions you are able to override a service that was previously registered by Arquillian Core or by other extensions. The problem is that if if there two extensions that override the same service, it will depend on the order of the registration of the extension that will define which version of the service will be the one used at the end. To avoid this problem this problem the best way would be to be able to set a priority in extension registry so you can set which one is going to be the last one. The best none invasive approach we have found is by providing an SPI so any extension can vetoed any service /ResourceProvider/TestEnricher/... to be registered by an extension. This SPI is a file present at META-INF directory and called exclusions. The file is a properties file where key is the service type you want to veto such as (`org.jboss.arquillian.test.spi.enricher.resource.ResourceProvider`) and inside all the implementations you want to veto of this kind, each one separated by comma. So before starting registering the extensions, the vetoed list will be loaded into service registry so they cannot be registered. was: With Arquillian Extensions you are able to override a service that was previously registered by Arquillian Core or by other extensions. The problem is that if if there two extensions that override the same service, it will depend on the order of the registration of the extension that will define which version of the service will be the one used at the end. To avoid this problem this problem the best way would be to be able to set a priority in extension registry so you can set which one is going to be the last one. The best none invasive approach we have found is by providing an SPI so any extension can vetoed any service /ResourceProvider/TestEnricher/... to be registered by an extension. This SPI is a file present at META-INF/services directory. The file is named with the service type you want to veto such as (`org.jboss.arquillian.test.spi.enricher.resource.ResourceProvider`) and inside all the implementations you want to veto each one in a new line. So before starting registering the extensions, the vetoed list will be loaded into service registry so they cannot be registered. > Allow Arquillian Core to define a way to execute registration of extensions in order > ------------------------------------------------------------------------------------ > > Key: ARQ-2053 > URL: https://issues.jboss.org/browse/ARQ-2053 > Project: Arquillian > Issue Type: Bug > Reporter: Alex Soto > Priority: Minor > > With Arquillian Extensions you are able to override a service that was previously registered by Arquillian Core or by other extensions. > The problem is that if if there two extensions that override the same service, it will depend on the order of the registration of the extension that will define which version of the service will be the one used at the end. > To avoid this problem this problem the best way would be to be able to set a priority in extension registry so you can set which one is going to be the last one. > The best none invasive approach we have found is by providing an SPI so any extension can vetoed any service /ResourceProvider/TestEnricher/... to be registered by an extension. This SPI is a file present at META-INF directory and called exclusions. The file is a properties file where key is the service type you want to veto such as (`org.jboss.arquillian.test.spi.enricher.resource.ResourceProvider`) and inside all the implementations you want to veto of this kind, each one separated by comma. > So before starting registering the extensions, the vetoed list will be loaded into service registry so they cannot be registered. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 07:31:00 2016 From: issues at jboss.org (Hemani Katyal (JIRA)) Date: Fri, 11 Nov 2016 07:31:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2054) Update Dependencies In-Reply-To: References: Message-ID: Hemani Katyal created ARQ-2054: ---------------------------------- Summary: Update Dependencies Key: ARQ-2054 URL: https://issues.jboss.org/browse/ARQ-2054 Project: Arquillian Issue Type: Feature Request Components: Extension - Jacoco Reporter: Hemani Katyal Dependencies should be updated to the latest ones: * Arquilllian Core 1.1.11.Final * JaCoCo 0.7.7.201606060606 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 07:32:00 2016 From: issues at jboss.org (Hemani Katyal (JIRA)) Date: Fri, 11 Nov 2016 07:32:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2054) Update Dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemani Katyal updated ARQ-2054: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/27 > Update Dependencies > ------------------- > > Key: ARQ-2054 > URL: https://issues.jboss.org/browse/ARQ-2054 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Jacoco > Reporter: Hemani Katyal > > Dependencies should be updated to the latest ones: > * Arquilllian Core 1.1.11.Final > * JaCoCo 0.7.7.201606060606 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 07:36:00 2016 From: issues at jboss.org (Hemani Katyal (JIRA)) Date: Fri, 11 Nov 2016 07:36:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2054) Update Dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemani Katyal updated ARQ-2054: ------------------------------- Fix Version/s: jacoco_1.0.0.next > Update Dependencies > ------------------- > > Key: ARQ-2054 > URL: https://issues.jboss.org/browse/ARQ-2054 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Jacoco > Reporter: Hemani Katyal > Fix For: jacoco_1.0.0.next > > > Dependencies should be updated to the latest ones: > * Arquilllian Core 1.1.11.Final > * JaCoCo 0.7.7.201606060606 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 07:41:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 07:41:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2055) Update Tomcat containers to the latest versions In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2055: ----------------------------------- Summary: Update Tomcat containers to the latest versions Key: ARQ-2055 URL: https://issues.jboss.org/browse/ARQ-2055 Project: Arquillian Issue Type: Component Upgrade Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR7 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: tomcat_1.0.0.CR8 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 07:44:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 07:44:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2056) Module Tomcat In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2056: ----------------------------------- Summary: Module Tomcat Key: ARQ-2056 URL: https://issues.jboss.org/browse/ARQ-2056 Project: Arquillian Issue Type: Task Affects Versions: tomcat_1.0.0.CR7 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: tomcat_1.0.0.CR8 Skip tests for module tomcat-managed-5.5 if JDK 1.8 is used -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 07:51:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 07:51:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2056) Module tomcat-managed-5.5 cannot be tested on JDK 1.8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2056: -------------------------------- Summary: Module tomcat-managed-5.5 cannot be tested on JDK 1.8 (was: Module Tomcat) > Module tomcat-managed-5.5 cannot be tested on JDK 1.8 > ----------------------------------------------------- > > Key: ARQ-2056 > URL: https://issues.jboss.org/browse/ARQ-2056 > Project: Arquillian > Issue Type: Task > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > > Skip tests for module tomcat-managed-5.5 if JDK 1.8 is used -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 08:10:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 08:10:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2056) Module tomcat-managed-5.5 cannot be tested on JDK 1.8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2056: -------------------------------- Component/s: Tomcat Containers > Module tomcat-managed-5.5 cannot be tested on JDK 1.8 > ----------------------------------------------------- > > Key: ARQ-2056 > URL: https://issues.jboss.org/browse/ARQ-2056 > Project: Arquillian > Issue Type: Task > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > > Skip tests for module tomcat-managed-5.5 if JDK 1.8 is used -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 08:10:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 08:10:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2057) Upgrade test dependencies (Arquillian, shrinkwrap, weld) to the latest version In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2057: ----------------------------------- Summary: Upgrade test dependencies (Arquillian,shrinkwrap,weld) to the latest version Key: ARQ-2057 URL: https://issues.jboss.org/browse/ARQ-2057 Project: Arquillian Issue Type: Component Upgrade Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR7 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: tomcat_1.0.0.CR8 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 08:10:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 08:10:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2057) Upgrade test dependencies (Arquillian, ShrinkWrap, Weld) to the latest versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2057: -------------------------------- Summary: Upgrade test dependencies (Arquillian,ShrinkWrap,Weld) to the latest versions (was: Upgrade test dependencies (Arquillian,shrinkwrap,weld) to the latest version) > Upgrade test dependencies (Arquillian,ShrinkWrap,Weld) to the latest versions > ----------------------------------------------------------------------------- > > Key: ARQ-2057 > URL: https://issues.jboss.org/browse/ARQ-2057 > Project: Arquillian > Issue Type: Component Upgrade > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 08:24:00 2016 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Fri, 11 Nov 2016 08:24:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2058) Update Arquillian-Core to use TestNG 6.9.10 In-Reply-To: References: Message-ID: Dipak Pawar created ARQ-2058: -------------------------------- Summary: Update Arquillian-Core to use TestNG 6.9.10 Key: ARQ-2058 URL: https://issues.jboss.org/browse/ARQ-2058 Project: Arquillian Issue Type: Enhancement Reporter: Dipak Pawar Upgrade Arquillian-Core to use TestNg 6.9.10 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 08:24:00 2016 From: issues at jboss.org (Dipak Pawar (JIRA)) Date: Fri, 11 Nov 2016 08:24:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2058) Update Arquillian-Core to use TestNG 6.9.10 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dipak Pawar updated ARQ-2058: ----------------------------- Issue Type: Component Upgrade (was: Enhancement) > Update Arquillian-Core to use TestNG 6.9.10 > -------------------------------------------- > > Key: ARQ-2058 > URL: https://issues.jboss.org/browse/ARQ-2058 > Project: Arquillian > Issue Type: Component Upgrade > Reporter: Dipak Pawar > > Upgrade Arquillian-Core to use TestNg 6.9.10 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:13:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:13:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2055) Update Tomcat containers to the latest versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek resolved ARQ-2055. --------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/891dec92b8f6ac70712da4b7ddff95f57404449c > Update Tomcat containers to the latest versions > ----------------------------------------------- > > Key: ARQ-2055 > URL: https://issues.jboss.org/browse/ARQ-2055 > Project: Arquillian > Issue Type: Component Upgrade > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:14:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:14:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2056) Module tomcat-managed-5.5 cannot be tested on JDK 1.8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek resolved ARQ-2056. --------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/7ac4cc643ad4ee1bd7481f912c53cdab4a803cd6 > Module tomcat-managed-5.5 cannot be tested on JDK 1.8 > ----------------------------------------------------- > > Key: ARQ-2056 > URL: https://issues.jboss.org/browse/ARQ-2056 > Project: Arquillian > Issue Type: Task > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > > Skip tests for module tomcat-managed-5.5 if JDK 1.8 is used -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:15:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:15:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2057) Upgrade test dependencies (Arquillian, ShrinkWrap, Weld) to the latest versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek resolved ARQ-2057. --------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/5f305d89e197be7e2b7d55652fe2bd324ea7146b > Upgrade test dependencies (Arquillian,ShrinkWrap,Weld) to the latest versions > ----------------------------------------------------------------------------- > > Key: ARQ-2057 > URL: https://issues.jboss.org/browse/ARQ-2057 > Project: Arquillian > Issue Type: Component Upgrade > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:16:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:16:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1855) Tomcat 6 Embedded container should support deployment of ROOT.war to the default context In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1855: -------------------------------- Fix Version/s: tomcat_1.0.0.CR8 (was: tomcat_1.0.0.Final) > Tomcat 6 Embedded container should support deployment of ROOT.war to the default context > ---------------------------------------------------------------------------------------- > > Key: ARQ-1855 > URL: https://issues.jboss.org/browse/ARQ-1855 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.CR8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:17:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:17:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1847: -------------------------------- Fix Version/s: tomcat_1.0.0.CR8 (was: tomcat_1.0.0.Final) > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.CR8 > > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:17:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:17:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1814) TomcatManagedConfiguration validates catalinaBase too soon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1814: -------------------------------- Fix Version/s: tomcat_1.0.0.CR8 (was: tomcat_1.0.0.Final) > TomcatManagedConfiguration validates catalinaBase too soon > ---------------------------------------------------------- > > Key: ARQ-1814 > URL: https://issues.jboss.org/browse/ARQ-1814 > Project: Arquillian > Issue Type: Bug > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Brett Meyer > Fix For: tomcat_1.0.0.CR8 > > > CATALINA_BASE is only necessary if you're running multiple instances of Tomcat on a single host. If only one instance is running, CATALINA_BASE==CATALINA_HOME. > When catalinaBase is not set in arquillian.xml (tomcat 7 managed container), you get the following NPE. TomcatManagedContainer could probably assume CATALINA_BASE==CATALINA_HOME if CATALINA_BASE is not explicitly set. > {code} > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:177) > 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.JUnit4TestSet.execute(JUnit4TestSet.java:35) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:146) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97) > 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.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:145) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:87) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > Caused by: java.lang.NullPointerException > at java.io.File.(File.java:251) > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:105) > ... 67 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:19:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:19:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1814) TomcatManagedConfiguration validates catalinaBase too soon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-1814: ----------------------------------- Assignee: Aslak Knutsen > TomcatManagedConfiguration validates catalinaBase too soon > ---------------------------------------------------------- > > Key: ARQ-1814 > URL: https://issues.jboss.org/browse/ARQ-1814 > Project: Arquillian > Issue Type: Bug > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Brett Meyer > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.CR8 > > > CATALINA_BASE is only necessary if you're running multiple instances of Tomcat on a single host. If only one instance is running, CATALINA_BASE==CATALINA_HOME. > When catalinaBase is not set in arquillian.xml (tomcat 7 managed container), you get the following NPE. TomcatManagedContainer could probably assume CATALINA_BASE==CATALINA_HOME if CATALINA_BASE is not explicitly set. > {code} > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:177) > 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.JUnit4TestSet.execute(JUnit4TestSet.java:35) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:146) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97) > 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.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:145) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:87) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > Caused by: java.lang.NullPointerException > at java.io.File.(File.java:251) > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:105) > ... 67 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Nov 11 10:20:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 11 Nov 2016 10:20:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-600) Improve Tomcat codebase - Managed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-600: ------------------------------- Fix Version/s: tomcat_1.0.0.CR8 (was: tomcat_1.0.0.Final) > Improve Tomcat codebase - Managed > --------------------------------- > > Key: ARQ-600 > URL: https://issues.jboss.org/browse/ARQ-600 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Reporter: Aslak Knutsen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.CR8 > > > After the Tomcat Container code clean up, tomcat-common, it seems all the Managed Tomcat containers are identical both in impl and configuration. > We can create a similar tomcat-common-managed that will have the common parts between the different versions. > {note} > If Tomcat Managed 5.5, 6 and 7 are identical, why do we have 3 versions? > {note} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:16:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:16:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1983) tomcat-embedded-8 unpackArchive property doesn't have any effect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1983: -------------------------------- Fix Version/s: tomcat_1.0.0.CR8 > tomcat-embedded-8 unpackArchive property doesn't have any effect > ---------------------------------------------------------------- > > Key: ARQ-1983 > URL: https://issues.jboss.org/browse/ARQ-1983 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.0.CR7 > Reporter: Tomas Remes > Fix For: tomcat_1.0.0.CR8 > > > This attribute is on class {{org.apache.catalina.core.StandardHost}} as well and {{org.apache.catalina.startup.HostConfig#lifecycleEvent}} uses this value therefore {{org.apache.catalina.startup.HostConfig#unpackWARs}} seems to have no effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:21:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:21:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1983) tomcat-embedded-8 unpackArchive property doesn't have any effect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1983: -------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Tomas Remes Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/2ec0604f96cac9d975798cd251a19646baaa2c97 > tomcat-embedded-8 unpackArchive property doesn't have any effect > ---------------------------------------------------------------- > > Key: ARQ-1983 > URL: https://issues.jboss.org/browse/ARQ-1983 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.0.CR7 > Reporter: Tomas Remes > Assignee: Tomas Remes > Fix For: tomcat_1.0.0.CR8 > > > This attribute is on class {{org.apache.catalina.core.StandardHost}} as well and {{org.apache.catalina.startup.HostConfig#lifecycleEvent}} uses this value therefore {{org.apache.catalina.startup.HostConfig#unpackWARs}} seems to have no effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:23:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:23:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1965) Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1965: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: tomcat_1.0.0.CR8 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/5691b2b0f932207cc127d5bfb6bfabde38cf3271 > Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 > --------------------------------------------------------------------- > > Key: ARQ-1965 > URL: https://issues.jboss.org/browse/ARQ-1965 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.CR8 > > > Tomcat 7 Adapter rely on Code from 7.0.52 > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/EmbeddedHostConfig.java#L81 > and > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/Tomcat7EmbeddedContainer.java#L318 > ContextHome(String, Boolean) is new in 7.0.52 but missing in previous versions. > Use reflection to check if (String, Boolean) exists, else fall back to (String). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:26:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:26:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2033) Managed Tomcat fails to launch on Windows during maven test phase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek resolved ARQ-2033. --------------------------------- Fix Version/s: tomcat_1.0.0.CR8 Assignee: Matous Jobanek Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-container-tomcat/commit/2ad2d38275268723d25d97497c1b88f222a59a0a > Managed Tomcat fails to launch on Windows during maven test phase > ----------------------------------------------------------------- > > Key: ARQ-2033 > URL: https://issues.jboss.org/browse/ARQ-2033 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Environment: Windows 7, jdk 8 [1.8.0_66], maven 3.3.9 > Reporter: Dave Levitt > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > > The *TomcatManagedContainer* class assembles file system path parameters int its start tomcat command line by string concatenation, for example: > {{ cmd.add("-Djava.endorsed.dirs=" + absoluteCatalinaHomePath + "/endorsed");}} > > This works fine on Linux and OSX but fails for those developers afflicted by Windows as their dev system. The '/' character embedded in several string fragments needs to be replaced by the localized *java.util.File.separator* field. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:28:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:28:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2057) Upgrade test dependencies (Arquillian, ShrinkWrap, Weld) to the latest versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2057. ------------------------------- > Upgrade test dependencies (Arquillian,ShrinkWrap,Weld) to the latest versions > ----------------------------------------------------------------------------- > > Key: ARQ-2057 > URL: https://issues.jboss.org/browse/ARQ-2057 > Project: Arquillian > Issue Type: Component Upgrade > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:28:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:28:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2056) Module tomcat-managed-5.5 cannot be tested on JDK 1.8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2056. ------------------------------- > Module tomcat-managed-5.5 cannot be tested on JDK 1.8 > ----------------------------------------------------- > > Key: ARQ-2056 > URL: https://issues.jboss.org/browse/ARQ-2056 > Project: Arquillian > Issue Type: Task > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > > Skip tests for module tomcat-managed-5.5 if JDK 1.8 is used -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:29:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:29:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2055) Update Tomcat containers to the latest versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2055. ------------------------------- > Update Tomcat containers to the latest versions > ----------------------------------------------- > > Key: ARQ-2055 > URL: https://issues.jboss.org/browse/ARQ-2055 > Project: Arquillian > Issue Type: Component Upgrade > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:29:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:29:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2033) Managed Tomcat fails to launch on Windows during maven test phase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2033. ------------------------------- > Managed Tomcat fails to launch on Windows during maven test phase > ----------------------------------------------------------------- > > Key: ARQ-2033 > URL: https://issues.jboss.org/browse/ARQ-2033 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Environment: Windows 7, jdk 8 [1.8.0_66], maven 3.3.9 > Reporter: Dave Levitt > Assignee: Matous Jobanek > Fix For: tomcat_1.0.0.CR8 > > > The *TomcatManagedContainer* class assembles file system path parameters int its start tomcat command line by string concatenation, for example: > {{ cmd.add("-Djava.endorsed.dirs=" + absoluteCatalinaHomePath + "/endorsed");}} > > This works fine on Linux and OSX but fails for those developers afflicted by Windows as their dev system. The '/' character embedded in several string fragments needs to be replaced by the localized *java.util.File.separator* field. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:29:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:29:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1983) tomcat-embedded-8 unpackArchive property doesn't have any effect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1983. ------------------------------- > tomcat-embedded-8 unpackArchive property doesn't have any effect > ---------------------------------------------------------------- > > Key: ARQ-1983 > URL: https://issues.jboss.org/browse/ARQ-1983 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.0.CR7 > Reporter: Tomas Remes > Assignee: Tomas Remes > Fix For: tomcat_1.0.0.CR8 > > > This attribute is on class {{org.apache.catalina.core.StandardHost}} as well and {{org.apache.catalina.startup.HostConfig#lifecycleEvent}} uses this value therefore {{org.apache.catalina.startup.HostConfig#unpackWARs}} seems to have no effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:29:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:29:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1965) Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1965. ------------------------------- > Tomcat 7 Adapter rely on ContextHome constructor introduced in 7.0.52 > --------------------------------------------------------------------- > > Key: ARQ-1965 > URL: https://issues.jboss.org/browse/ARQ-1965 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.CR8 > > > Tomcat 7 Adapter rely on Code from 7.0.52 > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/EmbeddedHostConfig.java#L81 > and > https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/Tomcat7EmbeddedContainer.java#L318 > ContextHome(String, Boolean) is new in 7.0.52 but missing in previous versions. > Use reflection to check if (String, Boolean) exists, else fall back to (String). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:29:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:29:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1855) Tomcat 6 Embedded container should support deployment of ROOT.war to the default context In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1855. ------------------------------- > Tomcat 6 Embedded container should support deployment of ROOT.war to the default context > ---------------------------------------------------------------------------------------- > > Key: ARQ-1855 > URL: https://issues.jboss.org/browse/ARQ-1855 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.CR8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:29:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:29:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1847. ------------------------------- > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.CR8 > > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:30:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:30:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1814) TomcatManagedConfiguration validates catalinaBase too soon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-1814. ------------------------------- > TomcatManagedConfiguration validates catalinaBase too soon > ---------------------------------------------------------- > > Key: ARQ-1814 > URL: https://issues.jboss.org/browse/ARQ-1814 > Project: Arquillian > Issue Type: Bug > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Brett Meyer > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.CR8 > > > CATALINA_BASE is only necessary if you're running multiple instances of Tomcat on a single host. If only one instance is running, CATALINA_BASE==CATALINA_HOME. > When catalinaBase is not set in arquillian.xml (tomcat 7 managed container), you get the following NPE. TomcatManagedContainer could probably assume CATALINA_BASE==CATALINA_HOME if CATALINA_BASE is not explicitly set. > {code} > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:177) > 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.JUnit4TestSet.execute(JUnit4TestSet.java:35) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:146) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97) > 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.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:145) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:87) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > Caused by: java.lang.NullPointerException > at java.io.File.(File.java:251) > at org.jboss.arquillian.container.tomcat.managed_7.TomcatManagedContainer.start(TomcatManagedContainer.java:105) > ... 67 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 14 08:30:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 14 Nov 2016 08:30:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-600) Improve Tomcat codebase - Managed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-600. ------------------------------ > Improve Tomcat codebase - Managed > --------------------------------- > > Key: ARQ-600 > URL: https://issues.jboss.org/browse/ARQ-600 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Reporter: Aslak Knutsen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.CR8 > > > After the Tomcat Container code clean up, tomcat-common, it seems all the Managed Tomcat containers are identical both in impl and configuration. > We can create a similar tomcat-common-managed that will have the common parts between the different versions. > {note} > If Tomcat Managed 5.5, 6 and 7 are identical, why do we have 3 versions? > {note} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Nov 15 02:41:02 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Tue, 15 Nov 2016 02:41:02 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2052) Profiles in arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Garcia resolved ARQ-2052. -------------------------------- Release Notes Text: Ok, thank you very much for information. I will choose the first option ;) Resolution: Done > Profiles in arquillian.xml > -------------------------- > > Key: ARQ-2052 > URL: https://issues.jboss.org/browse/ARQ-2052 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: Development > Reporter: Rafael Garcia > Priority: Minor > > Hi, > Could It set the *arquillian.xml* file for different environments or profiles?? > For example: > {code:java} > ${jira.username} > ${jira.password} > ${jira.url} > {code} > On the other hand, we have a properties file with: > {code:java} > # JIRA PROPERTIES > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Nov 15 03:56:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 15 Nov 2016 03:56:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2052) Profiles in arquillian.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2052. ------------------------------- Assignee: Matous Jobanek > Profiles in arquillian.xml > -------------------------- > > Key: ARQ-2052 > URL: https://issues.jboss.org/browse/ARQ-2052 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: Development > Reporter: Rafael Garcia > Assignee: Matous Jobanek > Priority: Minor > > Hi, > Could It set the *arquillian.xml* file for different environments or profiles?? > For example: > {code:java} > ${jira.username} > ${jira.password} > ${jira.url} > {code} > On the other hand, we have a properties file with: > {code:java} > # JIRA PROPERTIES > jira.url=http://XXXXX:8080 > jira.username=XXXXX > jira.password=XXXXX > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Nov 15 07:34:01 2016 From: issues at jboss.org (Alex Soto (JIRA)) Date: Tue, 15 Nov 2016 07:34:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2012) Warnings when test runs as client without @RunAsClient In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto closed ARQ-2012. -------------------------- Resolution: Done Fixed in PR https://github.com/arquillian/arquillian-core/pull/106 > Warnings when test runs as client without @RunAsClient > ------------------------------------------------------ > > Key: ARQ-2012 > URL: https://issues.jboss.org/browse/ARQ-2012 > Project: Arquillian > Issue Type: Bug > Components: Deployable Containers SPI > Affects Versions: 1.1.11.Final > Reporter: Ladislav Thon > Assignee: Matous Jobanek > > When I moved to Arquillian 1.1.11.Final, I started getting warnings when my tests run as client but don't use the {{@RunAsClient}} annotation. The cause is ARQ-1937. > I'll just reiterate that I actually never ever use the {{@RunAsClient}} annotation because it's superfluous. I simply set my {{@Deployment}} to {{testable = false}} or I have no {{@Deployment}} at all. I do that intentionally and I _expect_ that the test will run as client, so the warning doesn't make much sense for me. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 07:48:00 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Mon, 21 Nov 2016 07:48:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2059) Arquillian Governor Jira get Value from properties In-Reply-To: References: Message-ID: Rafael Garcia created ARQ-2059: ---------------------------------- Summary: Arquillian Governor Jira get Value from properties Key: ARQ-2059 URL: https://issues.jboss.org/browse/ARQ-2059 Project: Arquillian Issue Type: Feature Request Components: Configuration Environment: Hi, In Arquillian Governor Jira, how set I issues from properties fiel in value field?? For example: In properties file {noformat} key.issue=PBT-2 {noformat} In test.java @Jira(value = "*{color:red}${key.issue}{color}*") public void exampleTest() {...} Thanks in advance Reporter: Rafael Garcia Priority: Optional -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 08:33:00 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Mon, 21 Nov 2016 08:33:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2059) Arquillian Governor Jira get Value from properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Garcia updated ARQ-2059: ------------------------------- Environment: In Arquillian Governor Jira, how set I issues from properties fiel in value field?? (was: Hi, In Arquillian Governor Jira, how set I issues from properties fiel in value field?? For example: In properties file {noformat} key.issue=PBT-2 {noformat} In test.java @Jira(value = "*{color:red}${key.issue}{color}*") public void exampleTest() {...} Thanks in advance) > Arquillian Governor Jira get Value from properties > --------------------------------------------------- > > Key: ARQ-2059 > URL: https://issues.jboss.org/browse/ARQ-2059 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > Reporter: Rafael Garcia > Priority: Optional > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Nov 21 08:34:00 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Mon, 21 Nov 2016 08:34:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2059) Arquillian Governor Jira get Value from properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Garcia updated ARQ-2059: ------------------------------- Description: Hi, In Arquillian Governor Jira, how set I issues from properties fiel in value field?? For example: In properties file {noformat} key.issue=PBT-2 {noformat} In test.java @Jira(value = "*{color:red}${key.issue}{color}*") public void exampleTest() {...} Thanks in advance > Arquillian Governor Jira get Value from properties > --------------------------------------------------- > > Key: ARQ-2059 > URL: https://issues.jboss.org/browse/ARQ-2059 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > Reporter: Rafael Garcia > Priority: Optional > > Hi, > In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > For example: > In properties file > {noformat} > key.issue=PBT-2 > {noformat} > In test.java > @Jira(value = "*{color:red}${key.issue}{color}*") > public void exampleTest() {...} > Thanks in advance -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 23 03:44:00 2016 From: issues at jboss.org (Rafael Garcia (JIRA)) Date: Wed, 23 Nov 2016 03:44:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2059) Arquillian Governor Jira get Value from properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Garcia updated ARQ-2059: ------------------------------- Priority: Minor (was: Optional) > Arquillian Governor Jira get Value from properties > --------------------------------------------------- > > Key: ARQ-2059 > URL: https://issues.jboss.org/browse/ARQ-2059 > Project: Arquillian > Issue Type: Feature Request > Components: Configuration > Environment: In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > Reporter: Rafael Garcia > Priority: Minor > > Hi, > In Arquillian Governor Jira, how set I issues from properties fiel in value field?? > For example: > In properties file > {noformat} > key.issue=PBT-2 > {noformat} > In test.java > @Jira(value = "*{color:red}${key.issue}{color}*") > public void exampleTest() {...} > Thanks in advance -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 23 13:24:00 2016 From: issues at jboss.org (Stephan ivanov (JIRA)) Date: Wed, 23 Nov 2016 13:24:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1611) Arquillian doesn't handle Glassfish REST API redirect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13327391#comment-13327391 ] Stephan ivanov commented on ARQ-1611: ------------------------------------- Unfortunately I have the same problem. I've already tried everything I've found. Local works with no problems, remoute always: com.sun.jersey.api.container.ContainerException: [status: REDIRECTION reason: Found] at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getResponseMap(GlassFishClientUtil.java:177) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.GETRequest(GlassFishClientUtil.java:101) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getChildResources(GlassFishClientUtil.java:88) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.getServersList(GlassFishClientService.java:314) at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.startUp(GlassFishClientService.java:100) at org.jboss.arquillian.container.glassfish.CommonGlassFishManager.start(CommonGlassFishManager.java:64) at org.jboss.arquillian.container.glassfish.remote_3_1.GlassFishRestDeployableContainer.start(GlassFishRestDeployableContainer.java:58) at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) . . . . I have tested with i Glassfish.4.1.1 and Payara Server 164 Full Has anyone solved this problem. > Arquillian doesn't handle Glassfish REST API redirect > ----------------------------------------------------- > > Key: ARQ-1611 > URL: https://issues.jboss.org/browse/ARQ-1611 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Environment: Windows client and server > Windows client, Linux server > Linux client, Windows server > Glassfish 3.1.2.2, 4.0 and 4.0.1-b03-ml > Reporter: Andr? Pinheiro > > When deploying to a remote glassfish DAS instance, the REST API sends back a 302 redirect. Arquillian GlassFishClientUtil fails to handle that redirect - as it wasn't expecting that kind of response - and the following exception is thrown: > {quote} > com.sun.jersey.api.container.ContainerException: [status: REDIRECTION reason: Found] > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getResponseMap(GlassFishClientUtil.java:192) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.GETRequest(GlassFishClientUtil.java:109) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientUtil.getChildResources(GlassFishClientUtil.java:95) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.getServersList(GlassFishClientService.java:319) > at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.startUp(GlassFishClientService.java:102) > at org.jboss.arquillian.container.glassfish.CommonGlassFishManager.start(CommonGlassFishManager.java:72) > at org.jboss.arquillian.container.glassfish.remote_3_1.GlassFishRestDeployableContainer.start(GlassFishRestDeployableContainer.java:59) > 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:606) > 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:606) > 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:606) > 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:606) > 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:606) > 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.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > 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:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 24 04:29:00 2016 From: issues at jboss.org (Gerrit Hohl (JIRA)) Date: Thu, 24 Nov 2016 04:29:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1070) Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13327620#comment-13327620 ] Gerrit Hohl commented on ARQ-1070: ---------------------------------- I'm using arquillian-junit-container. And it also doesn't execute the @BeforeClass, @Before, @After and @AfterClass annotated methods of my test. Yes, I have an @Deployment annotated method. But still it would be nice if these methods would still work the way you would expect it from a JUnit test. > Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation > ----------------------------------------------------------------------------------- > > Key: ARQ-1070 > URL: https://issues.jboss.org/browse/ARQ-1070 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.0.2.Final > Environment: Java(TM) SE Runtime Environment (build 1.7.0_04-b20) > Reporter: Jan Papousek > Labels: junit > Attachments: junit-sample.zip > > > The following test doesn't pass: > {code} > @RunWith(Arquillian.class) > public class AppTest { > private boolean before = false; > @Before > public void before() { > this.before = true; > } > @Test > public void testBefore() { > Assert.assertTrue(before); > } > } > {code} > The same test without @RunWith annotation passes. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 24 05:56:00 2016 From: issues at jboss.org (Gerrit Hohl (JIRA)) Date: Thu, 24 Nov 2016 05:56:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1070) Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13327700#comment-13327700 ] Gerrit Hohl commented on ARQ-1070: ---------------------------------- Okay, I take everything back: arquillian-junit-container still supports the default annotations. It is just that they are called very late / early in the process. E.g. @BeforeClass is called after the deployment and @AfterClass before the removal of the deployment. > Arquillian JUnit Standalone doesn't execute methods annotated by @Before annotation > ----------------------------------------------------------------------------------- > > Key: ARQ-1070 > URL: https://issues.jboss.org/browse/ARQ-1070 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.0.2.Final > Environment: Java(TM) SE Runtime Environment (build 1.7.0_04-b20) > Reporter: Jan Papousek > Labels: junit > Attachments: junit-sample.zip > > > The following test doesn't pass: > {code} > @RunWith(Arquillian.class) > public class AppTest { > private boolean before = false; > @Before > public void before() { > this.before = true; > } > @Test > public void testBefore() { > Assert.assertTrue(before); > } > } > {code} > The same test without @RunWith annotation passes. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Nov 24 16:47:00 2016 From: issues at jboss.org (Artur Signell (JIRA)) Date: Thu, 24 Nov 2016 16:47:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-493) Javassist enhanced WebDriver does not work In-Reply-To: References: Message-ID: Artur Signell created ARQGRA-493: ------------------------------------ Summary: Javassist enhanced WebDriver does not work Key: ARQGRA-493 URL: https://issues.jboss.org/browse/ARQGRA-493 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.1.0.Final Reporter: Artur Signell When a WebDriver is wrapped inside a Javassist proxy, it seems that it will be rewrapped inside another proxy in org.jboss.arquillian.graphene.context.GrapheneContextImpl.LazyContext.getWebDriver(). After this, when driver.get(...) is executed, the result is java.lang.RuntimeException: not found _d32get:(Ljava/lang/String;)V in com.vaadin.testbench.TestBenchDriverProxy_$$_javassist_0$$EnhancerByGraphene$$a623df4c at javassist.util.proxy.RuntimeSupport.error(RuntimeSupport.java:94) at javassist.util.proxy.RuntimeSupport.findMethod(RuntimeSupport.java:70) at javassist.util.proxy.RuntimeSupport.find2Methods(RuntimeSupport.java:54) at com.vaadin.testbench.TestBenchDriverProxy_$$_javassist_0.get(TestBenchDriverProxy_$$_javassist_0.java) at org.jboss.arquillian.graphene.location.LocationEnricher.handleLocationOf(LocationEnricher.java:136) at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:96) at org.jboss.arquillian.graphene.location.LocationEnricher.resolve(LocationEnricher.java:81) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.enrichArguments(LocalTestExecuter.java:94) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:61) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) This does not happen if GrapheneProxyUtil.isProxy is updated to contain an additional check for javassist proxies: if (interfaze.getName().equals("javassist.util.proxy.ProxyObject")) { return true; } As I am not very familiar with this project, I have really no clue if this is a good or bad solution. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Nov 29 03:49:00 2016 From: issues at jboss.org (Tomas David (JIRA)) Date: Tue, 29 Nov 2016 03:49:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: Tomas David created ARQ-2060: -------------------------------- Summary: Support for Edge browser Key: ARQ-2060 URL: https://issues.jboss.org/browse/ARQ-2060 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Affects Versions: drone_2.1.0.Final Environment: Windows 10 Reporter: Tomas David Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Nov 29 03:52:00 2016 From: issues at jboss.org (Tomas David (JIRA)) Date: Tue, 29 Nov 2016 03:52:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13330615#comment-13330615 ] Tomas David commented on ARQ-2060: ---------------------------------- Please assign this task to me [~tomasdavidorg]. > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Nov 30 10:40:28 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 30 Nov 2016 10:40:28 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2060) Support for Edge browser In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-2060: ----------------------------------- Assignee: Tomas David > Support for Edge browser > ------------------------ > > Key: ARQ-2060 > URL: https://issues.jboss.org/browse/ARQ-2060 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.1.0.Final > Environment: Windows 10 > Reporter: Tomas David > Assignee: Tomas David > > Edge browser is not currently supported. Available options are: opera, safari, chrome, phantomjs, firefox, htmlUnit, internetExplorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)