From issues at jboss.org  Mon Mar  6 03:52:00 2017
From: issues at jboss.org (Jan Hrcek (JIRA))
Date: Mon, 6 Mar 2017 03:52:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300329@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.9555.1488790320368@Atlassian.JIRA>

Jan Hrcek created ARQGRA-497:
--------------------------------

             Summary: Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
                 Key: ARQGRA-497
                 URL: https://issues.jboss.org/browse/ARQGRA-497
             Project: Arquillian Graphene
          Issue Type: Bug
          Components: api
    Affects Versions: 2.1.0.Final
            Reporter: Jan Hrcek
            Priority: Blocker


I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
When instantiating browser I see the following exception:

{code:java}
Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
{code}


This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Mon Mar  6 09:26:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 6 Mar 2017 09:26:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2081) Upgrade to Selenium
	3.2.0
In-Reply-To: <JIRA.12680297.1488810305000@Atlassian.JIRA>
References: <JIRA.12680297.1488810305000@Atlassian.JIRA>
	<JIRA.12680297.1488810305008@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680297.1488810305000.14947.1488810360499@Atlassian.JIRA>

Matous Jobanek created ARQ-2081:
-----------------------------------

             Summary: Upgrade to Selenium 3.2.0
                 Key: ARQ-2081
                 URL: https://issues.jboss.org/browse/ARQ-2081
             Project: Arquillian
          Issue Type: Component Upgrade
          Components: Extension - Drone
    Affects Versions: drone_2.1.0.Alpha1
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: drone_2.1.0.Alpha2






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

From issues at jboss.org  Mon Mar  6 10:37:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 6 Mar 2017 10:37:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.16864.1488814620716@Atlassian.JIRA>


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

Matous Jobanek reassigned ARQGRA-497:
-------------------------------------

    Assignee: Matous Jobanek


> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Mon Mar  6 10:39:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 6 Mar 2017 10:39:01 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.16914.1488814741062@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-497:
---------------------------------------

Hi, thanks for reporting this.
This week, I'm going to fix this and release new versions of both Drone and Graphene that will be compatible with the latest version of selenium.

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Mon Mar  6 12:21:00 2017
From: issues at jboss.org (Abel Salgado Romero (JIRA))
Date: Mon, 6 Mar 2017 12:21:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2082) "Could not inject
 members" when running inside glassfish-embedded-3.1
In-Reply-To: <JIRA.12680354.1488820817000@Atlassian.JIRA>
References: <JIRA.12680354.1488820817000@Atlassian.JIRA>
	<JIRA.12680354.1488820817598@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680354.1488820817000.18404.1488820860418@Atlassian.JIRA>

Abel Salgado Romero created ARQ-2082:
----------------------------------------

             Summary: "Could not inject members" when running inside glassfish-embedded-3.1
                 Key: ARQ-2082
                 URL: https://issues.jboss.org/browse/ARQ-2082
             Project: Arquillian
          Issue Type: Feature Request
          Components: GlassFish Containers
    Affects Versions: 1.1.12.Final
         Environment: payara.micro= 4.1.1.171.0.1
arquillian.version = 1.1.12.Final
glassfish-embedded-3.1= 1.0.0.Final
            Reporter: Abel Salgado Romero


I have a project with some simple Rest services a some beans (with @ApplicationScoped) and a test that runs correctly when {@Deployment(testable = false)}.
However, if I set {testable = true} and try to retrive some component in the test, for instance:
{quote}
@Inject
private UserServiceImpl userService;
{quote}

Test fails with the message
{quote}
java.lang.RuntimeException: Could not inject members

	at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:135)
	at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:78)
...
Caused by: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001408: Unsatisfied dependencies for type HelloWorldResource with qualifiers @Default
  at injection point [BackedAnnotatedField] @Inject private com..payara.HelloTest.helloWorldResource
  at com..payara.HelloTest.helloWorldResource(HelloTest.java:0)

{quote}

Notes:
? Same code runs (with appropriate changes) on Wildfly-swarm
? Just in case it could be related, I have a multipart upload service, so I need to initialize the components like this:
{quote}
@ApplicationPath("/app/v1/")
public class DemoPayaraApplication extends ResourceConfig {
    public DemoPayaraApplication() {
        packages("com.everis.payara");
        register(MultiPartFeature.class);
    }
}
{quote}
And add additional dpendencies
{quote}
    <dependency>
      <groupId>org.glassfish.jersey.media</groupId>
      <artifactId>jersey-media-multipart</artifactId>
      <version>2.25.1</version>
      <scope>provided</scope>
    </dependency>
{quote}



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


From issues at jboss.org  Tue Mar  7 12:46:00 2017
From: issues at jboss.org (S Haster (JIRA))
Date: Tue, 7 Mar 2017 12:46:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.29085.1488908760612@Atlassian.JIRA>


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

S Haster commented on ARQGRA-497:
---------------------------------

We are also running into this problem with graphene-webdriver impl. Great to see you are already planning a new version of graphene :+1:

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Tue Mar  7 12:46:00 2017
From: issues at jboss.org (S Haster (JIRA))
Date: Tue, 7 Mar 2017 12:46:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.29089.1488908760689@Atlassian.JIRA>


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

S Haster edited comment on ARQGRA-497 at 3/7/17 12:45 PM:
----------------------------------------------------------

We are also running into this problem with graphene-webdriver impl. Great to see you are already planning a new version of graphene (y)


was (Author: buurmansven):
We are also running into this problem with graphene-webdriver impl. Great to see you are already planning a new version of graphene :+1:

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Wed Mar  8 03:34:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 8 Mar 2017 03:34:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2081) Upgrade to Selenium
	3.3.0
In-Reply-To: <JIRA.12680297.1488810305000@Atlassian.JIRA>
References: <JIRA.12680297.1488810305000@Atlassian.JIRA>
	<JIRA.12680297.1488810305000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680297.1488810305000.31896.1488962040126@Atlassian.JIRA>


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

Matous Jobanek updated ARQ-2081:
--------------------------------
    Summary: Upgrade to Selenium 3.3.0  (was: Upgrade to Selenium 3.2.0)


> Upgrade to Selenium 3.3.0
> -------------------------
>
>                 Key: ARQ-2081
>                 URL: https://issues.jboss.org/browse/ARQ-2081
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Alpha2
>
>




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

From issues at jboss.org  Wed Mar  8 14:51:01 2017
From: issues at jboss.org (Emond Papegaaij (JIRA))
Date: Wed, 8 Mar 2017 14:51:01 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.38477.1489002661432@Atlassian.JIRA>


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

Emond Papegaaij updated ARQGRA-497:
-----------------------------------
    Attachment: drone.diff
                graphene.diff


> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Wed Mar  8 14:58:00 2017
From: issues at jboss.org (Emond Papegaaij (JIRA))
Date: Wed, 8 Mar 2017 14:58:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.38498.1489003080187@Atlassian.JIRA>


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

Emond Papegaaij commented on ARQGRA-497:
----------------------------------------

The situation is a bit more complex than only a removed method. In 3.1.0 the Selenium team broke binary compatibility of both WebDriverWait.until methods (Function and Predicate). In 3.2.0 the one with the Predicate was removed. Also in 3.2.0, the Actions class was refactored, rendering it useless when using the now deprecated constructor.

I've attached patches for both drone and graphene to get the build working again. I didn't touch the animal sniffer, which is failing. This probably because Selenium now requires Java 8.

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Wed Mar  8 15:59:00 2017
From: issues at jboss.org (Emond Papegaaij (JIRA))
Date: Wed, 8 Mar 2017 15:59:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.38657.1489006740179@Atlassian.JIRA>


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

Emond Papegaaij edited comment on ARQGRA-497 at 3/8/17 3:58 PM:
----------------------------------------------------------------

The situation is a bit more complex than only a removed method. In 3.1.0 the Selenium team broke binary compatibility of both WebDriverWait.until methods (Function and Predicate). In 3.2.0 the one with the Predicate was removed. Also in 3.2.0, the Actions class was refactored, rendering it useless when using the now deprecated constructor.

I've attached patches for both drone and graphene to get the build working again. I didn't touch the animal sniffer, which is failing. This probably is because Selenium now requires Java 8.


was (Author: papegaaij):
The situation is a bit more complex than only a removed method. In 3.1.0 the Selenium team broke binary compatibility of both WebDriverWait.until methods (Function and Predicate). In 3.2.0 the one with the Predicate was removed. Also in 3.2.0, the Actions class was refactored, rendering it useless when using the now deprecated constructor.

I've attached patches for both drone and graphene to get the build working again. I didn't touch the animal sniffer, which is failing. This probably because Selenium now requires Java 8.

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 06:13:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 06:13:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2083) Upgrade to
 arquillian-phantom-driver 1.2.1.1
In-Reply-To: <JIRA.12680884.1489057959000@Atlassian.JIRA>
References: <JIRA.12680884.1489057959000@Atlassian.JIRA>
	<JIRA.12680884.1489057959549@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680884.1489057959000.41725.1489057980966@Atlassian.JIRA>

Matous Jobanek created ARQ-2083:
-----------------------------------

             Summary: Upgrade to arquillian-phantom-driver 1.2.1.1
                 Key: ARQ-2083
                 URL: https://issues.jboss.org/browse/ARQ-2083
             Project: Arquillian
          Issue Type: Component Upgrade
          Components: Extension - Drone
    Affects Versions: drone_2.1.0.Alpha1
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: drone_2.1.0.Alpha2






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

From issues at jboss.org  Thu Mar  9 08:49:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 08:49:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.43765.1489067340701@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-497:
---------------------------------------

Hi all,
thanks for your input folks. 
I have some migration already done:
Drone: https://github.com/MatousJobanek/arquillian-extension-drone/tree/develop-alpha2
Graphene: https://github.com/MatousJobanek/arquillian-graphene/tree/develop-2.2
and if I compare the changes and your diffs, then I think that we are on the same page.
The only problem that I have is with maven central sync. I've released arquillian-phantom-driver 1.2.1.1 and selenium-bom 3.3.0 in last two days, but they haven't been synced with central yet (which has happened for the first time). 
I'll probably release both Drone 2.1.Alpha2 and Graphene 2.2.0 today and I'll hope that there is nothing messed up in the synced functionality. 
If it is not synced with central correctly, then all the releases should be available here https://repository.jboss.org/nexus/service/local/repositories/releases/content/ 

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 08:49:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 08:49:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.43776.1489067340956@Atlassian.JIRA>


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

Matous Jobanek edited comment on ARQGRA-497 at 3/9/17 8:48 AM:
---------------------------------------------------------------

Hi all,
thanks for your input folks. 
I have some migration already done:
Drone: https://github.com/MatousJobanek/arquillian-extension-drone/tree/develop-alpha2
Graphene: https://github.com/MatousJobanek/arquillian-graphene/tree/develop-2.2
and if I compare the changes and your diffs, then I think that we are on the same page.
The only problem that I have is with maven central sync. I've released arquillian-phantom-driver 1.2.1.1 and selenium-bom 3.3.0 in last two days, but they haven't been synced with central yet (which has happened for the first time). 
I'll probably release both Drone 2.1.0.Alpha2 and Graphene 2.2.0 today and I'll hope that there is nothing messed up in the synced functionality. 
If it is not synced with central correctly, then all the releases should be available here https://repository.jboss.org/nexus/service/local/repositories/releases/content/ 


was (Author: mjobanek):
Hi all,
thanks for your input folks. 
I have some migration already done:
Drone: https://github.com/MatousJobanek/arquillian-extension-drone/tree/develop-alpha2
Graphene: https://github.com/MatousJobanek/arquillian-graphene/tree/develop-2.2
and if I compare the changes and your diffs, then I think that we are on the same page.
The only problem that I have is with maven central sync. I've released arquillian-phantom-driver 1.2.1.1 and selenium-bom 3.3.0 in last two days, but they haven't been synced with central yet (which has happened for the first time). 
I'll probably release both Drone 2.1.Alpha2 and Graphene 2.2.0 today and I'll hope that there is nothing messed up in the synced functionality. 
If it is not synced with central correctly, then all the releases should be available here https://repository.jboss.org/nexus/service/local/repositories/releases/content/ 

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 09:00:00 2017
From: issues at jboss.org (Emond Papegaaij (JIRA))
Date: Thu, 9 Mar 2017 09:00:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.44033.1489068000789@Atlassian.JIRA>


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

Emond Papegaaij commented on ARQGRA-497:
----------------------------------------

The diffs are very similar. I did however update some test classes in drone as well (switching from guava to java function). Thanks for the work so far.

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 09:03:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 09:03:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-498) Upgrade to Drone
 2.1.0.Alpha2 (Selenium 3.3.0)
In-Reply-To: <JIRA.12680964.1489068165000@Atlassian.JIRA>
References: <JIRA.12680964.1489068165000@Atlassian.JIRA>
	<JIRA.12680964.1489068165013@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680964.1489068165000.44057.1489068180466@Atlassian.JIRA>

Matous Jobanek created ARQGRA-498:
-------------------------------------

             Summary: Upgrade to Drone 2.1.0.Alpha2 (Selenium 3.3.0)
                 Key: ARQGRA-498
                 URL: https://issues.jboss.org/browse/ARQGRA-498
             Project: Arquillian Graphene
          Issue Type: Component Upgrade
    Affects Versions: 2.1.0.Final
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: 2.2.0






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

From issues at jboss.org  Thu Mar  9 09:06:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 09:06:01 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-499) Update jboss-parent
 to 22 and fix checkstyle
In-Reply-To: <JIRA.12680966.1489068342000@Atlassian.JIRA>
References: <JIRA.12680966.1489068342000@Atlassian.JIRA>
	<JIRA.12680966.1489068342006@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680966.1489068342000.44120.1489068361033@Atlassian.JIRA>

Matous Jobanek created ARQGRA-499:
-------------------------------------

             Summary: Update jboss-parent to 22 and fix checkstyle
                 Key: ARQGRA-499
                 URL: https://issues.jboss.org/browse/ARQGRA-499
             Project: Arquillian Graphene
          Issue Type: Component Upgrade
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: 2.2.0


update jboss-parent to 22 and remove the checkstyle version (so it uses the version specified in jboss-parent) + necessary modification to meet the checkstyle requirements



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

From issues at jboss.org  Thu Mar  9 09:18:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 09:18:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.44249.1489069080216@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-497:
---------------------------------------

[~papegaaij] me too, but in the next commit: https://github.com/MatousJobanek/arquillian-extension-drone/commit/2fcb507cb541a368e302106675ba6bf7852510f7#diff-41cc1c9f6daf102b677ae373a9bad206R20

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 09:23:00 2017
From: issues at jboss.org (Emond Papegaaij (JIRA))
Date: Thu, 9 Mar 2017 09:23:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.44308.1489069380401@Atlassian.JIRA>


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

Emond Papegaaij commented on ARQGRA-497:
----------------------------------------

Ok, great, then you've got all the changes I've made plus some more.

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 14:45:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 14:45:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.46770.1489088700292@Atlassian.JIRA>


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

Matous Jobanek updated ARQGRA-497:
----------------------------------
    Fix Version/s: 2.2.0


> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>             Fix For: 2.2.0
>
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 14:50:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 14:50:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.46776.1489089000262@Atlassian.JIRA>


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

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


fixed by:
in Drone:
https://github.com/arquillian/arquillian-extension-drone/commit/2fcb507cb541a368e302106675ba6bf7852510f7

in Graphene:
 https://github.com/arquillian/arquillian-graphene/commit/b7bf39cbeed0461a70ecf96861b95ee22f54f39a
 https://github.com/arquillian/arquillian-graphene/commit/0b1b0a088f90cd8611f7764a98a69486178b0517
 https://github.com/arquillian/arquillian-graphene/commit/b3d10bb6b47cc57ff5370bfb749fc2b1b4154951

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>             Fix For: 2.2.0
>
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Thu Mar  9 14:52:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 14:52:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-498) Upgrade to Drone
 2.1.0.Alpha2 (Selenium 3.3.0)
In-Reply-To: <JIRA.12680964.1489068165000@Atlassian.JIRA>
References: <JIRA.12680964.1489068165000@Atlassian.JIRA>
	<JIRA.12680964.1489068165000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680964.1489068165000.46779.1489089120168@Atlassian.JIRA>


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

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


pushed upstream in: https://github.com/arquillian/arquillian-graphene/commit/b7bf39cbeed0461a70ecf96861b95ee22f54f39a

> Upgrade to Drone 2.1.0.Alpha2 (Selenium 3.3.0)
> ----------------------------------------------
>
>                 Key: ARQGRA-498
>                 URL: https://issues.jboss.org/browse/ARQGRA-498
>             Project: Arquillian Graphene
>          Issue Type: Component Upgrade
>    Affects Versions: 2.1.0.Final
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: 2.2.0
>
>




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

From issues at jboss.org  Thu Mar  9 14:52:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 14:52:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-499) Update jboss-parent
 to 22 and fix checkstyle
In-Reply-To: <JIRA.12680966.1489068342000@Atlassian.JIRA>
References: <JIRA.12680966.1489068342000@Atlassian.JIRA>
	<JIRA.12680966.1489068342000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680966.1489068342000.46780.1489089120187@Atlassian.JIRA>


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

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


pushed upstream in https://github.com/arquillian/arquillian-graphene/commit/0b1b0a088f90cd8611f7764a98a69486178b0517

> Update jboss-parent to 22 and fix checkstyle
> --------------------------------------------
>
>                 Key: ARQGRA-499
>                 URL: https://issues.jboss.org/browse/ARQGRA-499
>             Project: Arquillian Graphene
>          Issue Type: Component Upgrade
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: 2.2.0
>
>
> update jboss-parent to 22 and remove the checkstyle version (so it uses the version specified in jboss-parent) + necessary modification to meet the checkstyle requirements



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

From issues at jboss.org  Thu Mar  9 14:55:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 14:55:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-495) Scheme and URL
 properties might be used in incompatible ways
In-Reply-To: <JIRA.12671802.1484744398000@Atlassian.JIRA>
References: <JIRA.12671802.1484744398000@Atlassian.JIRA>
	<JIRA.12671802.1484744398000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12671802.1484744398000.46790.1489089300152@Atlassian.JIRA>


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

Matous Jobanek reassigned ARQGRA-495:
-------------------------------------

    Assignee: Alex Soto


> Scheme and URL properties might be used in incompatible ways
> ------------------------------------------------------------
>
>                 Key: ARQGRA-495
>                 URL: https://issues.jboss.org/browse/ARQGRA-495
>             Project: Arquillian Graphene
>          Issue Type: Bug
>            Reporter: Alex Soto
>            Assignee: Alex Soto
>            Priority: Minor
>
> Graphene allows you to configure two properties, scheme and url. The problem is that Scheme might be http, https, ... and the URL instead of being the host + port + context definition, it is a full URL. SO it means that you could configure URL using https and scheme using http and then internally both values might be used independently.
> The ideal scenario would be that URL protocol takes precedence over scheme



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

From issues at jboss.org  Thu Mar  9 14:56:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 14:56:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-495) Scheme and URL
 properties might be used in incompatible ways
In-Reply-To: <JIRA.12671802.1484744398000@Atlassian.JIRA>
References: <JIRA.12671802.1484744398000@Atlassian.JIRA>
	<JIRA.12671802.1484744398000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12671802.1484744398000.46794.1489089360371@Atlassian.JIRA>


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

Matous Jobanek updated ARQGRA-495:
----------------------------------
    Fix Version/s: 2.2.0


> Scheme and URL properties might be used in incompatible ways
> ------------------------------------------------------------
>
>                 Key: ARQGRA-495
>                 URL: https://issues.jboss.org/browse/ARQGRA-495
>             Project: Arquillian Graphene
>          Issue Type: Bug
>            Reporter: Alex Soto
>            Assignee: Alex Soto
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> Graphene allows you to configure two properties, scheme and url. The problem is that Scheme might be http, https, ... and the URL instead of being the host + port + context definition, it is a full URL. SO it means that you could configure URL using https and scheme using http and then internally both values might be used independently.
> The ideal scenario would be that URL protocol takes precedence over scheme



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

From issues at jboss.org  Thu Mar  9 14:56:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 14:56:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-495) Scheme and URL
 properties might be used in incompatible ways
In-Reply-To: <JIRA.12671802.1484744398000@Atlassian.JIRA>
References: <JIRA.12671802.1484744398000@Atlassian.JIRA>
	<JIRA.12671802.1484744398000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12671802.1484744398000.46801.1489089360519@Atlassian.JIRA>


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

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


pushed upstream in: https://github.com/arquillian/arquillian-graphene/commit/f702ea10a9bf309a011f5acc64021781c881919e

> Scheme and URL properties might be used in incompatible ways
> ------------------------------------------------------------
>
>                 Key: ARQGRA-495
>                 URL: https://issues.jboss.org/browse/ARQGRA-495
>             Project: Arquillian Graphene
>          Issue Type: Bug
>            Reporter: Alex Soto
>            Assignee: Alex Soto
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> Graphene allows you to configure two properties, scheme and url. The problem is that Scheme might be http, https, ... and the URL instead of being the host + port + context definition, it is a full URL. SO it means that you could configure URL using https and scheme using http and then internally both values might be used independently.
> The ideal scenario would be that URL protocol takes precedence over scheme



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

From issues at jboss.org  Thu Mar  9 15:00:01 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:00:01 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2083) Upgrade to
 arquillian-phantom-driver 1.2.1.1
In-Reply-To: <JIRA.12680884.1489057960000@Atlassian.JIRA>
References: <JIRA.12680884.1489057960000@Atlassian.JIRA>
	<JIRA.12680884.1489057960000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680884.1489057960000.46826.1489089601023@Atlassian.JIRA>


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

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


pushed upstream in: https://github.com/arquillian/arquillian-extension-drone/commit/2fcb507cb541a368e302106675ba6bf7852510f7

> Upgrade to arquillian-phantom-driver 1.2.1.1
> --------------------------------------------
>
>                 Key: ARQ-2083
>                 URL: https://issues.jboss.org/browse/ARQ-2083
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Alpha2
>
>




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

From issues at jboss.org  Thu Mar  9 15:01:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:01:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2081) Upgrade to Selenium
	3.3.0
In-Reply-To: <JIRA.12680297.1488810305000@Atlassian.JIRA>
References: <JIRA.12680297.1488810305000@Atlassian.JIRA>
	<JIRA.12680297.1488810305000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680297.1488810305000.46832.1489089660795@Atlassian.JIRA>


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

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


pushed upstream in: https://github.com/arquillian/arquillian-extension-drone/commit/18ce9edfc4f85bb730d160c57628c252de680345

> Upgrade to Selenium 3.3.0
> -------------------------
>
>                 Key: ARQ-2081
>                 URL: https://issues.jboss.org/browse/ARQ-2081
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Alpha2
>
>




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

From issues at jboss.org  Thu Mar  9 15:02:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:02:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2080) Improper closing of
 browsers configured via remote webdrivers
In-Reply-To: <JIRA.12677509.1487332207000@Atlassian.JIRA>
References: <JIRA.12677509.1487332207000@Atlassian.JIRA>
	<JIRA.12677509.1487332207000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12677509.1487332207000.46834.1489089720113@Atlassian.JIRA>


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

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


pushed upstream in: https://github.com/arquillian/arquillian-extension-drone/commit/2a0b9f8c2409a78f0dcbf43a33b4a75eef335488

> Improper closing of browsers configured via remote webdrivers
> -------------------------------------------------------------
>
>                 Key: ARQ-2080
>                 URL: https://issues.jboss.org/browse/ARQ-2080
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Alpha2
>
>
> When remote WebDriver is being destroyed and the reusable session should be stored, then the browser is not closed.
> https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/factory/RemoteWebDriverFactory.java#L183-L187
> Steps to reproduce: run ReusableRemoteWebDriverTestCase with visible browser (eg. firefox)



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

From issues at jboss.org  Thu Mar  9 15:04:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:04:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2074) Check if binary is
 already executable before trying to chmod it regardless
In-Reply-To: <JIRA.12676868.1487143973000@Atlassian.JIRA>
References: <JIRA.12676868.1487143973000@Atlassian.JIRA>
	<JIRA.12676868.1487143973000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12676868.1487143973000.46842.1489089840146@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-2074.
-------------------------------
    Fix Version/s: drone_2.1.0.Alpha2
       Resolution: Done


pushed upstream in 
arquillian-phantom-driver: https://github.com/qa/arquillian-phantom-driver/commit/193e4ae8a3ad3f310c777439b6f74147cf24fd07
Drone: https://github.com/arquillian/arquillian-extension-drone/commit/7c0e617a059ac03655eb824a43e6b57c850450b8

> Check if binary is already executable before trying to chmod it regardless
> --------------------------------------------------------------------------
>
>                 Key: ARQ-2074
>                 URL: https://issues.jboss.org/browse/ARQ-2074
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Alpha2
>
>
> https://github.com/arquillian/arquillian-extension-drone/blob/master/drone-webdriver/src/main/java/org/jboss/arquillian/drone/webdriver/binary/handler/AbstractBinaryHandler.java#L201-L210
> Add check if the binary is already executable



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

From issues at jboss.org  Thu Mar  9 15:06:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:06:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2061) Upgrade to Selenium 3
In-Reply-To: <JIRA.12665900.1481112679000@Atlassian.JIRA>
References: <JIRA.12665900.1481112679000@Atlassian.JIRA>
	<JIRA.12665900.1481112679000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12665900.1481112679000.46852.1489089960140@Atlassian.JIRA>


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

Matous Jobanek updated ARQ-2061:
--------------------------------
    Fix Version/s: drone_2.1.0.Alpha1
                       (was: drone_3.0.0.Alpha1)


> Upgrade to Selenium 3
> ---------------------
>
>                 Key: ARQ-2061
>                 URL: https://issues.jboss.org/browse/ARQ-2061
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.0.1.Final
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Alpha1
>
>




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

From issues at jboss.org  Thu Mar  9 15:06:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:06:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2061) Upgrade to Selenium 3
In-Reply-To: <JIRA.12665900.1481112679000@Atlassian.JIRA>
References: <JIRA.12665900.1481112679000@Atlassian.JIRA>
	<JIRA.12665900.1481112679000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12665900.1481112679000.46854.1489089960194@Atlassian.JIRA>


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

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


pushed upstream in: https://github.com/arquillian/arquillian-extension-drone/commit/a746764a88301f05a4dbe292affd6d94745f738d

> Upgrade to Selenium 3
> ---------------------
>
>                 Key: ARQ-2061
>                 URL: https://issues.jboss.org/browse/ARQ-2061
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.0.1.Final
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Alpha1
>
>




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

From issues at jboss.org  Thu Mar  9 15:08:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:08:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1890) Support implementation
 of Microsoft WebDriver
In-Reply-To: <JIRA.12558474.1417443521000@Atlassian.JIRA>
References: <JIRA.12558474.1417443521000@Atlassian.JIRA>
	<JIRA.12558474.1417443521000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558474.1417443521000.46860.1489090080147@Atlassian.JIRA>


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

Matous Jobanek reassigned ARQ-1890:
-----------------------------------

    Assignee: Tomas David


> Support implementation of Microsoft WebDriver
> ---------------------------------------------
>
>                 Key: ARQ-1890
>                 URL: https://issues.jboss.org/browse/ARQ-1890
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>    Affects Versions: drone_1.3.1.Final
>            Reporter: Sona Jamborova
>            Assignee: Tomas David
>             Fix For: drone_2.1.0.Final
>
>
> Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium.
> My Idea is:
>   1) An user is responsible to install MS WebDriver
>   2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT.
> Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments).
> Solution for branch drone 1.3.x:
>  * for enabling property in arquillian.xml:
>  ** add new field (attribute) in class WebDriverConfiguration
>  ** add setter and getter for this field
>  ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class
>  * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine"
>  ** in class InternetExplorerDriverFactory



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

From issues at jboss.org  Thu Mar  9 15:11:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 9 Mar 2017 15:11:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1890) Support implementation
 of Microsoft WebDriver
In-Reply-To: <JIRA.12558474.1417443521000@Atlassian.JIRA>
References: <JIRA.12558474.1417443521000@Atlassian.JIRA>
	<JIRA.12558474.1417443521000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558474.1417443521000.46866.1489090260539@Atlassian.JIRA>


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

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


solved by https://github.com/arquillian/arquillian-extension-drone/commit/3914bc009e143a2fb964af228766d45b28f02879

> Support implementation of Microsoft WebDriver
> ---------------------------------------------
>
>                 Key: ARQ-1890
>                 URL: https://issues.jboss.org/browse/ARQ-1890
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>    Affects Versions: drone_1.3.1.Final
>            Reporter: Sona Jamborova
>            Assignee: Tomas David
>             Fix For: drone_2.1.0.Final
>
>
> Selenium team adds support of Microsoft WebDriver in 2.43.0. Drone should use this vendor as well as selenium.
> My Idea is:
>   1) An user is responsible to install MS WebDriver
>   2) Arquillian.xml presents new property (for example: IEDriverEngine). The values are LEGACY, VENDOR, AUTODETECT. The default value is LEGACY or AUTODETECT. I prefer AUTODETECT.
> Unfortunately, this feature is not fully supported by Selenium for Java platforms (see comments).
> Solution for branch drone 1.3.x:
>  * for enabling property in arquillian.xml:
>  ** add new field (attribute) in class WebDriverConfiguration
>  ** add setter and getter for this field
>  ** Note: properties in arquillian.xml are automaticaly mapped to fields in this class
>  * map a value of ieDriverEngine property to system property "webdriver.ie.driver.engine"
>  ** in class InternetExplorerDriverFactory



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

From issues at jboss.org  Fri Mar 10 01:39:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 10 Mar 2017 01:39:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.48000.1489127940274@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-497:
---------------------------------------

Hi, 
as I said, I released it yesterday and luckily everything is synced correctly with Maven central. 
So you can try Graphene 2.2.0 (Drone 2.1.0.Alpha2) with the fixes

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>             Fix For: 2.2.0
>
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Fri Mar 10 03:02:00 2017
From: issues at jboss.org (Emond Papegaaij (JIRA))
Date: Fri, 10 Mar 2017 03:02:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-497) Unable to start
 browser because FluentWait#until(Predicate) has been removed in selenium
 3.2.0
In-Reply-To: <JIRA.12680197.1488790300000@Atlassian.JIRA>
References: <JIRA.12680197.1488790300000@Atlassian.JIRA>
	<JIRA.12680197.1488790300000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12680197.1488790300000.48359.1489132920396@Atlassian.JIRA>


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

Emond Papegaaij commented on ARQGRA-497:
----------------------------------------

Thanks. We'll pick those up on our next upgrade round in a week.

> Unable to start browser because FluentWait#until(Predicate) has been removed in selenium 3.2.0
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-497
>                 URL: https://issues.jboss.org/browse/ARQGRA-497
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.1.0.Final
>            Reporter: Jan Hrcek
>            Assignee: Matous Jobanek
>            Priority: Blocker
>             Fix For: 2.2.0
>
>         Attachments: drone.diff, graphene.diff
>
>
> I'm unable to start Firefox/Chrome driver using Graphene 2.1.0.Final & selenium-bom 3.2.0.
> When instantiating browser I see the following exception:
> {code:java}
> Caused by: java.lang.NoSuchMethodError: org.openqa.selenium.support.ui.WebDriverWait.until(Lcom/google/common/base/Predicate;)V
> 	at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87)
> 	at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44)
> 	at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87)
> 	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 org.openqa.selenium.chrome.ChromeDriver$$EnhancerByGraphene$$1cfa9aea.manage(<generated>)
> {code}
> This seems to be caused by recent removal of FluentWait#until(Predicate) method in selenium (see [recent commit|https://github.com/SeleniumHQ/selenium/commit/bee4115079b7fa678e14eed82e432ddc575621e6]). Could you please update / remove this method from org.jboss.arquillian.graphene.wait.WebDriverWaitImpl so that the browsers can be instantiated again?



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

From issues at jboss.org  Wed Mar 15 13:00:01 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Wed, 15 Mar 2017 13:00:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2070) Add possibility to
 strip statement delimiter from parsed statements
In-Reply-To: <JIRA.12672132.1484856627000@Atlassian.JIRA>
References: <JIRA.12672132.1484856627000@Atlassian.JIRA>
	<JIRA.12672132.1484856627000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12672132.1484856627000.84831.1489597201851@Atlassian.JIRA>


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

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


Pushed upstream. Thanks!

> Add possibility to strip statement delimiter from parsed statements
> -------------------------------------------------------------------
>
>                 Key: ARQ-2070
>                 URL: https://issues.jboss.org/browse/ARQ-2070
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Persistence
>            Reporter: Tobias Stadler
>            Assignee: Bartosz Majsak
>            Priority: Minor
>
> I would be nice to have the possibility to strip the statement delimiter from the parsed statements. E.g. IBM DB2 (Express-c 11.1) does not accept the delimiter in the executed statement.



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

From issues at jboss.org  Sat Mar 18 13:35:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Sat, 18 Mar 2017 13:35:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2084) Update Selenium to 3.3.0
In-Reply-To: <JIRA.12683247.1489858485000@Atlassian.JIRA>
References: <JIRA.12683247.1489858485000@Atlassian.JIRA>
	<JIRA.12683247.1489858485887@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683247.1489858485000.103061.1489858500106@Atlassian.JIRA>

Matous Jobanek created ARQ-2084:
-----------------------------------

             Summary: Update Selenium to 3.3.0
                 Key: ARQ-2084
                 URL: https://issues.jboss.org/browse/ARQ-2084
             Project: Arquillian
          Issue Type: Component Upgrade
          Components: Extension - Drone
    Affects Versions: drone_2.1.0.Alpha2
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: Drone_2.1.0.Alpha3






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

From issues at jboss.org  Mon Mar 20 03:16:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 20 Mar 2017 03:16:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2085) Create GitHub release
	caching functionality
In-Reply-To: <JIRA.12683280.1489994147000@Atlassian.JIRA>
References: <JIRA.12683280.1489994147000@Atlassian.JIRA>
	<JIRA.12683280.1489994147752@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683280.1489994147000.103590.1489994160473@Atlassian.JIRA>

Matous Jobanek created ARQ-2085:
-----------------------------------

             Summary: Create GitHub release caching functionality
                 Key: ARQ-2085
                 URL: https://issues.jboss.org/browse/ARQ-2085
             Project: Arquillian
          Issue Type: Enhancement
          Components: Extension - Drone
    Affects Versions: drone_2.1.0.Alpha2
            Reporter: Matous Jobanek
            Assignee: Hemani Katyal
             Fix For: Drone_2.1.0.Alpha3


Implement GitHub release caching functionality that would cache GH responses based on last modification date from the returned header.
The reason is downloading geckodriver from GH - currently, it is easy to hit the GH rate limit of unauthorized requests



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

From issues at jboss.org  Mon Mar 20 03:17:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 20 Mar 2017 03:17:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2085) Create GitHub release
	caching functionality
In-Reply-To: <JIRA.12683280.1489994148000@Atlassian.JIRA>
References: <JIRA.12683280.1489994148000@Atlassian.JIRA>
	<JIRA.12683280.1489994148000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683280.1489994148000.103602.1489994220225@Atlassian.JIRA>


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

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


> Create GitHub release caching functionality
> -------------------------------------------
>
>                 Key: ARQ-2085
>                 URL: https://issues.jboss.org/browse/ARQ-2085
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha2
>            Reporter: Matous Jobanek
>            Assignee: Hemani Katyal
>             Fix For: Drone_2.1.0.Alpha3
>
>
> Implement GitHub release caching functionality that would cache GH responses based on last modification date from the returned header.
> The reason is downloading geckodriver from GH - currently, it is easy to hit the GH rate limit of unauthorized requests



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

From issues at jboss.org  Mon Mar 20 03:18:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 20 Mar 2017 03:18:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2084) Update Selenium to 3.3.0
In-Reply-To: <JIRA.12683247.1489858486000@Atlassian.JIRA>
References: <JIRA.12683247.1489858486000@Atlassian.JIRA>
	<JIRA.12683247.1489858486000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683247.1489858486000.103607.1489994280305@Atlassian.JIRA>


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

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


Updated in commit: https://github.com/arquillian/arquillian-extension-drone/commit/af7dce13134cd63b8a4c363a6049b90d18ac2768

> Update Selenium to 3.3.0
> ------------------------
>
>                 Key: ARQ-2084
>                 URL: https://issues.jboss.org/browse/ARQ-2084
>             Project: Arquillian
>          Issue Type: Component Upgrade
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha2
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: Drone_2.1.0.Alpha3
>
>




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

From issues at jboss.org  Mon Mar 20 03:18:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 20 Mar 2017 03:18:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2085) Create GitHub release
	caching functionality
In-Reply-To: <JIRA.12683280.1489994148000@Atlassian.JIRA>
References: <JIRA.12683280.1489994148000@Atlassian.JIRA>
	<JIRA.12683280.1489994148000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683280.1489994148000.103605.1489994280227@Atlassian.JIRA>


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

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


Pushed upstream in: https://github.com/arquillian/arquillian-extension-drone/commit/b0cb9ce0f371a64cfa79c2b70735ea4bccd3bb2e

> Create GitHub release caching functionality
> -------------------------------------------
>
>                 Key: ARQ-2085
>                 URL: https://issues.jboss.org/browse/ARQ-2085
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: Extension - Drone
>    Affects Versions: drone_2.1.0.Alpha2
>            Reporter: Matous Jobanek
>            Assignee: Hemani Katyal
>             Fix For: Drone_2.1.0.Alpha3
>
>
> Implement GitHub release caching functionality that would cache GH responses based on last modification date from the returned header.
> The reason is downloading geckodriver from GH - currently, it is easy to hit the GH rate limit of unauthorized requests



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

From issues at jboss.org  Mon Mar 20 12:37:00 2017
From: issues at jboss.org (Gunnar Morling (JIRA))
Date: Mon, 20 Mar 2017 12:37: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.1490027817342@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12683471.1490027817000.110098.1490027820818@Atlassian.JIRA>

Gunnar Morling created ARQ-2086:
-----------------------------------

             Summary: 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
            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  Thu Mar 23 05:50:00 2017
From: issues at jboss.org (Rostislav Svoboda (JIRA))
Date: Thu, 23 Mar 2017 05:50:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-579) We need to be able to
 override default protocol on a container level
In-Reply-To: <JIRA.12446051.1314887896000@Atlassian.JIRA>
References: <JIRA.12446051.1314887896000@Atlassian.JIRA>
	<JIRA.12446051.1314887896000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12446051.1314887896000.130883.1490262600777@Atlassian.JIRA>


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

Rostislav Svoboda commented on ARQ-579:
---------------------------------------

Mentioned also as known deficiency in http://wildfly-swarm.io/posts/running-java-ee-7-samples-with-wildfly-swarm/


> We need to be able to override default protocol on a container level
> --------------------------------------------------------------------
>
>                 Key: ARQ-579
>                 URL: https://issues.jboss.org/browse/ARQ-579
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Base Implementation, Configuration
>    Affects Versions: 1.0.0.Final
>            Reporter: Jos? Freitas
>              Labels: starter
>             Fix For: 2.0.0.Beta1
>
>
> Using <defaultProtocol type="Servlet 3.0" /> makes it impossible to run tests on tomcat-embedded-6.
> We need to be able to override default protocol on a container level, so we can use defaultProtocol property and still share an arquillian.xml between older servers.
> This is just a matter of honoring the protocol element child of the container element, which is already in the schema:
> {code:xml}
> <container qualifier="jbossas-managed-7" default="true">
>     <protocol type="Servlet 3.0"/>
> </container>
> {code}



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


From issues at jboss.org  Mon Mar 27 15:01:01 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:01:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2087) Skip empty elements
	when collecting errors
In-Reply-To: <JIRA.12684657.1490641232000@Atlassian.JIRA>
References: <JIRA.12684657.1490641232000@Atlassian.JIRA>
	<JIRA.12684657.1490641232426@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12684657.1490641232000.2109.1490641261919@Atlassian.JIRA>

Bartosz Majsak created ARQ-2087:
-----------------------------------

             Summary: Skip empty elements when collecting errors
                 Key: ARQ-2087
                 URL: https://issues.jboss.org/browse/ARQ-2087
             Project: Arquillian
          Issue Type: Enhancement
          Components: core
    Affects Versions: 1.1.12.Final
            Reporter: Bartosz Majsak


Under certain circumstances (e.g. daemon module from showcase repo) flattening collected errors results in NPE as there are elements on the list which are `null`. Ignore those when collecting test results.



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

From issues at jboss.org  Mon Mar 27 15:01:02 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:01:02 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2087) Skip empty elements
	when collecting errors
In-Reply-To: <JIRA.12684657.1490641232000@Atlassian.JIRA>
References: <JIRA.12684657.1490641232000@Atlassian.JIRA>
	<JIRA.12684657.1490641232000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12684657.1490641232000.2127.1490641262615@Atlassian.JIRA>


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

Bartosz Majsak updated ARQ-2087:
--------------------------------
    Fix Version/s: 1.1.13.Final


> Skip empty elements when collecting errors
> ------------------------------------------
>
>                 Key: ARQ-2087
>                 URL: https://issues.jboss.org/browse/ARQ-2087
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 1.1.12.Final
>            Reporter: Bartosz Majsak
>             Fix For: 1.1.13.Final
>
>
> Under certain circumstances (e.g. daemon module from showcase repo) flattening collected errors results in NPE as there are elements on the list which are `null`. Ignore those when collecting test results.



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

From issues at jboss.org  Mon Mar 27 15:01:03 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:01:03 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2087) Skip empty elements
	when collecting errors
In-Reply-To: <JIRA.12684657.1490641232000@Atlassian.JIRA>
References: <JIRA.12684657.1490641232000@Atlassian.JIRA>
	<JIRA.12684657.1490641232000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12684657.1490641232000.2134.1490641263281@Atlassian.JIRA>


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

Bartosz Majsak reassigned ARQ-2087:
-----------------------------------

    Assignee: Bartosz Majsak


> Skip empty elements when collecting errors
> ------------------------------------------
>
>                 Key: ARQ-2087
>                 URL: https://issues.jboss.org/browse/ARQ-2087
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 1.1.12.Final
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>             Fix For: 1.1.13.Final
>
>
> Under certain circumstances (e.g. daemon module from showcase repo) flattening collected errors results in NPE as there are elements on the list which are `null`. Ignore those when collecting test results.



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

From issues at jboss.org  Mon Mar 27 15:02:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:02:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2087) Skip empty elements
	when collecting errors
In-Reply-To: <JIRA.12684657.1490641232000@Atlassian.JIRA>
References: <JIRA.12684657.1490641232000@Atlassian.JIRA>
	<JIRA.12684657.1490641232000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12684657.1490641232000.2137.1490641320150@Atlassian.JIRA>


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

Bartosz Majsak commented on ARQ-2087:
-------------------------------------

Upstream https://github.com/arquillian/arquillian-core/commit/ce5b6a8f13998ca58e7fd3b8a0e78e2cae40a50e

> Skip empty elements when collecting errors
> ------------------------------------------
>
>                 Key: ARQ-2087
>                 URL: https://issues.jboss.org/browse/ARQ-2087
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 1.1.12.Final
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>             Fix For: 1.1.13.Final
>
>
> Under certain circumstances (e.g. daemon module from showcase repo) flattening collected errors results in NPE as there are elements on the list which are `null`. Ignore those when collecting test results.



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

From issues at jboss.org  Mon Mar 27 15:02:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:02:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2087) Skip empty elements
	when collecting errors
In-Reply-To: <JIRA.12684657.1490641232000@Atlassian.JIRA>
References: <JIRA.12684657.1490641232000@Atlassian.JIRA>
	<JIRA.12684657.1490641232000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12684657.1490641232000.2140.1490641320207@Atlassian.JIRA>


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

Bartosz Majsak resolved ARQ-2087.
---------------------------------
    Resolution: Done


> Skip empty elements when collecting errors
> ------------------------------------------
>
>                 Key: ARQ-2087
>                 URL: https://issues.jboss.org/browse/ARQ-2087
>             Project: Arquillian
>          Issue Type: Enhancement
>          Components: core
>    Affects Versions: 1.1.12.Final
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>             Fix For: 1.1.13.Final
>
>
> Under certain circumstances (e.g. daemon module from showcase repo) flattening collected errors results in NPE as there are elements on the list which are `null`. Ignore those when collecting test results.



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

From issues at jboss.org  Mon Mar 27 15:03:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:03: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.2143.1490641380125@Atlassian.JIRA>


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

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

Thanks for reporting.

> 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
>            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  Mon Mar 27 15:03:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:03:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1987) Arquillian doesn't work
 with latest Tomcat 7.0.64 and 8.0.27 due to class loader issues
In-Reply-To: <JIRA.12587190.1443973221000@Atlassian.JIRA>
References: <JIRA.12587190.1443973221000@Atlassian.JIRA>
	<JIRA.12587190.1443973221000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12587190.1443973221000.2146.1490641380196@Atlassian.JIRA>


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

Bartosz Majsak commented on ARQ-1987:
-------------------------------------

Did you try latest core and tomcat container adapter?

> Arquillian doesn't work with latest Tomcat 7.0.64 and 8.0.27 due to class loader issues
> ---------------------------------------------------------------------------------------
>
>                 Key: ARQ-1987
>                 URL: https://issues.jboss.org/browse/ARQ-1987
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Tomcat Containers
>    Affects Versions: 1.1.9.Final
>         Environment: {code}
> $ JAVA_HOME=`/usr/libexec/java_home -v 1.7` mvn --version
> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T13:57:37+02:00)
> Maven home: /usr/local/Cellar/maven/3.3.3/libexec
> Java version: 1.7.0_80, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11", arch: "x86_64", family: "mac"
> {code}
>            Reporter: Christian Schlichtherle
>            Priority: Blocker
>
> I am following the reference documentation for testing with an embedded Tomcat 7 container at https://docs.jboss.org/author/display/ARQ/Tomcat+7.0+-+Embedded . This works fine with Tomcat 7.0.50. However, when updating to Tomcat 7.0.64 and leaving all else unchanged, I get this when running my integration test:
> {code}
> /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/bin/java -ea -Djava.awt.headless=true -Didea.launcher.port=7540 "-Didea.launcher.bin.path=/Applications/IntelliJ IDEA 14.app/Contents/bin" -Dfile.encoding=UTF-8 -classpath "/Applications/IntelliJ IDEA 14.app/Contents/lib/idea_rt.jar:/Applications/IntelliJ IDEA 14.app/Contents/plugins/junit/lib/junit-rt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/ant-javafx.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/dt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/javafx-doclet.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/javafx-mx.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/jconsole.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/sa-jdi.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/lib/tools.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/deploy.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/htmlconverter.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/javaws.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/jce.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/jfxrt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/management-agent.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/plugin.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/resources.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/rt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/Users/christian/projects/trueupdate/trueupdate-installer/trueupdate-installer-tomcat/target/test-classes:/Users/christian/projects/trueupdate/trueupdate-installer/trueupdate-installer-tomcat/target/classes:/Users/christian/projects/trueupdate/trueupdate-installer/trueupdate-installer-core/target/classes:/Users/christian/projects/trueupdate/trueupdate-core/target/classes:/Users/christian/projects/trueupdate/trueupdate-util/target/classes:/Users/christian/projects/trueupdate/trueupdate-manager/trueupdate-manager-spec/target/classes:/Users/christian/projects/trueupdate/trueupdate-message/target/classes:/Users/christian/projects/trueupdate/trueupdate-artifact/trueupdate-artifact-spec/target/classes:/Users/christian/.m2/repository/org/jboss/arquillian/junit/arquillian-junit-container/1.1.5.Final/arquillian-junit-container-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/junit/arquillian-junit-core/1.1.5.Final/arquillian-junit-core-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/test/arquillian-test-api/1.1.5.Final/arquillian-test-api-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/core/arquillian-core-api/1.1.5.Final/arquillian-core-api-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/test/arquillian-test-spi/1.1.5.Final/arquillian-test-spi-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/core/arquillian-core-spi/1.1.5.Final/arquillian-core-spi-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/container/arquillian-container-test-api/1.1.5.Final/arquillian-container-test-api-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/shrinkwrap/shrinkwrap-api/1.2.2/shrinkwrap-api-1.2.2.jar:/Users/christian/.m2/repository/org/jboss/arquillian/container/arquillian-container-test-spi/1.1.5.Final/arquillian-container-test-spi-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/core/arquillian-core-impl-base/1.1.5.Final/arquillian-core-impl-base-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/test/arquillian-test-impl-base/1.1.5.Final/arquillian-test-impl-base-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/container/arquillian-container-impl-base/1.1.5.Final/arquillian-container-impl-base-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/config/arquillian-config-api/1.1.5.Final/arquillian-config-api-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/config/arquillian-config-impl-base/1.1.5.Final/arquillian-config-impl-base-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/shrinkwrap/descriptors/shrinkwrap-descriptors-spi/2.0.0-alpha-5/shrinkwrap-descriptors-spi-2.0.0-alpha-5.jar:/Users/christian/.m2/repository/org/easytesting/fest-assert/1.4/fest-assert-1.4.jar:/Users/christian/.m2/repository/org/easytesting/fest-util/1.1.6/fest-util-1.1.6.jar:/Users/christian/.m2/repository/org/jboss/arquillian/container/arquillian-container-test-impl-base/1.1.5.Final/arquillian-container-test-impl-base-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/shrinkwrap/shrinkwrap-impl-base/1.2.2/shrinkwrap-impl-base-1.2.2.jar:/Users/christian/.m2/repository/org/jboss/shrinkwrap/shrinkwrap-spi/1.2.2/shrinkwrap-spi-1.2.2.jar:/Users/christian/.m2/repository/org/jboss/arquillian/container/arquillian-tomcat-embedded-7/1.0.0.CR6/arquillian-tomcat-embedded-7-1.0.0.CR6.jar:/Users/christian/.m2/repository/org/jboss/arquillian/container/arquillian-container-spi/1.1.5.Final/arquillian-container-spi-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/shrinkwrap/descriptors/shrinkwrap-descriptors-api-base/2.0.0-alpha-5/shrinkwrap-descriptors-api-base-2.0.0-alpha-5.jar:/Users/christian/.m2/repository/org/jboss/arquillian/protocol/arquillian-protocol-servlet/1.1.5.Final/arquillian-protocol-servlet-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/testenricher/arquillian-testenricher-cdi/1.1.5.Final/arquillian-testenricher-cdi-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/testenricher/arquillian-testenricher-resource/1.1.5.Final/arquillian-testenricher-resource-1.1.5.Final.jar:/Users/christian/.m2/repository/org/jboss/arquillian/testenricher/arquillian-testenricher-initialcontext/1.1.5.Final/arquillian-testenricher-initialcontext-1.1.5.Final.jar:/Users/christian/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/7.0.64/tomcat-embed-core-7.0.64.jar:/Users/christian/.m2/repository/org/apache/tomcat/embed/tomcat-embed-jasper/7.0.64/tomcat-embed-jasper-7.0.64.jar:/Users/christian/.m2/repository/org/apache/tomcat/embed/tomcat-embed-el/7.0.64/tomcat-embed-el-7.0.64.jar:/Users/christian/.m2/repository/org/eclipse/jdt/core/compiler/ecj/4.4.2/ecj-4.4.2.jar:/Users/christian/.m2/repository/org/apache/tomcat/embed/tomcat-embed-logging-juli/7.0.64/tomcat-embed-logging-juli-7.0.64.jar:/Users/christian/.m2/repository/com/google/code/findbugs/annotations/3.0.0/annotations-3.0.0.jar:/Users/christian/.m2/repository/junit/junit/4.12/junit-4.12.jar:/Users/christian/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar:/Users/christian/.m2/repository/org/mockito/mockito-core/1.10.17/mockito-core-1.10.17.jar:/Users/christian/.m2/repository/org/objenesis/objenesis/2.1/objenesis-2.1.jar:/Users/christian/.m2/repository/org/scalatest/scalatest_2.11/2.2.3/scalatest_2.11-2.2.3.jar:/Users/christian/.m2/repository/org/scala-lang/scala-library/2.11.4/scala-library-2.11.4.jar:/Users/christian/.m2/repository/org/scala-lang/scala-reflect/2.11.2/scala-reflect-2.11.2.jar:/Users/christian/.m2/repository/org/scala-lang/modules/scala-xml_2.11/1.0.2/scala-xml_2.11-1.0.2.jar:/Users/christian/.m2/repository/org/scalacheck/scalacheck_2.11/1.12.1/scalacheck_2.11-1.12.1.jar:/Users/christian/.m2/repository/org/scala-lang/modules/scala-parser-combinators_2.11/1.0.2/scala-parser-combinators_2.11-1.0.2.jar:/Users/christian/.m2/repository/org/scala-sbt/test-interface/1.0/test-interface-1.0.jar" com.intellij.rt.execution.application.AppMain com.intellij.rt.execution.junit.JUnitStarter -ideVersion5 net.java.trueupdate.installer.tomcat.TomcatUpdateInstallerIT
> Okt 04, 2015 5:18:31 PM org.apache.coyote.AbstractProtocol init
> INFORMATION: Initializing ProtocolHandler ["http-bio-1971"]
> Okt 04, 2015 5:18:31 PM org.apache.catalina.core.StandardService startInternal
> INFORMATION: Starting service arquillian-tomcat-embedded-7
> Okt 04, 2015 5:18:31 PM org.apache.catalina.core.StandardEngine startInternal
> INFORMATION: Starting Servlet Engine: Apache Tomcat/7.0.64
> Okt 04, 2015 5:18:31 PM org.apache.coyote.AbstractProtocol start
> INFORMATION: Starting ProtocolHandler ["http-bio-1971"]
> Okt 04, 2015 5:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
> INFORMATION: Deploying web application archive /private/var/folders/qb/9yzsm8_13wq7mxsf8k0z98h40000gp/T/tomcat-embedded-73699509114599265821.tmp/webapps/3bc039ea-042f-4668-a75b-5f1424e3fdf4.war
> Okt 04, 2015 5:18:32 PM org.apache.catalina.startup.ContextConfig getDefaultWebXmlFragment
> INFORMATION: No global web.xml found
> Okt 04, 2015 5:18:33 PM org.apache.catalina.startup.TldConfig execute
> INFORMATION: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
> Okt 04, 2015 5:18:33 PM org.apache.catalina.startup.HostConfig deployWAR
> INFORMATION: Deployment of web application archive /private/var/folders/qb/9yzsm8_13wq7mxsf8k0z98h40000gp/T/tomcat-embedded-73699509114599265821.tmp/webapps/3bc039ea-042f-4668-a75b-5f1424e3fdf4.war has finished in 1,811 ms
> java.lang.ExceptionInInitializerError
> 	at org.jboss.shrinkwrap.api.ShrinkWrap.getDefaultDomain(ShrinkWrap.java:108)
> 	at org.jboss.shrinkwrap.api.ShrinkWrap.create(ShrinkWrap.java:136)
> 	at net.java.trueupdate.installer.tomcat.TomcatUpdateInstallerIT$.testArchive(TomcatUpdateInstallerIT.scala:59)
> 	at net.java.trueupdate.installer.tomcat.TomcatUpdateInstallerIT.test(TomcatUpdateInstallerIT.scala:32)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	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$6$1.invoke(Arquillian.java:301)
> 	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:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	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.ContainerTestExecuter.execute(ContainerTestExecuter.java:38)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:102)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	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:84)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	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:65)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	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:111)
> 	at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:294)
> 	at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267)
> 	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:193)
> 	at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345)
> 	at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49)
> 	at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> 	at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155)
> 	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> 	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> 	at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66)
> 	at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:159)
> 	at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:125)
> 	at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:89)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
> 	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
> 	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
> 	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassCastException: Incorrect expected type, org.jboss.shrinkwrap.api.ExtensionLoader, defined for org.jboss.shrinkwrap.impl.base.ServiceExtensionLoader
> 	at org.jboss.shrinkwrap.api.SecurityActions.newInstance(SecurityActions.java:143)
> 	at org.jboss.shrinkwrap.api.ConfigurationBuilder.createDefaultExtensionLoader(ConfigurationBuilder.java:230)
> 	at org.jboss.shrinkwrap.api.ConfigurationBuilder.setDefaults(ConfigurationBuilder.java:204)
> 	at org.jboss.shrinkwrap.api.Configuration.<init>(Configuration.java:81)
> 	at org.jboss.shrinkwrap.api.ConfigurationBuilder.build(ConfigurationBuilder.java:156)
> 	at org.jboss.shrinkwrap.api.ShrinkWrap.createDomain(ShrinkWrap.java:79)
> 	at org.jboss.shrinkwrap.api.ShrinkWrap.createDomain(ShrinkWrap.java:60)
> 	at org.jboss.shrinkwrap.api.ShrinkWrap$DefaultDomainWrapper.<init>(ShrinkWrap.java:204)
> 	at org.jboss.shrinkwrap.api.ShrinkWrap$DefaultDomainWrapper.<clinit>(ShrinkWrap.java:199)
> 	... 94 more
> Okt 04, 2015 5:18:34 PM org.apache.coyote.AbstractProtocol pause
> INFORMATION: Pausing ProtocolHandler ["http-bio-1971"]
> Okt 04, 2015 5:18:34 PM org.apache.catalina.core.StandardService stopInternal
> INFORMATION: Stopping service arquillian-tomcat-embedded-7
> Okt 04, 2015 5:18:34 PM org.apache.coyote.AbstractProtocol stop
> INFORMATION: Stopping ProtocolHandler ["http-bio-1971"]
> Process finished with exit code 255
> {code}
> The relevant code in {{SecurityActions.newInstance}} is this:
> {code}
>         try {
>             return expectedType.cast(obj);
>         } catch (final ClassCastException cce) {
>             // Reconstruct so we get some useful information
>             throw new ClassCastException("Incorrect expected type, " + expectedType.getName() + ", defined for "
>                 + obj.getClass().getName());
>         }
> {code}
> I've set a break point at line line 143, which is the {{throws}}-statement to verify that {{obj}} is loaded by a different class loader than the class loader of {{expectedType}}, which is why a {{ClassCastException}} is thrown.



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


From issues at jboss.org  Mon Mar 27 15:04:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:04: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.2150.1490641440212@Atlassian.JIRA>


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

Bartosz Majsak reassigned ARQ-2086:
-----------------------------------

    Assignee: Bartosz Majsak


> 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: Bartosz Majsak
>            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  Mon Mar 27 15:06:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:06:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1926) ARQ-1842	Show original
 exception instead of NullPointerExcetpion from TransactionHandler
In-Reply-To: <JIRA.12564059.1424782728000@Atlassian.JIRA>
References: <JIRA.12564059.1424782728000@Atlassian.JIRA>
	<JIRA.12564059.1424782728000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564059.1424782728000.2155.1490641560190@Atlassian.JIRA>


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

Bartosz Majsak closed ARQ-1926.
-------------------------------
    Fix Version/s: transaction_1.0.3.Final
       Resolution: Done
           Labels: duplicate  (was: )


> ARQ-1842	Show original exception instead of NullPointerExcetpion from TransactionHandler
> ----------------------------------------------------------------------------------------
>
>                 Key: ARQ-1926
>                 URL: https://issues.jboss.org/browse/ARQ-1926
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Transaction
>    Affects Versions: 1.1.6.Final, 1.1.7.Final
>            Reporter: Martijn Dashorst
>              Labels: duplicate
>             Fix For: transaction_1.0.3.Final
>
>
> This is a duplicate of ARQ-1842, but assigned to the proper component (1842 is assigned to core, this one to extension-transaction)
> ARQ-1842 has a pull request solving this issue.
> See ARQ-1842 Show original exception instead of NullPointerExcetpion from TransactionHandler



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

From issues at jboss.org  Mon Mar 27 15:07:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:07:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1925) @After no longer runs
 within transaction boundaries since 1.1.7
In-Reply-To: <JIRA.12564054.1424780515000@Atlassian.JIRA>
References: <JIRA.12564054.1424780515000@Atlassian.JIRA>
	<JIRA.12564054.1424780515000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564054.1424780515000.2158.1490641620307@Atlassian.JIRA>


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

Bartosz Majsak updated ARQ-1925:
--------------------------------
    Fix Version/s: transaction_1.0.4


> @After no longer runs within transaction boundaries since 1.1.7
> ---------------------------------------------------------------
>
>                 Key: ARQ-1925
>                 URL: https://issues.jboss.org/browse/ARQ-1925
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Transaction
>    Affects Versions: transaction_1.0.1.Final, 1.1.7.Final
>            Reporter: Emond Papegaaij
>             Fix For: transaction_1.0.4
>
>
> With the changes in TestLifecycleEvents introduced in Arquillian core 1.1.7, the @After junit methods no longer run within the transaction boundaries. In TransactionHandler.endTransactionAfterTest, first the transaction is ended and then the event proceeds, calling @After methods.
> I've created a pull request that switches these call, this fixes our testcases.



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

From issues at jboss.org  Mon Mar 27 15:07:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:07:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1925) @After no longer runs
 within transaction boundaries since 1.1.7
In-Reply-To: <JIRA.12564054.1424780515000@Atlassian.JIRA>
References: <JIRA.12564054.1424780515000@Atlassian.JIRA>
	<JIRA.12564054.1424780515000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564054.1424780515000.2165.1490641620453@Atlassian.JIRA>


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

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


> @After no longer runs within transaction boundaries since 1.1.7
> ---------------------------------------------------------------
>
>                 Key: ARQ-1925
>                 URL: https://issues.jboss.org/browse/ARQ-1925
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Transaction
>    Affects Versions: transaction_1.0.1.Final, 1.1.7.Final
>            Reporter: Emond Papegaaij
>             Fix For: transaction_1.0.4
>
>
> With the changes in TestLifecycleEvents introduced in Arquillian core 1.1.7, the @After junit methods no longer run within the transaction boundaries. In TransactionHandler.endTransactionAfterTest, first the transaction is ended and then the event proceeds, calling @After methods.
> I've created a pull request that switches these call, this fixes our testcases.



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

From issues at jboss.org  Mon Mar 27 15:08:00 2017
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 27 Mar 2017 15:08:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1925) @After no longer runs
 within transaction boundaries since 1.1.7
In-Reply-To: <JIRA.12564054.1424780515000@Atlassian.JIRA>
References: <JIRA.12564054.1424780515000@Atlassian.JIRA>
	<JIRA.12564054.1424780515000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12564054.1424780515000.2171.1490641680251@Atlassian.JIRA>


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

Bartosz Majsak commented on ARQ-1925:
-------------------------------------

Upstream https://github.com/arquillian/arquillian-extension-transaction/commit/92864c82117b9d6e5c70307f81a6ee774bed0c53

> @After no longer runs within transaction boundaries since 1.1.7
> ---------------------------------------------------------------
>
>                 Key: ARQ-1925
>                 URL: https://issues.jboss.org/browse/ARQ-1925
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Transaction
>    Affects Versions: transaction_1.0.1.Final, 1.1.7.Final
>            Reporter: Emond Papegaaij
>             Fix For: transaction_1.0.4
>
>
> With the changes in TestLifecycleEvents introduced in Arquillian core 1.1.7, the @After junit methods no longer run within the transaction boundaries. In TransactionHandler.endTransactionAfterTest, first the transaction is ended and then the event proceeds, calling @After methods.
> I've created a pull request that switches these call, this fixes our testcases.



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

From issues at jboss.org  Tue Mar 28 04:22:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 28 Mar 2017 04:22:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1699) PhantomJS resolution by
	Spacelift
In-Reply-To: <JIRA.12534576.1394464682000@Atlassian.JIRA>
References: <JIRA.12534576.1394464682000@Atlassian.JIRA>
	<JIRA.12534576.1394464682000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534576.1394464682000.4931.1490689320275@Atlassian.JIRA>


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

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


> PhantomJS resolution by Spacelift
> ---------------------------------
>
>                 Key: ARQ-1699
>                 URL: https://issues.jboss.org/browse/ARQ-1699
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>             Fix For: drone_2.1.0.Final
>
>
> PhantomJS resolution should be done via Spacelift.



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

From issues at jboss.org  Tue Mar 28 04:22:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 28 Mar 2017 04:22:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1699) PhantomJS resolution by
	Spacelift
In-Reply-To: <JIRA.12534576.1394464682000@Atlassian.JIRA>
References: <JIRA.12534576.1394464682000@Atlassian.JIRA>
	<JIRA.12534576.1394464682000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534576.1394464682000.4934.1490689320365@Atlassian.JIRA>


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

Matous Jobanek reassigned ARQ-1699:
-----------------------------------

    Assignee: Matous Jobanek


> PhantomJS resolution by Spacelift
> ---------------------------------
>
>                 Key: ARQ-1699
>                 URL: https://issues.jboss.org/browse/ARQ-1699
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Final
>
>
> PhantomJS resolution should be done via Spacelift.



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

From issues at jboss.org  Tue Mar 28 08:48:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 28 Mar 2017 08:48:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2088) When test is skipped
 because of an assumption, Arquillian's test result is passed
In-Reply-To: <JIRA.12684762.1490705236000@Atlassian.JIRA>
References: <JIRA.12684762.1490705236000@Atlassian.JIRA>
	<JIRA.12684762.1490705236288@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12684762.1490705236000.9677.1490705280195@Atlassian.JIRA>

Matous Jobanek created ARQ-2088:
-----------------------------------

             Summary: When test is skipped because of an assumption, Arquillian's test result is passed
                 Key: ARQ-2088
                 URL: https://issues.jboss.org/browse/ARQ-2088
             Project: Arquillian
          Issue Type: Enhancement
          Components: core
    Affects Versions: 1.1.13.Final
            Reporter: Matous Jobanek


When you run Arquillian test with an assumption: {{Assume.assumeFalse(true);}} then the test is skipped. The same also say both IDE and maven surefire, but Arquillian's {{TestResult}} retrieved in {{After}} phase contains status Passed.



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

From issues at jboss.org  Wed Mar 29 04:18:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Wed, 29 Mar 2017 04:18:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is
 not equal to the same element
In-Reply-To: <JIRA.12591592.1446713871000@Atlassian.JIRA>
References: <JIRA.12591592.1446713871000@Atlassian.JIRA>
	<JIRA.12591592.1446713871000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12591592.1446713871000.15246.1490775480586@Atlassian.JIRA>


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

Vsevolod Golovanov commented on ARQGRA-484:
-------------------------------------------

{code:title=PR154}if (obj instanceof GrapheneElementImpl) {
    obj = ((GrapheneElementImpl) obj).element;
}
return element.equals(obj);
{code}
{{obj instanceof GrapheneElementImpl}} would most of the time evaluate to false because obj would be a proxy. So the execution would move on to {{element.equals(obj)}}, where it relies on Selenium's RemoteWebElement#equals to unwrap the obj (via the WrapsElement interface and its getWrappedElement() method). Might as well rely on it in case of {{obj instanceof GrapheneElementImpl}} evaluating to true. In fact, whenever there are proxies involved, code like {{otherObj.privateField}} seems iffy. What if a proxy sometimes extends the Impl class?

> Enriched element is not equal to the same element
> -------------------------------------------------
>
>                 Key: ARQGRA-484
>                 URL: https://issues.jboss.org/browse/ARQGRA-484
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Alpha3
>            Reporter: Ji?? ?tefek
>
> After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass:
> {code}
>   @FindBy(id="id")
>   private WebElement e;
>   @Test 
>   private void test(){
>     e.equals(e) 
>   }
> {code}



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


From issues at jboss.org  Wed Mar 29 04:36:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Wed, 29 Mar 2017 04:36:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is
 not equal to the same element
In-Reply-To: <JIRA.12591592.1446713871000@Atlassian.JIRA>
References: <JIRA.12591592.1446713871000@Atlassian.JIRA>
	<JIRA.12591592.1446713871000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12591592.1446713871000.15430.1490776560441@Atlassian.JIRA>


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

Vsevolod Golovanov commented on ARQGRA-484:
-------------------------------------------

But sometimes a proxy doesn't implement WrapsElement, because it doesn't proxy a GrapheneElement, but a RemoteWebElement directly. E.g. {{driver.switchTo().activeElement()}}. This may be a separate bug...

> Enriched element is not equal to the same element
> -------------------------------------------------
>
>                 Key: ARQGRA-484
>                 URL: https://issues.jboss.org/browse/ARQGRA-484
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Alpha3
>            Reporter: Ji?? ?tefek
>
> After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass:
> {code}
>   @FindBy(id="id")
>   private WebElement e;
>   @Test 
>   private void test(){
>     e.equals(e) 
>   }
> {code}



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


From issues at jboss.org  Wed Mar 29 15:31:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Wed, 29 Mar 2017 15:31:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL
	parameters
In-Reply-To: <JIRA.12685068.1490815854000@Atlassian.JIRA>
References: <JIRA.12685068.1490815854000@Atlassian.JIRA>
	<JIRA.12685068.1490815854526@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685068.1490815854000.23312.1490815860236@Atlassian.JIRA>

Vsevolod Golovanov created ARQGRA-500:
-----------------------------------------

             Summary: Navigation with URL parameters
                 Key: ARQGRA-500
                 URL: https://issues.jboss.org/browse/ARQGRA-500
             Project: Arquillian Graphene
          Issue Type: Feature Request
            Reporter: Vsevolod Golovanov


I need to add a dynamic URL parameter to a location of a page before navigating to it.
I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding.
A special landing page would be a pretty ugly workaround.

I get that it's not possible with annotations. But at least support this with Graphene.goTo methods.
Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}.



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

From issues at jboss.org  Wed Mar 29 15:36:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Wed, 29 Mar 2017 15:36:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL
	parameters
In-Reply-To: <JIRA.12685068.1490815855000@Atlassian.JIRA>
References: <JIRA.12685068.1490815855000@Atlassian.JIRA>
	<JIRA.12685068.1490815855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685068.1490815855000.23324.1490816160058@Atlassian.JIRA>


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

Vsevolod Golovanov commented on ARQGRA-500:
-------------------------------------------

Why won't I go via normal means like a user would, arrive to this parameterized page through other pages? Sometimes this path is too complex, the pages involved are too heavy - they have their own tests, other teams support those pages. Sometimes there may not be such a path at all, because some pages are linked directly with parameters by 3rd party applications.

> Navigation with URL parameters
> ------------------------------
>
>                 Key: ARQGRA-500
>                 URL: https://issues.jboss.org/browse/ARQGRA-500
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Vsevolod Golovanov
>
> I need to add a dynamic URL parameter to a location of a page before navigating to it.
> I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding.
> A special landing page would be a pretty ugly workaround.
> I get that it's not possible with annotations. But at least support this with Graphene.goTo methods.
> Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}.



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

From issues at jboss.org  Thu Mar 30 02:58:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Thu, 30 Mar 2017 02:58:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL
	parameters
In-Reply-To: <JIRA.12685068.1490815855000@Atlassian.JIRA>
References: <JIRA.12685068.1490815855000@Atlassian.JIRA>
	<JIRA.12685068.1490815855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685068.1490815855000.24551.1490857080072@Atlassian.JIRA>


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

Vsevolod Golovanov commented on ARQGRA-500:
-------------------------------------------

Then again, some parameter provider class wouldn't know the context to decide on parameters. Only the test does. Some location decider probably can get the current test instance and call some callback on it. The test just needs to implement the interface ParameterProvider - this would be the trigger. No need to alter the \@Location annotation.

> Navigation with URL parameters
> ------------------------------
>
>                 Key: ARQGRA-500
>                 URL: https://issues.jboss.org/browse/ARQGRA-500
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Vsevolod Golovanov
>
> I need to add a dynamic URL parameter to a location of a page before navigating to it.
> I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding.
> A special landing page would be a pretty ugly workaround.
> I get that it's not possible with annotations. But at least support this with Graphene.goTo methods.
> Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}.



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

From issues at jboss.org  Thu Mar 30 03:37:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Thu, 30 Mar 2017 03:37:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is
 not equal to the same element
In-Reply-To: <JIRA.12591592.1446713871000@Atlassian.JIRA>
References: <JIRA.12591592.1446713871000@Atlassian.JIRA>
	<JIRA.12591592.1446713871000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12591592.1446713871000.24844.1490859420204@Atlassian.JIRA>


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

Vsevolod Golovanov edited comment on ARQGRA-484 at 3/30/17 3:36 AM:
--------------------------------------------------------------------

<Moved to PR154>


was (Author: vsevolodgolovanov):
{code:title=PR154}if (obj instanceof GrapheneElementImpl) {
    obj = ((GrapheneElementImpl) obj).element;
}
return element.equals(obj);
{code}
{{obj instanceof GrapheneElementImpl}} would most of the time evaluate to false because obj would be a proxy. So the execution would move on to {{element.equals(obj)}}, where it relies on Selenium's RemoteWebElement#equals to unwrap the obj (via the WrapsElement interface and its getWrappedElement() method). Might as well rely on it in case of {{obj instanceof GrapheneElementImpl}} evaluating to true. In fact, whenever there are proxies involved, code like {{otherObj.privateField}} seems iffy. What if a proxy sometimes extends the Impl class?

> Enriched element is not equal to the same element
> -------------------------------------------------
>
>                 Key: ARQGRA-484
>                 URL: https://issues.jboss.org/browse/ARQGRA-484
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Alpha3
>            Reporter: Ji?? ?tefek
>
> After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass:
> {code}
>   @FindBy(id="id")
>   private WebElement e;
>   @Test 
>   private void test(){
>     e.equals(e) 
>   }
> {code}



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


From issues at jboss.org  Thu Mar 30 03:37:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Thu, 30 Mar 2017 03:37:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is
 not equal to the same element
In-Reply-To: <JIRA.12591592.1446713871000@Atlassian.JIRA>
References: <JIRA.12591592.1446713871000@Atlassian.JIRA>
	<JIRA.12591592.1446713871000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12591592.1446713871000.24845.1490859420221@Atlassian.JIRA>


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

Vsevolod Golovanov edited comment on ARQGRA-484 at 3/30/17 3:36 AM:
--------------------------------------------------------------------

<Moved to PR154>


was (Author: vsevolodgolovanov):
But sometimes a proxy doesn't implement WrapsElement, because it doesn't proxy a GrapheneElement, but a RemoteWebElement directly. E.g. {{driver.switchTo().activeElement()}}. This may be a separate bug...

> Enriched element is not equal to the same element
> -------------------------------------------------
>
>                 Key: ARQGRA-484
>                 URL: https://issues.jboss.org/browse/ARQGRA-484
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Alpha3
>            Reporter: Ji?? ?tefek
>
> After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass:
> {code}
>   @FindBy(id="id")
>   private WebElement e;
>   @Test 
>   private void test(){
>     e.equals(e) 
>   }
> {code}



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


From issues at jboss.org  Thu Mar 30 04:18:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 30 Mar 2017 04:18:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-484) Enriched element is
 not equal to the same element
In-Reply-To: <JIRA.12591592.1446713871000@Atlassian.JIRA>
References: <JIRA.12591592.1446713871000@Atlassian.JIRA>
	<JIRA.12591592.1446713871000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12591592.1446713871000.25032.1490861880395@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-484:
---------------------------------------

[~vsevolodgolovanov] Thank you for your investigation. Any contribution/help in this issue will be very welcome.

> Enriched element is not equal to the same element
> -------------------------------------------------
>
>                 Key: ARQGRA-484
>                 URL: https://issues.jboss.org/browse/ARQGRA-484
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Alpha3
>            Reporter: Ji?? ?tefek
>
> After upgrading to 2.1.0.Alpha3 from Alpha2, the following (simplified) test won't pass:
> {code}
>   @FindBy(id="id")
>   private WebElement e;
>   @Test 
>   private void test(){
>     e.equals(e) 
>   }
> {code}



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


From issues at jboss.org  Thu Mar 30 05:02:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Thu, 30 Mar 2017 05:02:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL
	parameters
In-Reply-To: <JIRA.12685068.1490815855000@Atlassian.JIRA>
References: <JIRA.12685068.1490815855000@Atlassian.JIRA>
	<JIRA.12685068.1490815855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685068.1490815855000.25563.1490864520176@Atlassian.JIRA>


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

Vsevolod Golovanov edited comment on ARQGRA-500 at 3/30/17 5:01 AM:
--------------------------------------------------------------------

Then again, some parameter provider class wouldn't know the context to decide on parameters. Only the test does. Some location decider probably can get the current test instance and call some callback on it. The test just needs to implement the interface ParameterProvider - this would be the trigger. No need to alter the \@Location annotation.

Upd: it's probably not possible to "get the current test instance" without hardcoding some specific test framework like JUnit.


was (Author: vsevolodgolovanov):
Then again, some parameter provider class wouldn't know the context to decide on parameters. Only the test does. Some location decider probably can get the current test instance and call some callback on it. The test just needs to implement the interface ParameterProvider - this would be the trigger. No need to alter the \@Location annotation.

> Navigation with URL parameters
> ------------------------------
>
>                 Key: ARQGRA-500
>                 URL: https://issues.jboss.org/browse/ARQGRA-500
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Vsevolod Golovanov
>
> I need to add a dynamic URL parameter to a location of a page before navigating to it.
> I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding.
> A special landing page would be a pretty ugly workaround.
> I get that it's not possible with annotations. But at least support this with Graphene.goTo methods.
> Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}.



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

From issues at jboss.org  Thu Mar 30 05:14:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Thu, 30 Mar 2017 05:14:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL
	parameters
In-Reply-To: <JIRA.12685068.1490815855000@Atlassian.JIRA>
References: <JIRA.12685068.1490815855000@Atlassian.JIRA>
	<JIRA.12685068.1490815855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685068.1490815855000.25668.1490865240061@Atlassian.JIRA>


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

Vsevolod Golovanov edited comment on ARQGRA-500 at 3/30/17 5:13 AM:
--------------------------------------------------------------------

Then again, some parameter provider class wouldn't know the context to decide on parameters. Only the test does. Some location decider probably can get the current test instance and call some callback on it. The test just needs to implement the interface ParameterProvider - this would be the trigger. No need to alter the \@Location annotation.

Upd: it's probably not possible to "get the current test instance" without hardcoding some specific test framework like JUnit.

Upd2: it should be possible! Otherwise how would Graphene's annotations work. They know the test object, see org.jboss.arquillian.test.spi.TestEnricher.


was (Author: vsevolodgolovanov):
Then again, some parameter provider class wouldn't know the context to decide on parameters. Only the test does. Some location decider probably can get the current test instance and call some callback on it. The test just needs to implement the interface ParameterProvider - this would be the trigger. No need to alter the \@Location annotation.

Upd: it's probably not possible to "get the current test instance" without hardcoding some specific test framework like JUnit.

> Navigation with URL parameters
> ------------------------------
>
>                 Key: ARQGRA-500
>                 URL: https://issues.jboss.org/browse/ARQGRA-500
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Vsevolod Golovanov
>
> I need to add a dynamic URL parameter to a location of a page before navigating to it.
> I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding.
> A special landing page would be a pretty ugly workaround.
> I get that it's not possible with annotations. But at least support this with Graphene.goTo methods.
> Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}.



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

From issues at jboss.org  Thu Mar 30 07:04:00 2017
From: issues at jboss.org (Vsevolod Golovanov (JIRA))
Date: Thu, 30 Mar 2017 07:04:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL
	parameters
In-Reply-To: <JIRA.12685068.1490815855000@Atlassian.JIRA>
References: <JIRA.12685068.1490815855000@Atlassian.JIRA>
	<JIRA.12685068.1490815855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685068.1490815855000.27267.1490871840102@Atlassian.JIRA>


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

Vsevolod Golovanov commented on ARQGRA-500:
-------------------------------------------

An example implementation of the LocationParameterProvider approach via overriding Graphene's LocationDecider is at http://stackoverflow.com/a/43115879/1341535

Now the interface seems weird to me. Maybe annotations would be more in line here with other Graphene stuff. \@LocationParameters on a field (outjection at navigation time) or a method (callback).

> Navigation with URL parameters
> ------------------------------
>
>                 Key: ARQGRA-500
>                 URL: https://issues.jboss.org/browse/ARQGRA-500
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Vsevolod Golovanov
>
> I need to add a dynamic URL parameter to a location of a page before navigating to it.
> I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding.
> A special landing page would be a pretty ugly workaround.
> I get that it's not possible with annotations. But at least support this with Graphene.goTo methods.
> Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}.



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

From issues at jboss.org  Thu Mar 30 07:51:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 30 Mar 2017 07:51:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-494) Enrich WebElements
 returned by JavascriptExecutor (to protect against staleness etc)
In-Reply-To: <JIRA.12671428.1484581817000@Atlassian.JIRA>
References: <JIRA.12671428.1484581817000@Atlassian.JIRA>
	<JIRA.12671428.1484581817000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12671428.1484581817000.28137.1490874660641@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-494:
---------------------------------------

Hi [~vsevolodgolovanov]
Thank you for reporting this. If you have some working fix already for this issue, feel free to send PR. We would be very thankful. 
Our time and knowledge for maintaining this project are very limited, so we are glad for any help.

> Enrich WebElements returned by JavascriptExecutor (to protect against staleness etc)
> ------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-494
>                 URL: https://issues.jboss.org/browse/ARQGRA-494
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Final
>            Reporter: Vsevolod Golovanov
>
> ARQGRA-252 took care of elements found by manually calling SearchContext#findElement*, but there is still org.openqa.selenium.JavascriptExecutor:
> {code}
> jsExecutor.executeScript("return $('*').toArray();");
> {code}
> This would return unproxified WebElement instances.



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

From issues at jboss.org  Thu Mar 30 07:52:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 30 Mar 2017 07:52:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-496) JavaScript interface
 returns null instead of false for Booleans
In-Reply-To: <JIRA.12672270.1484911568000@Atlassian.JIRA>
References: <JIRA.12672270.1484911568000@Atlassian.JIRA>
	<JIRA.12672270.1484911568000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12672270.1484911568000.28148.1490874720455@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-496:
---------------------------------------

Hi [~vsevolodgolovanov]
Thank you for reporting this. If you have some working fix already for this issue, feel free to send PR. We would be very thankful. 
Our time and knowledge for maintaining this project are very limited, so we are glad for any help.

> JavaScript interface returns null instead of false for Booleans
> ---------------------------------------------------------------
>
>                 Key: ARQGRA-496
>                 URL: https://issues.jboss.org/browse/ARQGRA-496
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Final
>            Reporter: Vsevolod Golovanov
>
> {code}
> @JavaScript(value = "MyObject")
> public interface MyJsInterface {
> 	Boolean getSomeValue();
> }
> {code}
> If in js MyObject.someValue === false, then attempting to get the value via Graphene's MyJsInterface will result in null getting returned, instead of false.
> If you declare a primitive boolean return type, then null will get silently 'casted' to false, but that's not something I want either. I want to distinguish the three states with Boolean. I want an exception for null with boolean.
> {code:title=call.js/invokeInterface}
> if (property && target[property]) {
>     return target[property];
> }
> {code}  
> There are 2 problems here.
> # Instead of {{target\[property\]}} there should be an explicit {{typeof(target\[property\]}) !== 'undefined')}} check (or {{property in target}}, if you want to distinguish the "property is defined, but its value is undefined" case).
> # When invokeInterface doesn't find neither getter, nor setter, nor method it quits without returning or throwing anything. There should be some kind of explicit handling if it can't find property/method at all.
> The problem probably affects not only Booleans, but other types with falsey values too.



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

From issues at jboss.org  Thu Mar 30 08:24:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 30 Mar 2017 08:24:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-500) Navigation with URL
	parameters
In-Reply-To: <JIRA.12685068.1490815855000@Atlassian.JIRA>
References: <JIRA.12685068.1490815855000@Atlassian.JIRA>
	<JIRA.12685068.1490815855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12685068.1490815855000.28613.1490876640331@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-500:
---------------------------------------

[~vsevolodgolovanov] interesting solution. If you want, you can try to incorporate it into Graphene and cover it by tests. 

> Navigation with URL parameters
> ------------------------------
>
>                 Key: ARQGRA-500
>                 URL: https://issues.jboss.org/browse/ARQGRA-500
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Vsevolod Golovanov
>
> I need to add a dynamic URL parameter to a location of a page before navigating to it.
> I don't want to use Selenium's navigation, because I would then need to reinvent/shoehorn Graphene's location deciding.
> A special landing page would be a pretty ugly workaround.
> I get that it's not possible with annotations. But at least support this with Graphene.goTo methods.
> Actually it may be possible with annotations, if you could supply some provider class? E.g. {{\@Location(value = "MyView.xhtml", parameterProvider = MyParameterProvider.class)}}.



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

From issues at jboss.org  Fri Mar 31 12:40:00 2017
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 31 Mar 2017 12:40:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1699) PhantomJS resolution by
	Spacelift
In-Reply-To: <JIRA.12534576.1394464682000@Atlassian.JIRA>
References: <JIRA.12534576.1394464682000@Atlassian.JIRA>
	<JIRA.12534576.1394464682000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534576.1394464682000.39210.1490978400393@Atlassian.JIRA>


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

Matous Jobanek updated ARQ-1699:
--------------------------------
    Fix Version/s: drone_2.1.0.Beta1
                       (was: drone_2.1.0.Final)


> PhantomJS resolution by Spacelift
> ---------------------------------
>
>                 Key: ARQ-1699
>                 URL: https://issues.jboss.org/browse/ARQ-1699
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.1.0.Beta1
>
>
> PhantomJS resolution should be done via Spacelift.



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