From issues at jboss.org  Tue Aug  1 05:21:00 2017
From: issues at jboss.org (Benjamin Marwell (JIRA))
Date: Tue, 1 Aug 2017 05:21:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2131) Fix for multiple JVM
	arguments not release
In-Reply-To: <JIRA.12705112.1501159232000@Atlassian.JIRA>
References: <JIRA.12705112.1501159232000@Atlassian.JIRA>
	<JIRA.12705112.1501159232000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12705112.1501159232000.42038.1501579260528@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442564#comment-13442564 ] 

Benjamin Marwell commented on ARQ-2131:
---------------------------------------

Hello [~gpoul],

thanks for your reply. I know there is a fix coming in the next release. This issue is about the fact, that there was no release for two years.

I'd look into it about the test.

> Fix for multiple JVM arguments not release
> ------------------------------------------
>
>                 Key: ARQ-2131
>                 URL: https://issues.jboss.org/browse/ARQ-2131
>             Project: Arquillian
>          Issue Type: Bug
>          Components: WebSphere Containers
>         Environment: {code}arquillian-container-was-1.0.0.Beta2{code}
> {{arquillian.xml}} snippet:
> {code:xml}  <container qualifier="liberty-ci-managed">
>     <configuration>
>       <property name="deployType">xml</property>
>       <property name="javaVmArguments">-Dsetting1=x -Dsetting2=y</property>
>     </configuration>
>   </container>{code}
>            Reporter: Benjamin Marwell
>            Assignee: Gerhard Poul
>             Fix For: was_1.0.0.next
>
>
> Hello,
> h2. expected output
> Process started with (from Debug):
> {{FINER: Starting server with command: [java, -Dsetting1=x, -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}}
> h2. actual output
> note the missing comma betweed setting1 and setting2:
> {{FINER: Starting server with command: [java, -Dsetting1=x -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}}
> h2. Solution
> Already exists. This commit is currently not in a release:
> https://github.com/arquillian/arquillian-container-was/commit/a1a77fe92418f49943a97a57a4dd1ff7ebc2bd25#diff-957685487719c29ce4c464fc2ec9cf39
> What can't be seen from here: this commit is needed to have multiple JVM args. Otherwise all jvm args are concatenated into a single String.
> So, the bug is fixed in trunk, but not released.
> h2. Proposed test case
> It is also missing a test  case.
> Please add a test case with two or more {{-D}}-Parameters and check in your servlet if they are set.
> Thank you very much!



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Tue Aug  1 12:37:00 2017
From: issues at jboss.org (Gerhard Poul (JIRA))
Date: Tue, 1 Aug 2017 12:37:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2131) Fix for multiple JVM
	arguments not released
In-Reply-To: <JIRA.12705112.1501159232000@Atlassian.JIRA>
References: <JIRA.12705112.1501159232000@Atlassian.JIRA>
	<JIRA.12705112.1501159232000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12705112.1501159232000.47636.1501605420311@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Poul updated ARQ-2131:
------------------------------
    Summary: Fix for multiple JVM arguments not released  (was: Fix for multiple JVM arguments not release)


> Fix for multiple JVM arguments not released
> -------------------------------------------
>
>                 Key: ARQ-2131
>                 URL: https://issues.jboss.org/browse/ARQ-2131
>             Project: Arquillian
>          Issue Type: Bug
>          Components: WebSphere Containers
>         Environment: {code}arquillian-container-was-1.0.0.Beta2{code}
> {{arquillian.xml}} snippet:
> {code:xml}  <container qualifier="liberty-ci-managed">
>     <configuration>
>       <property name="deployType">xml</property>
>       <property name="javaVmArguments">-Dsetting1=x -Dsetting2=y</property>
>     </configuration>
>   </container>{code}
>            Reporter: Benjamin Marwell
>            Assignee: Gerhard Poul
>             Fix For: was_1.0.0.next
>
>
> Hello,
> h2. expected output
> Process started with (from Debug):
> {{FINER: Starting server with command: [java, -Dsetting1=x, -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}}
> h2. actual output
> note the missing comma betweed setting1 and setting2:
> {{FINER: Starting server with command: [java, -Dsetting1=x -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}}
> h2. Solution
> Already exists. This commit is currently not in a release:
> https://github.com/arquillian/arquillian-container-was/commit/a1a77fe92418f49943a97a57a4dd1ff7ebc2bd25#diff-957685487719c29ce4c464fc2ec9cf39
> What can't be seen from here: this commit is needed to have multiple JVM args. Otherwise all jvm args are concatenated into a single String.
> So, the bug is fixed in trunk, but not released.
> h2. Proposed test case
> It is also missing a test  case.
> Please add a test case with two or more {{-D}}-Parameters and check in your servlet if they are set.
> Thank you very much!



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Tue Aug  1 12:38:00 2017
From: issues at jboss.org (Gerhard Poul (JIRA))
Date: Tue, 1 Aug 2017 12:38:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2131) Fix for multiple JVM
	arguments not released
In-Reply-To: <JIRA.12705112.1501159232000@Atlassian.JIRA>
References: <JIRA.12705112.1501159232000@Atlassian.JIRA>
	<JIRA.12705112.1501159232000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12705112.1501159232000.47639.1501605480370@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442934#comment-13442934 ] 

Gerhard Poul commented on ARQ-2131:
-----------------------------------

[~aslak] What do you think? Would you be able to push a new beta out?

> Fix for multiple JVM arguments not released
> -------------------------------------------
>
>                 Key: ARQ-2131
>                 URL: https://issues.jboss.org/browse/ARQ-2131
>             Project: Arquillian
>          Issue Type: Bug
>          Components: WebSphere Containers
>         Environment: {code}arquillian-container-was-1.0.0.Beta2{code}
> {{arquillian.xml}} snippet:
> {code:xml}  <container qualifier="liberty-ci-managed">
>     <configuration>
>       <property name="deployType">xml</property>
>       <property name="javaVmArguments">-Dsetting1=x -Dsetting2=y</property>
>     </configuration>
>   </container>{code}
>            Reporter: Benjamin Marwell
>            Assignee: Gerhard Poul
>             Fix For: was_1.0.0.next
>
>
> Hello,
> h2. expected output
> Process started with (from Debug):
> {{FINER: Starting server with command: [java, -Dsetting1=x, -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}}
> h2. actual output
> note the missing comma betweed setting1 and setting2:
> {{FINER: Starting server with command: [java, -Dsetting1=x -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}}
> h2. Solution
> Already exists. This commit is currently not in a release:
> https://github.com/arquillian/arquillian-container-was/commit/a1a77fe92418f49943a97a57a4dd1ff7ebc2bd25#diff-957685487719c29ce4c464fc2ec9cf39
> What can't be seen from here: this commit is needed to have multiple JVM args. Otherwise all jvm args are concatenated into a single String.
> So, the bug is fixed in trunk, but not released.
> h2. Proposed test case
> It is also missing a test  case.
> Please add a test case with two or more {{-D}}-Parameters and check in your servlet if they are set.
> Thank you very much!



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Aug  3 10:37:00 2017
From: issues at jboss.org (Vaclav Muzikar (JIRA))
Date: Thu, 3 Aug 2017 10:37:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2132) Support for
 FirefoxOptions and SafariOptions in Drone
In-Reply-To: <JIRA.12706022.1501771005000@Atlassian.JIRA>
References: <JIRA.12706022.1501771005000@Atlassian.JIRA>
	<JIRA.12706022.1501771005063@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706022.1501771005000.60335.1501771020104@Atlassian.JIRA>

Vaclav Muzikar created ARQ-2132:
-----------------------------------

             Summary: Support for FirefoxOptions and SafariOptions in Drone
                 Key: ARQ-2132
                 URL: https://issues.jboss.org/browse/ARQ-2132
             Project: Arquillian
          Issue Type: Feature Request
          Components: Extension - Drone
            Reporter: Vaclav Muzikar
            Assignee: Vaclav Muzikar


FirefoxOptions are mainly needed for setting up the GeckoDriver logger level.
SafariOptions are needed for testing with Safari Technical Preview.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug  4 04:40:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Fri, 4 Aug 2017 04:40:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-511) Graphene proxies
 don't support calling protected/package-protected methods in valid context
In-Reply-To: <JIRA.12706118.1501835951000@Atlassian.JIRA>
References: <JIRA.12706118.1501835951000@Atlassian.JIRA>
	<JIRA.12706118.1501835951877@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706118.1501835951000.63738.1501836000169@Atlassian.JIRA>

Vsevolod Golovanov created ARQGRA-511:
-----------------------------------------

             Summary: Graphene proxies don't support calling protected/package-protected methods in valid context
                 Key: ARQGRA-511
                 URL: https://issues.jboss.org/browse/ARQGRA-511
             Project: Arquillian Graphene
          Issue Type: Bug
          Components: core
    Affects Versions: 2.1.0.Final
            Reporter: Vsevolod Golovanov


I have this base Component (Page Fragment) Class:
{code}
public abstract class Component {

	protected WebElement getRoot() {
		// ...
	}

	@Override
	public boolean equals(Object obj) {
		if (!(obj instanceof Component))
			return false;

                // WebElementUtils.equal is a ARQGRA-484 workaround, irrelevant here
		return WebElementUtils.equal(getRoot(), ((Component) obj).getRoot());
	}

}
{code}
The equals call results in an exception
{code}java.lang.RuntimeException: unexpected invocation exception during invocation of ru.argustelecom.system.inf.testframework.it.ui.comp.Component#getRoot(), on target 'ru.argustelecom.system.inf.testframework.it.ui.comp.AutoComplete at 83ddf46d': Class org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler can not access a member of class ru.argustelecom.system.inf.testframework.it.ui.comp.Component with modifiers "protected"
	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:137)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212)
	at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:234)
	at ru.argustelecom.system.inf.testframework.it.ui.comp.AutoComplete$$EnhancerByGraphene$$4040d070.getRoot(<generated>)
	at ru.argustelecom.system.inf.testframework.it.ui.comp.Component.equals(Component.java:283)
	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.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:130)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212)
	at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208)
	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:234)
	at ru.argustelecom.system.inf.testframework.it.ui.comp.AutoComplete$$EnhancerByGraphene$$4040d070.equals(<generated>)
	at org.junit.Assert.isEquals(Assert.java:131)
	at org.junit.Assert.equalsRegardingNull(Assert.java:127)
	at org.junit.Assert.assertEquals(Assert.java:111)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at ru.argustelecom.system.inf.testframework.it.ui.comp.test.AutoCompleteIT.autoComplete(AutoCompleteIT.java:42)
	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.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.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:370)
	at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
	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)
	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:145)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
	at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
	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)
	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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
	at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363)
	at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245)
	at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
	at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
	at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315)
	at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
	at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72)
	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)
	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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
	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)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
	at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311)
	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.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204)
	at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
	at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
	at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166)
	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
	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:678)
	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.IllegalAccessException: Class org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler can not access a member of class ru.argustelecom.system.inf.testframework.it.ui.comp.Component with modifiers "protected"
	at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:102)
	at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:296)
	at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:288)
	at java.lang.reflect.Method.invoke(Method.java:491)
	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:130)
	... 151 more
{code}
Looking at the GrapheneProxyHandler code:
{code}
    protected Object invokeReal(Object target, Method method, Object[] args) throws Throwable {
        Object result;
        try {
            if (target instanceof GrapheneProxyInstance) {
                target = ((GrapheneProxyInstance) target).unwrap();
            }
            if (!method.getDeclaringClass().isInstance(target)) {
                Method realMethod = target.getClass().getDeclaredMethod(method.getName(), method.getParameterTypes());
                if (!realMethod.isAccessible()) {
                    realMethod.setAccessible(true);
                }
                result = realMethod.invoke(target, args);
            } else {
                result = method.invoke(target, args);
            }
            // ...
{code}
This {{!method.getDeclaringClass().isInstance(target)}} check doesn't pass, so the accessibility modification is skipped. And naturally GrapheneProxyHandler doesn't have an access to Component#getRoot since it's in a different package and not a subclass.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug  4 06:33:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Fri, 4 Aug 2017 06:33:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-511) Graphene proxies
 don't support calling protected/package-protected methods in a valid
 context
In-Reply-To: <JIRA.12706118.1501835952000@Atlassian.JIRA>
References: <JIRA.12706118.1501835952000@Atlassian.JIRA>
	<JIRA.12706118.1501835952000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706118.1501835952000.64608.1501842780176@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQGRA-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vsevolod Golovanov updated ARQGRA-511:
--------------------------------------
    Summary: Graphene proxies don't support calling protected/package-protected methods in a valid context  (was: Graphene proxies don't support calling protected/package-protected methods in valid context)


> Graphene proxies don't support calling protected/package-protected methods in a valid context
> ---------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-511
>                 URL: https://issues.jboss.org/browse/ARQGRA-511
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.1.0.Final
>            Reporter: Vsevolod Golovanov
>
> I have this base Component (Page Fragment) Class:
> {code}
> public abstract class Component {
> 	protected WebElement getRoot() {
> 		// ...
> 	}
> 	@Override
> 	public boolean equals(Object obj) {
> 		if (!(obj instanceof Component))
> 			return false;
>                 // WebElementUtils.equal is a ARQGRA-484 workaround, irrelevant here
> 		return WebElementUtils.equal(getRoot(), ((Component) obj).getRoot());
> 	}
> }
> {code}
> The equals call results in an exception
> {code}java.lang.RuntimeException: unexpected invocation exception during invocation of ru.argustelecom.system.inf.testframework.it.ui.comp.Component#getRoot(), on target 'ru.argustelecom.system.inf.testframework.it.ui.comp.AutoComplete at 83ddf46d': Class org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler can not access a member of class ru.argustelecom.system.inf.testframework.it.ui.comp.Component with modifiers "protected"
> 	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:137)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212)
> 	at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:234)
> 	at ru.argustelecom.system.inf.testframework.it.ui.comp.AutoComplete$$EnhancerByGraphene$$4040d070.getRoot(<generated>)
> 	at ru.argustelecom.system.inf.testframework.it.ui.comp.Component.equals(Component.java:283)
> 	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.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:130)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212)
> 	at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:234)
> 	at ru.argustelecom.system.inf.testframework.it.ui.comp.AutoComplete$$EnhancerByGraphene$$4040d070.equals(<generated>)
> 	at org.junit.Assert.isEquals(Assert.java:131)
> 	at org.junit.Assert.equalsRegardingNull(Assert.java:127)
> 	at org.junit.Assert.assertEquals(Assert.java:111)
> 	at org.junit.Assert.assertEquals(Assert.java:144)
> 	at ru.argustelecom.system.inf.testframework.it.ui.comp.test.AutoCompleteIT.autoComplete(AutoCompleteIT.java:42)
> 	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.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.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:370)
> 	at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> 	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)
> 	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:145)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> 	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> 	at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
> 	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)
> 	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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> 	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
> 	at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363)
> 	at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245)
> 	at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> 	at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> 	at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259)
> 	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> 	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 	at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:315)
> 	at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> 	at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72)
> 	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)
> 	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.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> 	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)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> 	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
> 	at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:311)
> 	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.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204)
> 	at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422)
> 	at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> 	at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 	at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> 	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:678)
> 	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.IllegalAccessException: Class org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler can not access a member of class ru.argustelecom.system.inf.testframework.it.ui.comp.Component with modifiers "protected"
> 	at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:102)
> 	at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:296)
> 	at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:288)
> 	at java.lang.reflect.Method.invoke(Method.java:491)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:130)
> 	... 151 more
> {code}
> Looking at the GrapheneProxyHandler code:
> {code}
>     protected Object invokeReal(Object target, Method method, Object[] args) throws Throwable {
>         Object result;
>         try {
>             if (target instanceof GrapheneProxyInstance) {
>                 target = ((GrapheneProxyInstance) target).unwrap();
>             }
>             if (!method.getDeclaringClass().isInstance(target)) {
>                 Method realMethod = target.getClass().getDeclaredMethod(method.getName(), method.getParameterTypes());
>                 if (!realMethod.isAccessible()) {
>                     realMethod.setAccessible(true);
>                 }
>                 result = realMethod.invoke(target, args);
>             } else {
>                 result = method.invoke(target, args);
>             }
>             // ...
> {code}
> This {{!method.getDeclaringClass().isInstance(target)}} check doesn't pass, so the accessibility modification is skipped. And naturally GrapheneProxyHandler doesn't have an access to Component#getRoot since it's in a different package and not a subclass.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug  4 08:38:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Fri, 4 Aug 2017 08:38:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage
	work for Field
In-Reply-To: <JIRA.12501724.1380281456000@Atlassian.JIRA>
References: <JIRA.12501724.1380281456000@Atlassian.JIRA>
	<JIRA.12501724.1380281456000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501724.1380281456000.65075.1501850280722@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444441#comment-13444441 ] 

Vsevolod Golovanov commented on ARQGRA-382:
-------------------------------------------

bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...

> Make @InitialPage work for Field
> --------------------------------
>
>                 Key: ARQGRA-382
>                 URL: https://issues.jboss.org/browse/ARQGRA-382
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> While @InitialPage allows to be used on test class field, it does not do anything.
> {code}
> @InitialPage AddUserPage page;
> @Test
> void test() {
>     page.foo()
> }
> {code}
> raises
> {code}
> java.lang.NullPointerException: null
>         at com.acme.example.test.DroneTest.addUser(DroneTest.java:35)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug  4 08:39:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Fri, 4 Aug 2017 08:39:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage
	work for Field
In-Reply-To: <JIRA.12501724.1380281456000@Atlassian.JIRA>
References: <JIRA.12501724.1380281456000@Atlassian.JIRA>
	<JIRA.12501724.1380281456000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501724.1380281456000.65079.1501850340332@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444441#comment-13444441 ] 

Vsevolod Golovanov edited comment on ARQGRA-382 at 8/4/17 8:38 AM:
-------------------------------------------------------------------

bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the pages behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...


was (Author: vsevolodgolovanov):
bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...

> Make @InitialPage work for Field
> --------------------------------
>
>                 Key: ARQGRA-382
>                 URL: https://issues.jboss.org/browse/ARQGRA-382
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> While @InitialPage allows to be used on test class field, it does not do anything.
> {code}
> @InitialPage AddUserPage page;
> @Test
> void test() {
>     page.foo()
> }
> {code}
> raises
> {code}
> java.lang.NullPointerException: null
>         at com.acme.example.test.DroneTest.addUser(DroneTest.java:35)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug  4 08:39:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Fri, 4 Aug 2017 08:39:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage
	work for Field
In-Reply-To: <JIRA.12501724.1380281456000@Atlassian.JIRA>
References: <JIRA.12501724.1380281456000@Atlassian.JIRA>
	<JIRA.12501724.1380281456000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501724.1380281456000.65083.1501850340468@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444441#comment-13444441 ] 

Vsevolod Golovanov edited comment on ARQGRA-382 at 8/4/17 8:38 AM:
-------------------------------------------------------------------

bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...


was (Author: vsevolodgolovanov):
bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the pages behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...

> Make @InitialPage work for Field
> --------------------------------
>
>                 Key: ARQGRA-382
>                 URL: https://issues.jboss.org/browse/ARQGRA-382
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> While @InitialPage allows to be used on test class field, it does not do anything.
> {code}
> @InitialPage AddUserPage page;
> @Test
> void test() {
>     page.foo()
> }
> {code}
> raises
> {code}
> java.lang.NullPointerException: null
>         at com.acme.example.test.DroneTest.addUser(DroneTest.java:35)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug  4 08:41:01 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Fri, 4 Aug 2017 08:41:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage
	work for Field
In-Reply-To: <JIRA.12501724.1380281456000@Atlassian.JIRA>
References: <JIRA.12501724.1380281456000@Atlassian.JIRA>
	<JIRA.12501724.1380281456000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501724.1380281456000.65105.1501850461019@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444441#comment-13444441 ] 

Vsevolod Golovanov edited comment on ARQGRA-382 at 8/4/17 8:40 AM:
-------------------------------------------------------------------

bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated, though class scoped InitialPage certainly makes no sense with a method scoped Drone).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...


was (Author: vsevolodgolovanov):
bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...

> Make @InitialPage work for Field
> --------------------------------
>
>                 Key: ARQGRA-382
>                 URL: https://issues.jboss.org/browse/ARQGRA-382
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> While @InitialPage allows to be used on test class field, it does not do anything.
> {code}
> @InitialPage AddUserPage page;
> @Test
> void test() {
>     page.foo()
> }
> {code}
> raises
> {code}
> java.lang.NullPointerException: null
>         at com.acme.example.test.DroneTest.addUser(DroneTest.java:35)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug  4 11:21:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Fri, 4 Aug 2017 11:21:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage
	work for Field
In-Reply-To: <JIRA.12501724.1380281456000@Atlassian.JIRA>
References: <JIRA.12501724.1380281456000@Atlassian.JIRA>
	<JIRA.12501724.1380281456000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501724.1380281456000.66292.1501860060181@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444441#comment-13444441 ] 

Vsevolod Golovanov edited comment on ARQGRA-382 at 8/4/17 11:20 AM:
--------------------------------------------------------------------

bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. -It also mirrors the default Drone instance scope- (Update: I forgot, the default is class scope.) (but I don't think these scopes should always be equated, though class scoped InitialPage certainly makes no sense with a method scoped Drone).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...


was (Author: vsevolodgolovanov):
bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. It also mirrors the default Drone instance scope (but I don't think these scopes should always be equated, though class scoped InitialPage certainly makes no sense with a method scoped Drone).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...

> Make @InitialPage work for Field
> --------------------------------
>
>                 Key: ARQGRA-382
>                 URL: https://issues.jboss.org/browse/ARQGRA-382
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> While @InitialPage allows to be used on test class field, it does not do anything.
> {code}
> @InitialPage AddUserPage page;
> @Test
> void test() {
>     page.foo()
> }
> {code}
> raises
> {code}
> java.lang.NullPointerException: null
>         at com.acme.example.test.DroneTest.addUser(DroneTest.java:35)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Aug  7 04:03:00 2017
From: issues at jboss.org (Evgeniya Evlogieva (JIRA))
Date: Mon, 7 Aug 2017 04:03:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2133) When deployment fails
 tests with @OperateOnDeployment are still executed
In-Reply-To: <JIRA.12706283.1502092957000@Atlassian.JIRA>
References: <JIRA.12706283.1502092957000@Atlassian.JIRA>
	<JIRA.12706283.1502092957247@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706283.1502092957000.69449.1502092980147@Atlassian.JIRA>

Evgeniya Evlogieva created ARQ-2133:
---------------------------------------

             Summary: When deployment fails tests with @OperateOnDeployment are still executed
                 Key: ARQ-2133
                 URL: https://issues.jboss.org/browse/ARQ-2133
             Project: Arquillian
          Issue Type: Bug
          Components: Deployable Containers SPI
    Affects Versions: 1.1.13.Final
            Reporter: Evgeniya Evlogieva


An application is deployed by the arquillian's @Deployment annotation. When tests are run, only the tests from the first test class (that is executed first) after the deployment, fail directly with 'Deployment failed', the rest of the tests that depend on this deployment are being executed.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug  9 00:36:00 2017
From: issues at jboss.org (Abhijit Humbe (JIRA))
Date: Wed, 9 Aug 2017 00:36:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2134) Arquillian test only
 disable web application didnt undeploy application
In-Reply-To: <JIRA.12706646.1502253321000@Atlassian.JIRA>
References: <JIRA.12706646.1502253321000@Atlassian.JIRA>
	<JIRA.12706646.1502253321637@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706646.1502253321000.85209.1502253360092@Atlassian.JIRA>

Abhijit Humbe created ARQ-2134:
----------------------------------

             Summary: Arquillian test only disable web application didnt undeploy application
                 Key: ARQ-2134
                 URL: https://issues.jboss.org/browse/ARQ-2134
             Project: Arquillian
          Issue Type: Bug
          Components: JBoss AS Containers
            Reporter: Abhijit Humbe
         Attachments: simple01892901.tar.gz

Arquillian is used to deploy an ear file, run it, and undeploy it from a remote server. When the test runs, it leaves the ear file in the server and it is disabled, but not undeployed.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug  9 04:09:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Wed, 9 Aug 2017 04:09:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2135)
 TransactionProviderNotFoundException for client side tests
In-Reply-To: <JIRA.12706672.1502266128000@Atlassian.JIRA>
References: <JIRA.12706672.1502266128000@Atlassian.JIRA>
	<JIRA.12706672.1502266128126@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706672.1502266128000.86025.1502266140265@Atlassian.JIRA>

Bartosz Majsak created ARQ-2135:
-----------------------------------

             Summary: TransactionProviderNotFoundException for client side tests
                 Key: ARQ-2135
                 URL: https://issues.jboss.org/browse/ARQ-2135
             Project: Arquillian
          Issue Type: Bug
          Components: Extension - Transaction
    Affects Versions: transaction_1.0.4
            Reporter: Bartosz Majsak


https://github.com/arquillian/arquillian-extension-transaction/issues/14



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug  9 04:10:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Wed, 9 Aug 2017 04:10:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2135)
 TransactionProviderNotFoundException for client side tests
In-Reply-To: <JIRA.12706672.1502266128000@Atlassian.JIRA>
References: <JIRA.12706672.1502266128000@Atlassian.JIRA>
	<JIRA.12706672.1502266128000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706672.1502266128000.86032.1502266200503@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak updated ARQ-2135:
--------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-extension-transaction/pull/15


> TransactionProviderNotFoundException for client side tests
> ----------------------------------------------------------
>
>                 Key: ARQ-2135
>                 URL: https://issues.jboss.org/browse/ARQ-2135
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Transaction
>    Affects Versions: transaction_1.0.4
>            Reporter: Bartosz Majsak
>
> https://github.com/arquillian/arquillian-extension-transaction/issues/14



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug  9 04:13:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Wed, 9 Aug 2017 04:13:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2135)
 TransactionProviderNotFoundException for client side tests
In-Reply-To: <JIRA.12706672.1502266128000@Atlassian.JIRA>
References: <JIRA.12706672.1502266128000@Atlassian.JIRA>
	<JIRA.12706672.1502266128000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706672.1502266128000.86052.1502266380603@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak updated ARQ-2135:
--------------------------------
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: transaction_1.0.5
       Resolution: Done


> TransactionProviderNotFoundException for client side tests
> ----------------------------------------------------------
>
>                 Key: ARQ-2135
>                 URL: https://issues.jboss.org/browse/ARQ-2135
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Transaction
>    Affects Versions: transaction_1.0.4
>            Reporter: Bartosz Majsak
>             Fix For: transaction_1.0.5
>
>
> https://github.com/arquillian/arquillian-extension-transaction/issues/14



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug  9 04:14:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Wed, 9 Aug 2017 04:14:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2135)
 TransactionProviderNotFoundException for client side tests
In-Reply-To: <JIRA.12706672.1502266128000@Atlassian.JIRA>
References: <JIRA.12706672.1502266128000@Atlassian.JIRA>
	<JIRA.12706672.1502266128000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706672.1502266128000.86067.1502266440183@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak closed ARQ-2135.
-------------------------------


> TransactionProviderNotFoundException for client side tests
> ----------------------------------------------------------
>
>                 Key: ARQ-2135
>                 URL: https://issues.jboss.org/browse/ARQ-2135
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Transaction
>    Affects Versions: transaction_1.0.4
>            Reporter: Bartosz Majsak
>             Fix For: transaction_1.0.5
>
>
> https://github.com/arquillian/arquillian-extension-transaction/issues/14



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Aug 10 04:02:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 10 Aug 2017 04:02:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-510) cglib is causing
 warnings in FieldAccessValidatorEnricher
In-Reply-To: <JIRA.12705319.1501250717000@Atlassian.JIRA>
References: <JIRA.12705319.1501250717000@Atlassian.JIRA>
	<JIRA.12705319.1501250717000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12705319.1501250717000.96951.1502352120299@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQGRA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQGRA-510:
----------------------------------
    Fix Version/s: 2.3.1


> cglib is causing warnings in FieldAccessValidatorEnricher
> ---------------------------------------------------------
>
>                 Key: ARQGRA-510
>                 URL: https://issues.jboss.org/browse/ARQGRA-510
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Vaclav Muzikar
>            Assignee: Matous Jobanek
>            Priority: Critical
>             Fix For: 2.3.1
>
>
> In Graphene 2.3.0, cglib dependency was updated to version 3.2.5.
> When using a Page Object, many warning messages (one for each Page Object) are printed to the log (which could then be literally flooded with those messages). This is probably caused by the cglib update.
> {noformat}
> Jul 28, 2017 3:52:42 PM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity
> WARNING: Package-friendly field 'CGLIB$FACTORY_DATA' found in org.test.TestPage$$EnhancerByGraphene$$260509ea. Direct access to fields outside of the declaring class is not allowed.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Aug 10 04:03:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 10 Aug 2017 04:03:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-510) cglib is causing
 warnings in FieldAccessValidatorEnricher
In-Reply-To: <JIRA.12705319.1501250717000@Atlassian.JIRA>
References: <JIRA.12705319.1501250717000@Atlassian.JIRA>
	<JIRA.12705319.1501250717000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12705319.1501250717000.96955.1502352180261@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQGRA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQGRA-510.
---------------------------------
    Resolution: Done


> cglib is causing warnings in FieldAccessValidatorEnricher
> ---------------------------------------------------------
>
>                 Key: ARQGRA-510
>                 URL: https://issues.jboss.org/browse/ARQGRA-510
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Vaclav Muzikar
>            Assignee: Matous Jobanek
>            Priority: Critical
>             Fix For: 2.3.1
>
>
> In Graphene 2.3.0, cglib dependency was updated to version 3.2.5.
> When using a Page Object, many warning messages (one for each Page Object) are printed to the log (which could then be literally flooded with those messages). This is probably caused by the cglib update.
> {noformat}
> Jul 28, 2017 3:52:42 PM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity
> WARNING: Package-friendly field 'CGLIB$FACTORY_DATA' found in org.test.TestPage$$EnhancerByGraphene$$260509ea. Direct access to fields outside of the declaring class is not allowed.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Aug 10 08:03:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Thu, 10 Aug 2017 08:03:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage
	work for Field
In-Reply-To: <JIRA.12501724.1380281456000@Atlassian.JIRA>
References: <JIRA.12501724.1380281456000@Atlassian.JIRA>
	<JIRA.12501724.1380281456000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501724.1380281456000.99005.1502366580435@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444441#comment-13444441 ] 

Vsevolod Golovanov edited comment on ARQGRA-382 at 8/10/17 8:02 AM:
--------------------------------------------------------------------

bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. -It also mirrors the default Drone instance scope- (Update: I forgot, the default is class scope.) (but I don't think these scopes should always be equated, though class scoped InitialPage certainly makes no sense with a method scoped Drone).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...

Update.
JUnit doesn't have a defined \@Test method execution order. In practice the order often changes between runs. Keeping this in mind, a BeforeClass-like InitialPage doesn't make much sense, unless all the tests somehow guarantee that they won't affect each other, even though they all execute on the same opened page? This is very dubious.
TestNG doesn't specify the execution order by default either, but has {{\@Test(priority, dependsOnGroups, dependsOnMethods)}}.
I think InitialPage on a field should just always be considered method-scoped (\@Test-scoped).


was (Author: vsevolodgolovanov):
bq. However, all other fields in tests preserve the state among tests, so Before would be an exception.
That seems worrisome, does this imply that the page instances behind \@Page fields survive between test methods? JUnit creates a new test class instance for each of the \@Test methods - each of those runs is supposed to be a self-contained independent execution unaffected by other runs. One method execution seems to be a proper natural scope for \@InitialPage too. -It also mirrors the default Drone instance scope- (Update: I forgot, the default is class scope.) (but I don't think these scopes should always be equated, though class scoped InitialPage certainly makes no sense with a method scoped Drone).

Maybe {{\@InitialPage static_field}} = BeforeClass, {{\@InitialPage instance_field}} = Before? Gotta not break parallel execution though...

> Make @InitialPage work for Field
> --------------------------------
>
>                 Key: ARQGRA-382
>                 URL: https://issues.jboss.org/browse/ARQGRA-382
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> While @InitialPage allows to be used on test class field, it does not do anything.
> {code}
> @InitialPage AddUserPage page;
> @Test
> void test() {
>     page.foo()
> }
> {code}
> raises
> {code}
> java.lang.NullPointerException: null
>         at com.acme.example.test.DroneTest.addUser(DroneTest.java:35)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Aug 10 08:23:00 2017
From: issues at jboss.org (Karel Piwko (JIRA))
Date: Thu, 10 Aug 2017 08:23:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-382) Make @InitialPage
	work for Field
In-Reply-To: <JIRA.12501724.1380281456000@Atlassian.JIRA>
References: <JIRA.12501724.1380281456000@Atlassian.JIRA>
	<JIRA.12501724.1380281456000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501724.1380281456000.99151.1502367780250@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447281#comment-13447281 ] 

Karel Piwko commented on ARQGRA-382:
------------------------------------

Vsevolod - haven't read through whole comment but I wanted to flag you can use @InSequence annotation with Arquillian to order tests:

http://arquillian.org/guides/getting_started_rinse_and_repeat/

> Make @InitialPage work for Field
> --------------------------------
>
>                 Key: ARQGRA-382
>                 URL: https://issues.jboss.org/browse/ARQGRA-382
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> While @InitialPage allows to be used on test class field, it does not do anything.
> {code}
> @InitialPage AddUserPage page;
> @Test
> void test() {
>     page.foo()
> }
> {code}
> raises
> {code}
> java.lang.NullPointerException: null
>         at com.acme.example.test.DroneTest.addUser(DroneTest.java:35)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Thu Aug 10 10:36:00 2017
From: issues at jboss.org (Neil Swartz (JIRA))
Date: Thu, 10 Aug 2017 10:36:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2134) Arquillian test only
 disable web application didnt undeploy application
In-Reply-To: <JIRA.12706646.1502253322000@Atlassian.JIRA>
References: <JIRA.12706646.1502253322000@Atlassian.JIRA>
	<JIRA.12706646.1502253322000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706646.1502253322000.102166.1502375760347@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447418#comment-13447418 ] 

Neil Swartz commented on ARQ-2134:
----------------------------------

I found this issue:
https://github.com/ingwarsw/arquillian-suite-extension/issues/13

In reading the code I see in ArchiveDeployer that it builds the plan, but does not call "andRemoveUndeployed()"
That might be the issue.
Could EAP 6.3 have automatically removed the ear, but Wildfly/EAP7 does not?


> Arquillian test only disable web application didnt undeploy application
> -----------------------------------------------------------------------
>
>                 Key: ARQ-2134
>                 URL: https://issues.jboss.org/browse/ARQ-2134
>             Project: Arquillian
>          Issue Type: Bug
>          Components: JBoss AS Containers
>            Reporter: Abhijit Humbe
>         Attachments: simple01892901.tar.gz
>
>
> Arquillian is used to deploy an ear file, run it, and undeploy it from a remote server. When the test runs, it leaves the ear file in the server and it is disabled, but not undeployed.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 08:54:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 08:54:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not
 reported with recent versions of TestNG
In-Reply-To: <JIRA.12683471.1490027817000@Atlassian.JIRA>
References: <JIRA.12683471.1490027817000@Atlassian.JIRA>
	<JIRA.12683471.1490027817000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683471.1490027817000.107374.1502456040665@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447894#comment-13447894 ] 

Bartosz Majsak commented on ARQ-2086:
-------------------------------------

There is a new version released, but not published yet to Maven Central. https://bintray.com/cbeust/maven/testng/6.12

With this, I can confirm that all works fine.

We have to wait however until the new version of TestNG lands in Maven Central :(

> Test failures not reported with recent versions of TestNG
> ---------------------------------------------------------
>
>                 Key: ARQ-2086
>                 URL: https://issues.jboss.org/browse/ARQ-2086
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.12.Final
>            Reporter: Gunnar Morling
>            Assignee: Dipak Pawar
>            Priority: Blocker
>
> When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing.
> A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug.
> There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 09:00:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 09:00:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2086) Test failures not
 reported with recent versions of TestNG
In-Reply-To: <JIRA.12683471.1490027817000@Atlassian.JIRA>
References: <JIRA.12683471.1490027817000@Atlassian.JIRA>
	<JIRA.12683471.1490027817000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683471.1490027817000.107423.1502456400494@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak updated ARQ-2086:
--------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-core/pull/134


> Test failures not reported with recent versions of TestNG
> ---------------------------------------------------------
>
>                 Key: ARQ-2086
>                 URL: https://issues.jboss.org/browse/ARQ-2086
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.12.Final
>            Reporter: Gunnar Morling
>            Assignee: Dipak Pawar
>            Priority: Blocker
>
> When using recent TestNG versions (> 6.8.21) with Arquillian, failing tests are accidentally reported as passing.
> A reproducer can be found at https://github.com/gunnarmorling/arquillian-testng-bug.
> There is a single test which is expected to fail, but it actually is reported as successful with TestNG 6.11. It is reported as failed as expected with 6.8.21. Run {{mvn clean install}} for reproducing.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 11:10:00 2017
From: issues at jboss.org (Neil Swartz (JIRA))
Date: Fri, 11 Aug 2017 11:10:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2134) Arquillian test only
 disable web application didnt undeploy application
In-Reply-To: <JIRA.12706646.1502253322000@Atlassian.JIRA>
References: <JIRA.12706646.1502253322000@Atlassian.JIRA>
	<JIRA.12706646.1502253322000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706646.1502253322000.108567.1502464200281@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448013#comment-13448013 ] 

Neil Swartz commented on ARQ-2134:
----------------------------------

It appears that 2.1.0.Beta1 of Arquillian fixes the issue.

> Arquillian test only disable web application didnt undeploy application
> -----------------------------------------------------------------------
>
>                 Key: ARQ-2134
>                 URL: https://issues.jboss.org/browse/ARQ-2134
>             Project: Arquillian
>          Issue Type: Bug
>          Components: JBoss AS Containers
>            Reporter: Abhijit Humbe
>         Attachments: simple01892901.tar.gz
>
>
> Arquillian is used to deploy an ear file, run it, and undeploy it from a remote server. When the test runs, it leaves the ear file in the server and it is disabled, but not undeployed.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 12:24:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 12:24:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2136) Add support to preserve
 original property value using placeholder
In-Reply-To: <JIRA.12707161.1502468617000@Atlassian.JIRA>
References: <JIRA.12707161.1502468617000@Atlassian.JIRA>
	<JIRA.12707161.1502468617069@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707161.1502468617000.109182.1502468640375@Atlassian.JIRA>

Bartosz Majsak created ARQ-2136:
-----------------------------------

             Summary: Add support to preserve original property value using placeholder
                 Key: ARQ-2136
                 URL: https://issues.jboss.org/browse/ARQ-2136
             Project: Arquillian
          Issue Type: Enhancement
            Reporter: Bartosz Majsak
            Priority: Minor


https://github.com/arquillian/arquillian-core/pull/122



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 12:24:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 12:24:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2136) Add support to preserve
 original property value using placeholder
In-Reply-To: <JIRA.12707161.1502468617000@Atlassian.JIRA>
References: <JIRA.12707161.1502468617000@Atlassian.JIRA>
	<JIRA.12707161.1502468617000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707161.1502468617000.109185.1502468640489@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak updated ARQ-2136:
--------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-core/pull/122


> Add support to preserve original property value using placeholder
> -----------------------------------------------------------------
>
>                 Key: ARQ-2136
>                 URL: https://issues.jboss.org/browse/ARQ-2136
>             Project: Arquillian
>          Issue Type: Enhancement
>            Reporter: Bartosz Majsak
>            Priority: Minor
>
> https://github.com/arquillian/arquillian-core/pull/122



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 12:24:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 12:24:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2136) Add support to preserve
 original property value using placeholder
In-Reply-To: <JIRA.12707161.1502468617000@Atlassian.JIRA>
References: <JIRA.12707161.1502468617000@Atlassian.JIRA>
	<JIRA.12707161.1502468617000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707161.1502468617000.109189.1502468640662@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak updated ARQ-2136:
--------------------------------
    Component/s: Configuration


> Add support to preserve original property value using placeholder
> -----------------------------------------------------------------
>
>                 Key: ARQ-2136
>                 URL: https://issues.jboss.org/browse/ARQ-2136
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Configuration
>            Reporter: Bartosz Majsak
>            Priority: Minor
>
> https://github.com/arquillian/arquillian-core/pull/122



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 12:25:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 12:25:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2136) Add support to preserve
 original property value using placeholder
In-Reply-To: <JIRA.12707161.1502468617000@Atlassian.JIRA>
References: <JIRA.12707161.1502468617000@Atlassian.JIRA>
	<JIRA.12707161.1502468617000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707161.1502468617000.109192.1502468700157@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak updated ARQ-2136:
--------------------------------
    Affects Version/s: 1.1.13.Final


> Add support to preserve original property value using placeholder
> -----------------------------------------------------------------
>
>                 Key: ARQ-2136
>                 URL: https://issues.jboss.org/browse/ARQ-2136
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Configuration
>    Affects Versions: 1.1.13.Final
>            Reporter: Bartosz Majsak
>            Priority: Minor
>
> https://github.com/arquillian/arquillian-core/pull/122



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 12:25:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 12:25:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2136) Add support to preserve
 original property value using placeholder
In-Reply-To: <JIRA.12707161.1502468617000@Atlassian.JIRA>
References: <JIRA.12707161.1502468617000@Atlassian.JIRA>
	<JIRA.12707161.1502468617000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707161.1502468617000.109195.1502468700224@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak reassigned ARQ-2136:
-----------------------------------

    Assignee: Bartosz Majsak


> Add support to preserve original property value using placeholder
> -----------------------------------------------------------------
>
>                 Key: ARQ-2136
>                 URL: https://issues.jboss.org/browse/ARQ-2136
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Configuration
>    Affects Versions: 1.1.13.Final
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>            Priority: Minor
>
> https://github.com/arquillian/arquillian-core/pull/122



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 11 12:30:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Fri, 11 Aug 2017 12:30:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2136) Add support to preserve
 original property value using placeholder
In-Reply-To: <JIRA.12707161.1502468617000@Atlassian.JIRA>
References: <JIRA.12707161.1502468617000@Atlassian.JIRA>
	<JIRA.12707161.1502468617000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707161.1502468617000.109202.1502469000512@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak updated ARQ-2136:
--------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Add support to preserve original property value using placeholder
> -----------------------------------------------------------------
>
>                 Key: ARQ-2136
>                 URL: https://issues.jboss.org/browse/ARQ-2136
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Configuration
>    Affects Versions: 1.1.13.Final
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>            Priority: Minor
>
> https://github.com/arquillian/arquillian-core/pull/122



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Aug 14 08:58:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 14 Aug 2017 08:58:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2137) Update Selenium to 3.5.0
In-Reply-To: <JIRA.12707338.1502715433000@Atlassian.JIRA>
References: <JIRA.12707338.1502715433000@Atlassian.JIRA>
	<JIRA.12707338.1502715433468@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707338.1502715433000.114146.1502715481154@Atlassian.JIRA>

Matous Jobanek created ARQ-2137:
-----------------------------------

             Summary: Update Selenium to 3.5.0
                 Key: ARQ-2137
                 URL: https://issues.jboss.org/browse/ARQ-2137
             Project: Arquillian
          Issue Type: Component Upgrade
          Components: Extension - Drone
    Affects Versions: drone_2.3.1
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: drone_2.4.0






--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Aug 14 09:02:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 14 Aug 2017 09:02:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2132) Support for
 FirefoxOptions and SafariOptions in Drone
In-Reply-To: <JIRA.12706022.1501771005000@Atlassian.JIRA>
References: <JIRA.12706022.1501771005000@Atlassian.JIRA>
	<JIRA.12706022.1501771005000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706022.1501771005000.114251.1502715721592@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2132:
--------------------------------
    Fix Version/s: drone_2.4.0


> Support for FirefoxOptions and SafariOptions in Drone
> -----------------------------------------------------
>
>                 Key: ARQ-2132
>                 URL: https://issues.jboss.org/browse/ARQ-2132
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>            Assignee: Vaclav Muzikar
>             Fix For: drone_2.4.0
>
>
> FirefoxOptions are mainly needed for setting up the GeckoDriver logger level.
> SafariOptions are needed for testing with Safari Technical Preview.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Aug 14 09:02:02 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 14 Aug 2017 09:02:02 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2129) Operations Binary
 download/extraction/marking as executable are not thread-safe
In-Reply-To: <JIRA.12702871.1500552890000@Atlassian.JIRA>
References: <JIRA.12702871.1500552890000@Atlassian.JIRA>
	<JIRA.12702871.1500552890000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12702871.1500552890000.114266.1502715722398@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2129:
--------------------------------
    Fix Version/s: drone_2.4.0
                       (was: drone_2.3.2)


> Operations Binary download/extraction/marking as executable are not thread-safe
> -------------------------------------------------------------------------------
>
>                 Key: ARQ-2129
>                 URL: https://issues.jboss.org/browse/ARQ-2129
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>    Affects Versions: drone_2.3.1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 18 07:41:00 2017
From: issues at jboss.org (Thomas Jodes (JIRA))
Date: Fri, 18 Aug 2017 07:41:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2138) Conduct DBUnit
 properties from arquillian-persistence
In-Reply-To: <JIRA.12708002.1503056442000@Atlassian.JIRA>
References: <JIRA.12708002.1503056442000@Atlassian.JIRA>
	<JIRA.12708002.1503056442521@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708002.1503056442000.140834.1503056460195@Atlassian.JIRA>

Thomas Jodes created ARQ-2138:
---------------------------------

             Summary: Conduct DBUnit properties from arquillian-persistence
                 Key: ARQ-2138
                 URL: https://issues.jboss.org/browse/ARQ-2138
             Project: Arquillian
          Issue Type: Feature Request
          Components: Extension - Persistence
    Affects Versions: 1.0.0.CR7
            Reporter: Thomas Jodes
            Assignee: Bartosz Majsak


As an arquillian-persistence user, I want to access all DBUnit properties from the arquillian-persistence configuration. 

Only a few DBUnit properties like caseSensitiveTablesNames are conducted from the arq-persisence configuration. In my case, I've got yml-Data with columns of empty content.
I'd like to set the DBUnit property "allowEmptyFields" through the arquillian persistence config as follows:

  <extension qualifier="persistence-dbunit">
        <property name="defaultDataSetFormat">YAML</property>
        <property name="allowEmptyFields">true</property>
  </extension>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Fri Aug 18 08:43:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 18 Aug 2017 08:43:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2137) Update Selenium to 3.5.1
In-Reply-To: <JIRA.12707338.1502715433000@Atlassian.JIRA>
References: <JIRA.12707338.1502715433000@Atlassian.JIRA>
	<JIRA.12707338.1502715433000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707338.1502715433000.141256.1503060180514@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2137:
--------------------------------
    Summary: Update Selenium to 3.5.1  (was: Update Selenium to 3.5.0)


> Update Selenium to 3.5.1
> ------------------------
>
>                 Key: ARQ-2137
>                 URL: https://issues.jboss.org/browse/ARQ-2137
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.3.1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug 23 09:44:00 2017
From: issues at jboss.org (Vaclav Muzikar (JIRA))
Date: Wed, 23 Aug 2017 09:44:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2132) Support for
 FirefoxOptions and SafariOptions in Drone
In-Reply-To: <JIRA.12706022.1501771005000@Atlassian.JIRA>
References: <JIRA.12706022.1501771005000@Atlassian.JIRA>
	<JIRA.12706022.1501771005000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706022.1501771005000.160324.1503495840224@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453130#comment-13453130 ] 

Vaclav Muzikar commented on ARQ-2132:
-------------------------------------

[~mjobanek] I think we can close this. Correct?

> Support for FirefoxOptions and SafariOptions in Drone
> -----------------------------------------------------
>
>                 Key: ARQ-2132
>                 URL: https://issues.jboss.org/browse/ARQ-2132
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>            Assignee: Vaclav Muzikar
>             Fix For: drone_2.4.0
>
>
> FirefoxOptions are mainly needed for setting up the GeckoDriver logger level.
> SafariOptions are needed for testing with Safari Technical Preview.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug 23 09:47:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 23 Aug 2017 09:47:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2137) Update Selenium to 3.5.1
In-Reply-To: <JIRA.12707338.1502715433000@Atlassian.JIRA>
References: <JIRA.12707338.1502715433000@Atlassian.JIRA>
	<JIRA.12707338.1502715433000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12707338.1502715433000.160342.1503496020343@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQ-2137.
-------------------------------
    Resolution: Done


> Update Selenium to 3.5.1
> ------------------------
>
>                 Key: ARQ-2137
>                 URL: https://issues.jboss.org/browse/ARQ-2137
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.3.1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug 23 09:47:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 23 Aug 2017 09:47:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2129) Operations Binary
 download/extraction/marking as executable are not thread-safe
In-Reply-To: <JIRA.12702871.1500552890000@Atlassian.JIRA>
References: <JIRA.12702871.1500552890000@Atlassian.JIRA>
	<JIRA.12702871.1500552890000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12702871.1500552890000.160347.1503496020603@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQ-2129.
-------------------------------
    Resolution: Done


> Operations Binary download/extraction/marking as executable are not thread-safe
> -------------------------------------------------------------------------------
>
>                 Key: ARQ-2129
>                 URL: https://issues.jboss.org/browse/ARQ-2129
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>    Affects Versions: drone_2.3.1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug 23 09:48:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 23 Aug 2017 09:48:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2132) Support for
 FirefoxOptions and SafariOptions in Drone
In-Reply-To: <JIRA.12706022.1501771005000@Atlassian.JIRA>
References: <JIRA.12706022.1501771005000@Atlassian.JIRA>
	<JIRA.12706022.1501771005000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12706022.1501771005000.160357.1503496080769@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQ-2132.
-------------------------------
    Resolution: Done


Sure, I thought that I did it, but I probably forgot. 
Thanks for pointing this out [~vmuzikar]

> Support for FirefoxOptions and SafariOptions in Drone
> -----------------------------------------------------
>
>                 Key: ARQ-2132
>                 URL: https://issues.jboss.org/browse/ARQ-2132
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>            Assignee: Vaclav Muzikar
>             Fix For: drone_2.4.0
>
>
> FirefoxOptions are mainly needed for setting up the GeckoDriver logger level.
> SafariOptions are needed for testing with Safari Technical Preview.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug 23 12:01:02 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 23 Aug 2017 12:01:02 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2139) Drone should support
 authenticated GH requests
In-Reply-To: <JIRA.12708547.1503504055000@Atlassian.JIRA>
References: <JIRA.12708547.1503504055000@Atlassian.JIRA>
	<JIRA.12708547.1503504055572@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708547.1503504055000.161553.1503504062364@Atlassian.JIRA>

Matous Jobanek created ARQ-2139:
-----------------------------------

             Summary: Drone should support authenticated GH requests
                 Key: ARQ-2139
                 URL: https://issues.jboss.org/browse/ARQ-2139
             Project: Arquillian
          Issue Type: Feature Request
          Components: Extension - Drone
    Affects Versions: drone_2.4.0
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: drone_2.4.1


Otherwise, it is easy to reach GH limit in larger CI environment.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug 23 12:03:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 23 Aug 2017 12:03:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2139) Drone should support
 authenticated GH requests
In-Reply-To: <JIRA.12708547.1503504056000@Atlassian.JIRA>
References: <JIRA.12708547.1503504056000@Atlassian.JIRA>
	<JIRA.12708547.1503504056000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708547.1503504056000.161555.1503504180380@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2139:
--------------------------------
    Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/108


> Drone should support authenticated GH requests
> ----------------------------------------------
>
>                 Key: ARQ-2139
>                 URL: https://issues.jboss.org/browse/ARQ-2139
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>    Affects Versions: drone_2.4.0
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.1
>
>
> Otherwise, it is easy to reach GH limit in larger CI environment.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Wed Aug 23 12:03:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 23 Aug 2017 12:03:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2139) Drone should support
 authenticated GH requests
In-Reply-To: <JIRA.12708547.1503504056000@Atlassian.JIRA>
References: <JIRA.12708547.1503504056000@Atlassian.JIRA>
	<JIRA.12708547.1503504056000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708547.1503504056000.161561.1503504180646@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQ-2139.
-------------------------------
    Resolution: Done


> Drone should support authenticated GH requests
> ----------------------------------------------
>
>                 Key: ARQ-2139
>                 URL: https://issues.jboss.org/browse/ARQ-2139
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>    Affects Versions: drone_2.4.0
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.4.1
>
>
> Otherwise, it is easy to reach GH limit in larger CI environment.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Aug 28 05:34:00 2017
From: issues at jboss.org (Vaclav Muzikar (JIRA))
Date: Mon, 28 Aug 2017 05:34:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2140) Support for specifying
 the architecture of the binary for IE driver
In-Reply-To: <JIRA.12708943.1503912832000@Atlassian.JIRA>
References: <JIRA.12708943.1503912832000@Atlassian.JIRA>
	<JIRA.12708943.1503912832691@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708943.1503912832000.175750.1503912840144@Atlassian.JIRA>

Vaclav Muzikar created ARQ-2140:
-----------------------------------

             Summary: Support for specifying the architecture of the binary for IE driver
                 Key: ARQ-2140
                 URL: https://issues.jboss.org/browse/ARQ-2140
             Project: Arquillian
          Issue Type: Enhancement
          Components: Extension - Drone
            Reporter: Vaclav Muzikar


When automatically downloading the IE driver binary, it should be possible to specify the target architecture.

64 bit version of the IE driver is having some issues with some IE versions, specifically the {{sendKeys}} method is very slow. Therefore it's recommended to use the 32 bit version of the driver.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Aug 28 05:37:00 2017
From: issues at jboss.org (Vaclav Muzikar (JIRA))
Date: Mon, 28 Aug 2017 05:37:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2140) Support for specifying
 the architecture for IE driver binary
In-Reply-To: <JIRA.12708943.1503912833000@Atlassian.JIRA>
References: <JIRA.12708943.1503912833000@Atlassian.JIRA>
	<JIRA.12708943.1503912833000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708943.1503912833000.175756.1503913020217@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vaclav Muzikar updated ARQ-2140:
--------------------------------
    Summary: Support for specifying the architecture for IE driver binary  (was: Support for specifying the architecture of the binary for IE driver)


> Support for specifying the architecture for IE driver binary
> ------------------------------------------------------------
>
>                 Key: ARQ-2140
>                 URL: https://issues.jboss.org/browse/ARQ-2140
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>
> When automatically downloading the IE driver binary, it should be possible to specify the target architecture.
> 64 bit version of the IE driver is having some issues with some IE versions, specifically the {{sendKeys}} method is very slow. Therefore it's recommended to use the 32 bit version of the driver.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)

From issues at jboss.org  Mon Aug 28 06:18:00 2017
From: issues at jboss.org (Vaclav Muzikar (JIRA))
Date: Mon, 28 Aug 2017 06:18:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2140) Support for specifying
 the architecture for IE driver binary
In-Reply-To: <JIRA.12708943.1503912833000@Atlassian.JIRA>
References: <JIRA.12708943.1503912833000@Atlassian.JIRA>
	<JIRA.12708943.1503912833000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12708943.1503912833000.176010.1503915480115@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vaclav Muzikar updated ARQ-2140:
--------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/110


> Support for specifying the architecture for IE driver binary
> ------------------------------------------------------------
>
>                 Key: ARQ-2140
>                 URL: https://issues.jboss.org/browse/ARQ-2140
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>            Reporter: Vaclav Muzikar
>
> When automatically downloading the IE driver binary, it should be possible to specify the target architecture.
> 64 bit version of the IE driver is having some issues with some IE versions, specifically the {{sendKeys}} method is very slow. Therefore it's recommended to use the 32 bit version of the driver.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)