From issues at jboss.org  Mon Feb  1 15:46:00 2016
From: issues at jboss.org (Marc Richards (JIRA))
Date: Mon, 1 Feb 2016 15:46:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with
	arquillian-junit.jar
In-Reply-To: <JIRA.12568783.1429482364000@Atlassian.JIRA>
References: <JIRA.12568783.1429482364000@Atlassian.JIRA>
	<JIRA.12568783.1429482364000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12568783.1429482364000.45148.1454359560234@Atlassian.JIRA>


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

Marc Richards commented on ARQ-1944:
------------------------------------

No, the same classed isn't packaged in multiple jars and I don't have two different implementations with the same name.  I am not all that familiar with how class loaders work or how arquillian does its voodoo, but basically it looks to me like arquillian is using sun/misc/Launcher$AppClassLoader to load the test while Tomcat is using org/apache/catalina/loader/WebappClassLoader to load the backend functionality that responds to the test and myorg/rest/model/OrderStatus is referenced by both, which is not allowed.

Prior to 7.0.51 Tomcat used sun/misc/Launcher$AppClassLoader by default so there was no conflict, however now they have switched to using org/apache/catalina/loader/WebappClassLoader in order to be more inline with the Servlet Specification[1]

{quote}the web application class loader diverges from the default Java delegation model (in accordance with the recommendations in the Servlet Specification, version 2.4, section 9.7.2 Web Application Classloader). When a request to load a class from the web application's WebappX class loader is processed, this class loader will look in the local repositories first, instead of delegating before looking.{quote}

{quote}
Therefore, from the perspective of a web application, class or resource loading looks in the following repositories, in this order:

* Bootstrap classes of your JVM
* /WEB-INF/classes of your web application
* /WEB-INF/lib/*.jar of your web application
* System class loader classes (described above)
* Common class loader classes (described above)

If the web application class loader is configured with <Loader delegate="true"/> then the order becomes:

* Bootstrap classes of your JVM
* System class loader classes (described above)
* Common class loader classes (described above)
* /WEB-INF/classes of your web application
* /WEB-INF/lib/*.jar of your web application
{quote}

So I am using the <Loader delegate="true"/> workaround for now. Hopefully the arqullian team can figure out a way to make things work without the workaround.

[1] https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html#Class_Loader_Definitions

> Linkage error with arquillian-junit.jar
> ---------------------------------------
>
>                 Key: ARQ-1944
>                 URL: https://issues.jboss.org/browse/ARQ-1944
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final
>         Environment: JDK7, Windows 7 x64, Linux x64
>            Reporter: Chris Rankin
>         Attachments: arquillian-hamcrest-test.tar.xz
>
>
> Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine).
> The test fails with this error message:
> {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT
> testTrouble(org.testing.web.TroubleIT)  Time elapsed: 0.774 sec  <<< ERROR!
> java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature
> 	at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35)
> {code}
> This error can be resolved in four different ways:
> - Rewrite the test using TestNG
> - Rewrite the test without using any Hamcrest matchers.
> - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}.
> - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place.
> See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb  1 15:46:00 2016
From: issues at jboss.org (Marc Richards (JIRA))
Date: Mon, 1 Feb 2016 15:46:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with
	arquillian-junit.jar
In-Reply-To: <JIRA.12568783.1429482364000@Atlassian.JIRA>
References: <JIRA.12568783.1429482364000@Atlassian.JIRA>
	<JIRA.12568783.1429482364000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12568783.1429482364000.45149.1454359560256@Atlassian.JIRA>


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

Marc Richards edited comment on ARQ-1944 at 2/1/16 3:45 PM:
------------------------------------------------------------

No, the same classed isn't packaged in multiple jars and I don't have two different implementations with the same name.  I am not all that familiar with how class loaders work or how arquillian does its voodoo, but basically it looks to me like arquillian is using *sun/misc/Launcher$AppClassLoader* to load the test while Tomcat is using *org/apache/catalina/loader/WebappClassLoader* to load the backend functionality that responds to the test and myorg/rest/model/OrderStatus is referenced by both, which is not allowed.

Prior to 7.0.51 Tomcat used sun/misc/Launcher$AppClassLoader by default so there was no conflict, however now they have switched to using org/apache/catalina/loader/WebappClassLoader in order to be more inline with the Servlet Specification[1]

{quote}the web application class loader diverges from the default Java delegation model (in accordance with the recommendations in the Servlet Specification, version 2.4, section 9.7.2 Web Application Classloader). When a request to load a class from the web application's WebappX class loader is processed, this class loader will look in the local repositories first, instead of delegating before looking.{quote}

{quote}
Therefore, from the perspective of a web application, class or resource loading looks in the following repositories, in this order:

* Bootstrap classes of your JVM
* /WEB-INF/classes of your web application
* /WEB-INF/lib/*.jar of your web application
* System class loader classes (described above)
* Common class loader classes (described above)

If the web application class loader is configured with <Loader delegate="true"/> then the order becomes:

* Bootstrap classes of your JVM
* System class loader classes (described above)
* Common class loader classes (described above)
* /WEB-INF/classes of your web application
* /WEB-INF/lib/*.jar of your web application
{quote}

So I am using the <Loader delegate="true"/> workaround for now. Hopefully the arqullian team can figure out a way to make things work without the workaround.

[1] https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html#Class_Loader_Definitions


was (Author: talawahdotnet):
No, the same classed isn't packaged in multiple jars and I don't have two different implementations with the same name.  I am not all that familiar with how class loaders work or how arquillian does its voodoo, but basically it looks to me like arquillian is using sun/misc/Launcher$AppClassLoader to load the test while Tomcat is using org/apache/catalina/loader/WebappClassLoader to load the backend functionality that responds to the test and myorg/rest/model/OrderStatus is referenced by both, which is not allowed.

Prior to 7.0.51 Tomcat used sun/misc/Launcher$AppClassLoader by default so there was no conflict, however now they have switched to using org/apache/catalina/loader/WebappClassLoader in order to be more inline with the Servlet Specification[1]

{quote}the web application class loader diverges from the default Java delegation model (in accordance with the recommendations in the Servlet Specification, version 2.4, section 9.7.2 Web Application Classloader). When a request to load a class from the web application's WebappX class loader is processed, this class loader will look in the local repositories first, instead of delegating before looking.{quote}

{quote}
Therefore, from the perspective of a web application, class or resource loading looks in the following repositories, in this order:

* Bootstrap classes of your JVM
* /WEB-INF/classes of your web application
* /WEB-INF/lib/*.jar of your web application
* System class loader classes (described above)
* Common class loader classes (described above)

If the web application class loader is configured with <Loader delegate="true"/> then the order becomes:

* Bootstrap classes of your JVM
* System class loader classes (described above)
* Common class loader classes (described above)
* /WEB-INF/classes of your web application
* /WEB-INF/lib/*.jar of your web application
{quote}

So I am using the <Loader delegate="true"/> workaround for now. Hopefully the arqullian team can figure out a way to make things work without the workaround.

[1] https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html#Class_Loader_Definitions

> Linkage error with arquillian-junit.jar
> ---------------------------------------
>
>                 Key: ARQ-1944
>                 URL: https://issues.jboss.org/browse/ARQ-1944
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final
>         Environment: JDK7, Windows 7 x64, Linux x64
>            Reporter: Chris Rankin
>         Attachments: arquillian-hamcrest-test.tar.xz
>
>
> Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine).
> The test fails with this error message:
> {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT
> testTrouble(org.testing.web.TroubleIT)  Time elapsed: 0.774 sec  <<< ERROR!
> java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature
> 	at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35)
> {code}
> This error can be resolved in four different ways:
> - Rewrite the test using TestNG
> - Rewrite the test without using any Hamcrest matchers.
> - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}.
> - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place.
> See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb  1 16:40:00 2016
From: issues at jboss.org (Chris Rankin (JIRA))
Date: Mon, 1 Feb 2016 16:40:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with
	arquillian-junit.jar
In-Reply-To: <JIRA.12568783.1429482364000@Atlassian.JIRA>
References: <JIRA.12568783.1429482364000@Atlassian.JIRA>
	<JIRA.12568783.1429482364000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12568783.1429482364000.45537.1454362800249@Atlassian.JIRA>


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

Chris Rankin commented on ARQ-1944:
-----------------------------------

As I understand it, the order in which Tomcat scans different locations for classes cannot possibly matter if every class exists in _exactly one_ location. The reason I raised this bug in the first place is precisely _because_ {{org.hamcrest.*}} exists in more than one place unless extraordinary steps are taken.
The fact that you are also having linkage errors when the loader order changes _strongly suggests_ that you are mistaken somewhere in your belief about how your classes are packaged.
If you look closely, you'll see that my own error also mentioned {{sun.misc.Launcher$AppClassLoader}}:
{code}java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature{code}
So I think that's a {color:red}red herring{color} because my problem really(\!) was caused by duplicated classes.


> Linkage error with arquillian-junit.jar
> ---------------------------------------
>
>                 Key: ARQ-1944
>                 URL: https://issues.jboss.org/browse/ARQ-1944
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final
>         Environment: JDK7, Windows 7 x64, Linux x64
>            Reporter: Chris Rankin
>         Attachments: arquillian-hamcrest-test.tar.xz
>
>
> Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine).
> The test fails with this error message:
> {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT
> testTrouble(org.testing.web.TroubleIT)  Time elapsed: 0.774 sec  <<< ERROR!
> java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature
> 	at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35)
> {code}
> This error can be resolved in four different ways:
> - Rewrite the test using TestNG
> - Rewrite the test without using any Hamcrest matchers.
> - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}.
> - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place.
> See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb  1 16:50:00 2016
From: issues at jboss.org (Chris Rankin (JIRA))
Date: Mon, 1 Feb 2016 16:50:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with
	arquillian-junit.jar
In-Reply-To: <JIRA.12568783.1429482364000@Atlassian.JIRA>
References: <JIRA.12568783.1429482364000@Atlassian.JIRA>
	<JIRA.12568783.1429482364000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12568783.1429482364000.45569.1454363400230@Atlassian.JIRA>


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

Chris Rankin commented on ARQ-1944:
-----------------------------------

Hmm, is your {{myorg/rest/model/OrderStatus}} class imported via a Maven {{<dependency>}} from your local repository? Because I've noticed {{maven-failsafe-plugin}} put things on the integration test classpath twice before. Whenever I've had this problem, I've needed to add something like this to the failsafe plugin's configuration:
{code:xml}<configuration>
    <classpathDependencyExcludes>
        <classpathDependencyExclude>groupdId:artifactId</classpathDependencyExclude>
    </classpathDependencyExcludes>
</configuration>{code}
Although having said that, I've never had a linkage error because of this.

> Linkage error with arquillian-junit.jar
> ---------------------------------------
>
>                 Key: ARQ-1944
>                 URL: https://issues.jboss.org/browse/ARQ-1944
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final
>         Environment: JDK7, Windows 7 x64, Linux x64
>            Reporter: Chris Rankin
>         Attachments: arquillian-hamcrest-test.tar.xz
>
>
> Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine).
> The test fails with this error message:
> {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT
> testTrouble(org.testing.web.TroubleIT)  Time elapsed: 0.774 sec  <<< ERROR!
> java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature
> 	at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35)
> {code}
> This error can be resolved in four different ways:
> - Rewrite the test using TestNG
> - Rewrite the test without using any Hamcrest matchers.
> - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}.
> - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place.
> See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 07:37:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 07:37:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1696) Update documentation to
	cover Drone 2.0.0
In-Reply-To: <JIRA.12534573.1394464535000@Atlassian.JIRA>
References: <JIRA.12534573.1394464535000@Atlassian.JIRA>
	<JIRA.12534573.1394464535000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534573.1394464535000.48047.1454416620360@Atlassian.JIRA>


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

Matous Jobanek reassigned ARQ-1696:
-----------------------------------

    Assignee: Matous Jobanek


> Update documentation to cover Drone 2.0.0
> -----------------------------------------
>
>                 Key: ARQ-1696
>                 URL: https://issues.jboss.org/browse/ARQ-1696
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Update documentation to cover Arquillian Drone 2.0.0. Graphene 2 being the most prominent citizen here.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 07:37:01 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 07:37:01 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1696) Update documentation to
	cover Drone 2.0.0
In-Reply-To: <JIRA.12534573.1394464535000@Atlassian.JIRA>
References: <JIRA.12534573.1394464535000@Atlassian.JIRA>
	<JIRA.12534573.1394464535000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534573.1394464535000.48060.1454416621248@Atlassian.JIRA>


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

Matous Jobanek commented on ARQ-1696:
-------------------------------------

Updated https://docs.jboss.org/author/display/ARQ/Drone

> Update documentation to cover Drone 2.0.0
> -----------------------------------------
>
>                 Key: ARQ-1696
>                 URL: https://issues.jboss.org/browse/ARQ-1696
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Update documentation to cover Arquillian Drone 2.0.0. Graphene 2 being the most prominent citizen here.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 07:38:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 07:38:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1696) Update documentation to
	cover Drone 2.0.0
In-Reply-To: <JIRA.12534573.1394464535000@Atlassian.JIRA>
References: <JIRA.12534573.1394464535000@Atlassian.JIRA>
	<JIRA.12534573.1394464535000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534573.1394464535000.48077.1454416680882@Atlassian.JIRA>


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

Matous Jobanek resolved ARQ-1696.
---------------------------------
    Resolution: Done


> Update documentation to cover Drone 2.0.0
> -----------------------------------------
>
>                 Key: ARQ-1696
>                 URL: https://issues.jboss.org/browse/ARQ-1696
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Update documentation to cover Arquillian Drone 2.0.0. Graphene 2 being the most prominent citizen here.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 07:39:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 07:39:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1697) Migration guide for
	users
In-Reply-To: <JIRA.12534574.1394464579000@Atlassian.JIRA>
References: <JIRA.12534574.1394464579000@Atlassian.JIRA>
	<JIRA.12534574.1394464579000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534574.1394464579000.48080.1454416740449@Atlassian.JIRA>


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

Matous Jobanek reassigned ARQ-1697:
-----------------------------------

    Assignee: Matous Jobanek


> Migration guide for users
> -------------------------
>
>                 Key: ARQ-1697
>                 URL: https://issues.jboss.org/browse/ARQ-1697
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Provide a migration guide to help users use Drone 2.0.0 instead of 1.2.x/1.3.x.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 10:01:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 10:01:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1697) Migration guide for
	users
In-Reply-To: <JIRA.12534574.1394464579000@Atlassian.JIRA>
References: <JIRA.12534574.1394464579000@Atlassian.JIRA>
	<JIRA.12534574.1394464579000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534574.1394464579000.49544.1454425260433@Atlassian.JIRA>


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

Matous Jobanek resolved ARQ-1697.
---------------------------------
    Resolution: Done


https://github.com/arquillian/arquillian-extension-drone/wiki/Home/
https://github.com/arquillian/arquillian-extension-drone/wiki/API-changes-in-Drone-2

> Migration guide for users
> -------------------------
>
>                 Key: ARQ-1697
>                 URL: https://issues.jboss.org/browse/ARQ-1697
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Provide a migration guide to help users use Drone 2.0.0 instead of 1.2.x/1.3.x.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 10:02:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 10:02:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1698) Migration guide for
	developers
In-Reply-To: <JIRA.12534575.1394464618000@Atlassian.JIRA>
References: <JIRA.12534575.1394464618000@Atlassian.JIRA>
	<JIRA.12534575.1394464618000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534575.1394464618000.49558.1454425320476@Atlassian.JIRA>


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

Matous Jobanek resolved ARQ-1698.
---------------------------------
      Assignee: Matous Jobanek
    Resolution: Done


https://github.com/arquillian/arquillian-extension-drone/wiki
https://github.com/arquillian/arquillian-extension-drone/wiki/SPI-changes-in-Drone-2

> Migration guide for developers
> ------------------------------
>
>                 Key: ARQ-1698
>                 URL: https://issues.jboss.org/browse/ARQ-1698
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Provide a migration guide for developers updating their extensions from 1.2/1.3 to 2.0.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 10:08:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 10:08:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1995) Update to latest
 version of Selenium and Arquillian core
In-Reply-To: <JIRA.12589590.1445260708000@Atlassian.JIRA>
References: <JIRA.12589590.1445260708000@Atlassian.JIRA>
	<JIRA.12589590.1445260708000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12589590.1445260708000.49602.1454425680231@Atlassian.JIRA>


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

Matous Jobanek resolved ARQ-1995.
---------------------------------
    Resolution: Done


The latest versions the Drone has been updated to are: 
arquillian-core 1.1.11.Final https://github.com/arquillian/arquillian-extension-drone/commit/309c223712e3f46865b9deeedd711c1533eeedfa
selenium 2.50.1 https://github.com/arquillian/arquillian-extension-drone/commit/33fd2457fb110d8639fa326df35fd6e9995a128b


> Update to latest version of Selenium and Arquillian core
> --------------------------------------------------------
>
>                 Key: ARQ-1995
>                 URL: https://issues.jboss.org/browse/ARQ-1995
>             Project: Arquillian
>          Issue Type: Component  Upgrade
>          Components: Extension - Drone
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 10:10:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 2 Feb 2016 10:10:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2006) ISE for
 deployment-scoped drone point when manual deployment is used
In-Reply-To: <JIRA.12599127.1452609137000@Atlassian.JIRA>
References: <JIRA.12599127.1452609137000@Atlassian.JIRA>
	<JIRA.12599127.1452609137000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12599127.1452609137000.49625.1454425800319@Atlassian.JIRA>


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

Matous Jobanek updated ARQ-2006:
--------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


Pushed upstream in: 
https://github.com/arquillian/arquillian-extension-drone/commit/2ca9f31a1943aa66296c4a01fda78620f8ab2b13
https://github.com/arquillian/arquillian-extension-drone/commit/75f0db0ac65d3edef439cca099bcf10bca8e4f97

> ISE for deployment-scoped drone point when manual deployment is used
> --------------------------------------------------------------------
>
>                 Key: ARQ-2006
>                 URL: https://issues.jboss.org/browse/ARQ-2006
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>    Affects Versions: drone_2.0.0.Alpha5
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Consider these scenarios:
> 1)
> {code:java}
>     @Deployment(name = "first", managed = false)
>     public static Archive deployFirst() {
>         return ShrinkWrap.create(WebArchive.class);
>     }
>     @Deployment(name = "second")
>     public static WebArchive deploySecond() {
>         return ShrinkWrap.create(WebArchive.class);
>     }
>     @ArquillianResource
>     private Deployer deployer;
>     @Drone
>     @OperateOnDeployment("first")
>     private WebDriver firstBrowser;
>     @Drone
>     @OperateOnDeployment("second")
>     private WebDriver secondBrowser;
>     @Test
>     @InSequence(1)
>     public void runFirstTest() throws InterruptedException {
>         deployer.deploy("first");
>         firstBrowser.get("http://google.com");
>         deployer.undeploy("first");
>     }
>     @Test
>     @InSequence(2)
>     public void runSecondTest() throws InterruptedException {
>         secondBrowser.get("http://google.com");
>     }
> {code}
> 2)
> {code:java}
>     @Deployment(name = "deployment", managed = false)
>     public static Archive deployFirst() {
>         return ShrinkWrap.create(WebArchive.class);
>     }
>     @ArquillianResource
>     private Deployer deployer;
>     @Drone
>     @OperateOnDeployment("deployment")
>     private WebDriver browser;
>     @Test
>     @InSequence(1)
>     public void runFirstTest() throws InterruptedException {
>         deployer.deploy("deployment");
>         browser.get("http://google.com");
>         deployer.undeploy("deployment");
>     }
>     @Test
>     @InSequence(2)
>     public void runSecondTest() throws InterruptedException {
>         deployer.deploy("deployment");
>         browser.get("http://google.com");
>         deployer.undeploy("deployment");
>     }
> {code}
> both of them lead to the IllegalStateException:
> {noformat}
> java.lang.IllegalStateException: Injection point DronePointImpl{droneClass=interface org.openqa.selenium.WebDriver, annotations=[@org.jboss.arquillian.drone.api.annotation.Drone(), @org.jboss.arquillian.container.test.api.OperateOnDeployment(value=deployment)], lifecycle=DEPLOYMENT} has deployment lifecycle and has to be prepared in @BeforeClass.
> 	at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.ensureInjectionPointPrepared(DroneTestEnrichHelper.java:104)
> 	at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.enrichTestClass(DroneTestEnrichHelper.java:72)
> 	at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:54)
> ...
> {noformat}
> The cause: the deployment-scoped drone point is destroyed before undeploy, but created only in BeforeClass. In the first test method the drone point is destroyed, however before the second test method is launched the test class is enriched including the drone point that is already destroyed.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Feb  2 15:37:00 2016
From: issues at jboss.org (Chris Rankin (JIRA))
Date: Tue, 2 Feb 2016 15:37:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1944) Linkage error with
	arquillian-junit.jar
In-Reply-To: <JIRA.12568783.1429482364000@Atlassian.JIRA>
References: <JIRA.12568783.1429482364000@Atlassian.JIRA>
	<JIRA.12568783.1429482364000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12568783.1429482364000.51252.1454445420245@Atlassian.JIRA>


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

Chris Rankin edited comment on ARQ-1944 at 2/2/16 3:36 PM:
-----------------------------------------------------------

Hmm, is your {{myorg/rest/model/OrderStatus}} class imported via a Maven {{<dependency>}} from your local repository? Because I've noticed {{maven-failsafe-plugin}} put things on the integration test classpath twice before inside the embedded Tomcat container. Whenever I've had this problem, I've needed to add something like this to the failsafe plugin's configuration:
{code:xml}<configuration>
    <classpathDependencyExcludes>
        <classpathDependencyExclude>groupdId:artifactId</classpathDependencyExclude>
    </classpathDependencyExcludes>
</configuration>{code}
Although having said that, I've never had a linkage error because of this.


was (Author: chrisjr):
Hmm, is your {{myorg/rest/model/OrderStatus}} class imported via a Maven {{<dependency>}} from your local repository? Because I've noticed {{maven-failsafe-plugin}} put things on the integration test classpath twice before. Whenever I've had this problem, I've needed to add something like this to the failsafe plugin's configuration:
{code:xml}<configuration>
    <classpathDependencyExcludes>
        <classpathDependencyExclude>groupdId:artifactId</classpathDependencyExclude>
    </classpathDependencyExcludes>
</configuration>{code}
Although having said that, I've never had a linkage error because of this.

> Linkage error with arquillian-junit.jar
> ---------------------------------------
>
>                 Key: ARQ-1944
>                 URL: https://issues.jboss.org/browse/ARQ-1944
>             Project: Arquillian
>          Issue Type: Bug
>    Affects Versions: 1.1.7.Final, 1.1.8.Final, 1.1.9.Final, 1.1.10.Final, 1.1.11.Final
>         Environment: JDK7, Windows 7 x64, Linux x64
>            Reporter: Chris Rankin
>         Attachments: arquillian-hamcrest-test.tar.xz
>
>
> Testing a WAR in embedded Tomcat >= 7.0.51 using Restassured, JUnit and Hamcrest matchers. (TestNG works fine).
> The test fails with this error message:
> {code}Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.404 sec <<< FAILURE! - in org.testing.web.TroubleIT
> testTrouble(org.testing.web.TroubleIT)  Time elapsed: 0.774 sec  <<< ERROR!
> java.lang.LinkageError: loader constraint violation: when resolving interface method "com.jayway.restassured.specification.ResponseSpecification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification;" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/testing/web/TroubleIT, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, com/jayway/restassured/specification/ResponseSpecification, have different Class objects for the type cification.statusCode(Lorg/hamcrest/Matcher;)Lcom/jayway/restassured/specification/ResponseSpecification; used in the signature
> 	at org.testing.web.TroubleIT.testTrouble(TroubleIT.java:35)
> {code}
> This error can be resolved in four different ways:
> - Rewrite the test using TestNG
> - Rewrite the test without using any Hamcrest matchers.
> - Remove "org.hamcrest" from {{org.jboss.arquillian.junit.container.JUnitDeploymentAppender}}.
> - Set {{@Deployment(testable = false)}} to prevent Arquillian from packaging its artifacts into the deployment in the first place.
> See [Issue #78 for arquillian-core|https://github.com/arquillian/arquillian-core/issues/78]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:14:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:14:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1743) Merge configuration and
 callable creation together
In-Reply-To: <JIRA.12537226.1396611084000@Atlassian.JIRA>
References: <JIRA.12537226.1396611084000@Atlassian.JIRA>
	<JIRA.12537226.1396611084000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537226.1396611084000.54146.1454508840400@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1743.
-------------------------------


> Merge configuration and callable creation together
> --------------------------------------------------
>
>                 Key: ARQ-1743
>                 URL: https://issues.jboss.org/browse/ARQ-1743
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Extension - Drone
>    Affects Versions: drone_2.0.0.Alpha1
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> There should be just one event and either both or none of the object should be present.
> This mean that callable and configuration should be created at the same time. This would make usage of Drone much easier. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:14:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:14:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1692) Factories should not
 bring runtime dependencies
In-Reply-To: <JIRA.12534568.1394464191000@Atlassian.JIRA>
References: <JIRA.12534568.1394464191000@Atlassian.JIRA>
	<JIRA.12534568.1394464191000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534568.1394464191000.54149.1454508840468@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1692.
-------------------------------


> Factories should not bring runtime dependencies
> -----------------------------------------------
>
>                 Key: ARQ-1692
>                 URL: https://issues.jboss.org/browse/ARQ-1692
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> DroneFactories should fail graciously in case that Drone type they are trying to instantiate are not on classpath.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:15:02 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:15:02 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1340) Drone webdriver is not
 created during @BeforeClass
In-Reply-To: <JIRA.12486577.1362588795000@Atlassian.JIRA>
References: <JIRA.12486577.1362588795000@Atlassian.JIRA>
	<JIRA.12486577.1362588795000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486577.1362588795000.54157.1454508902608@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1340.
-------------------------------


> Drone webdriver is not created during @BeforeClass
> --------------------------------------------------
>
>                 Key: ARQ-1340
>                 URL: https://issues.jboss.org/browse/ARQ-1340
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>    Affects Versions: drone_1.1.1.Final
>         Environment: Arquillian JUnit Container 1.0.3.Final
> Arquillian Graphene Webdriver 2.0.0.Alpha3
> Arquillian Drone dependencies and Selenium dependencies 1.1.1.Final
> Arquillian Core dependencies 1.0.3.Final
> junit 4.8.1
> jdk 1.6
>            Reporter: Alex Okrushko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Drone webdriver is not created during @BeforeClass, however *is created during @Before or if called by GrapheneContext.getProxy()*
> The following does NOT work:
> {code:java} 
> @RunWith(Arquillian.class)
> public class TestDroneLogin {
> 	@Drone
> 	private static WebDriver driver;
> 	
> 	@BeforeClass
> 	public static void setup(){
> //GrapheneContext.getProxy().navigate().to("http://google.com");
> 		driver.navigate().to("http://google.com");
> 	}
> 	
> 	@Test
> 	public void testInput(){
> 		driver.findElement(By.cssSelector("input#gbqfq"));
> 	}
> }
> {code} 
> However, if I use {{GrapheneContext.getProxy()}} instead of {{driver}}, everything works as expected:
> {code:java} 
> @BeforeClass
> 	public static void setup(){
> 		GrapheneContext.getProxy().navigate().to("http://google.com");
> 	}
> {code}
> ALSO, if {{@Before}} is used then Drone webdriver is created as expected, so this problem is specific to {{@BeforeClass}}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:15:02 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:15:02 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1178) Arquillian Drone Module
 page on arquillian.org is out of date
In-Reply-To: <JIRA.12478153.1351610095000@Atlassian.JIRA>
References: <JIRA.12478153.1351610095000@Atlassian.JIRA>
	<JIRA.12478153.1351610095000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12478153.1351610095000.54160.1454508902667@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1178.
-------------------------------


> Arquillian Drone Module page on arquillian.org is out of date
> -------------------------------------------------------------
>
>                 Key: ARQ-1178
>                 URL: https://issues.jboss.org/browse/ARQ-1178
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Description how to use Drone should be improved.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:15:02 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:15:02 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2006) ISE for
 deployment-scoped drone point when manual deployment is used
In-Reply-To: <JIRA.12599127.1452609137000@Atlassian.JIRA>
References: <JIRA.12599127.1452609137000@Atlassian.JIRA>
	<JIRA.12599127.1452609137000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12599127.1452609137000.54165.1454508902781@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-2006.
-------------------------------


> ISE for deployment-scoped drone point when manual deployment is used
> --------------------------------------------------------------------
>
>                 Key: ARQ-2006
>                 URL: https://issues.jboss.org/browse/ARQ-2006
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Drone
>    Affects Versions: drone_2.0.0.Alpha5
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Consider these scenarios:
> 1)
> {code:java}
>     @Deployment(name = "first", managed = false)
>     public static Archive deployFirst() {
>         return ShrinkWrap.create(WebArchive.class);
>     }
>     @Deployment(name = "second")
>     public static WebArchive deploySecond() {
>         return ShrinkWrap.create(WebArchive.class);
>     }
>     @ArquillianResource
>     private Deployer deployer;
>     @Drone
>     @OperateOnDeployment("first")
>     private WebDriver firstBrowser;
>     @Drone
>     @OperateOnDeployment("second")
>     private WebDriver secondBrowser;
>     @Test
>     @InSequence(1)
>     public void runFirstTest() throws InterruptedException {
>         deployer.deploy("first");
>         firstBrowser.get("http://google.com");
>         deployer.undeploy("first");
>     }
>     @Test
>     @InSequence(2)
>     public void runSecondTest() throws InterruptedException {
>         secondBrowser.get("http://google.com");
>     }
> {code}
> 2)
> {code:java}
>     @Deployment(name = "deployment", managed = false)
>     public static Archive deployFirst() {
>         return ShrinkWrap.create(WebArchive.class);
>     }
>     @ArquillianResource
>     private Deployer deployer;
>     @Drone
>     @OperateOnDeployment("deployment")
>     private WebDriver browser;
>     @Test
>     @InSequence(1)
>     public void runFirstTest() throws InterruptedException {
>         deployer.deploy("deployment");
>         browser.get("http://google.com");
>         deployer.undeploy("deployment");
>     }
>     @Test
>     @InSequence(2)
>     public void runSecondTest() throws InterruptedException {
>         deployer.deploy("deployment");
>         browser.get("http://google.com");
>         deployer.undeploy("deployment");
>     }
> {code}
> both of them lead to the IllegalStateException:
> {noformat}
> java.lang.IllegalStateException: Injection point DronePointImpl{droneClass=interface org.openqa.selenium.WebDriver, annotations=[@org.jboss.arquillian.drone.api.annotation.Drone(), @org.jboss.arquillian.container.test.api.OperateOnDeployment(value=deployment)], lifecycle=DEPLOYMENT} has deployment lifecycle and has to be prepared in @BeforeClass.
> 	at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.ensureInjectionPointPrepared(DroneTestEnrichHelper.java:104)
> 	at org.jboss.arquillian.drone.impl.DroneTestEnrichHelper.enrichTestClass(DroneTestEnrichHelper.java:72)
> 	at org.jboss.arquillian.drone.impl.DroneTestEnricher.enrich(DroneTestEnricher.java:54)
> ...
> {noformat}
> The cause: the deployment-scoped drone point is destroyed before undeploy, but created only in BeforeClass. In the first test method the drone point is destroyed, however before the second test method is launched the test class is enriched including the drone point that is already destroyed.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:15:02 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:15:02 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1995) Update to latest
 version of Selenium and Arquillian core
In-Reply-To: <JIRA.12589590.1445260708000@Atlassian.JIRA>
References: <JIRA.12589590.1445260708000@Atlassian.JIRA>
	<JIRA.12589590.1445260708000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12589590.1445260708000.54167.1454508902827@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1995.
-------------------------------


> Update to latest version of Selenium and Arquillian core
> --------------------------------------------------------
>
>                 Key: ARQ-1995
>                 URL: https://issues.jboss.org/browse/ARQ-1995
>             Project: Arquillian
>          Issue Type: Component  Upgrade
>          Components: Extension - Drone
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:15:02 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:15:02 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1698) Migration guide for
	developers
In-Reply-To: <JIRA.12534575.1394464618000@Atlassian.JIRA>
References: <JIRA.12534575.1394464618000@Atlassian.JIRA>
	<JIRA.12534575.1394464618000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534575.1394464618000.54170.1454508902897@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1698.
-------------------------------


> Migration guide for developers
> ------------------------------
>
>                 Key: ARQ-1698
>                 URL: https://issues.jboss.org/browse/ARQ-1698
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Provide a migration guide for developers updating their extensions from 1.2/1.3 to 2.0.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:15:02 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:15:02 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1697) Migration guide for
	users
In-Reply-To: <JIRA.12534574.1394464579000@Atlassian.JIRA>
References: <JIRA.12534574.1394464579000@Atlassian.JIRA>
	<JIRA.12534574.1394464579000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534574.1394464579000.54173.1454508902977@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1697.
-------------------------------


> Migration guide for users
> -------------------------
>
>                 Key: ARQ-1697
>                 URL: https://issues.jboss.org/browse/ARQ-1697
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Provide a migration guide to help users use Drone 2.0.0 instead of 1.2.x/1.3.x.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb  3 09:15:03 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 3 Feb 2016 09:15:03 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1696) Update documentation to
	cover Drone 2.0.0
In-Reply-To: <JIRA.12534573.1394464535000@Atlassian.JIRA>
References: <JIRA.12534573.1394464535000@Atlassian.JIRA>
	<JIRA.12534573.1394464535000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534573.1394464535000.54176.1454508903128@Atlassian.JIRA>


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

Matous Jobanek closed ARQ-1696.
-------------------------------


> Update documentation to cover Drone 2.0.0
> -----------------------------------------
>
>                 Key: ARQ-1696
>                 URL: https://issues.jboss.org/browse/ARQ-1696
>             Project: Arquillian
>          Issue Type: Task
>          Components: Extension - Drone
>            Reporter: Karel Piwko
>            Assignee: Matous Jobanek
>             Fix For: drone_2.0.0.Beta1
>
>
> Update documentation to cover Arquillian Drone 2.0.0. Graphene 2 being the most prominent citizen here.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Thu Feb  4 06:03:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 4 Feb 2016 06:03:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-477) Upgrade to Core 1.1.8,
 Drone 2.0.0.Alpha5, Selenium 2.47.1
In-Reply-To: <JIRA.12585587.1442867329000@Atlassian.JIRA>
References: <JIRA.12585587.1442867329000@Atlassian.JIRA>
	<JIRA.12585587.1442867329000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12585587.1442867329000.57191.1454583780421@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-477:
---------------------------------------

Sent another PR: https://github.com/arquillian/arquillian-graphene/pull/145

> Upgrade to Core 1.1.8,  Drone 2.0.0.Alpha5, Selenium 2.47.1
> -----------------------------------------------------------
>
>                 Key: ARQGRA-477
>                 URL: https://issues.jboss.org/browse/ARQGRA-477
>             Project: Arquillian Graphene
>          Issue Type: Component  Upgrade
>            Reporter: Luk?? Fry?
>             Fix For: 2.1-Tracking
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Thu Feb  4 10:08:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 4 Feb 2016 10:08:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-471)
 GrapheneContextualHandler: do not wrap AssertionErrors in
 IllegalStateException
In-Reply-To: <JIRA.12573721.1433334611000@Atlassian.JIRA>
References: <JIRA.12573721.1433334611000@Atlassian.JIRA>
	<JIRA.12573721.1433334611000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12573721.1433334611000.58583.1454598480170@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-471:
---------------------------------------

PR: https://github.com/arquillian/arquillian-graphene/pull/147

> GrapheneContextualHandler: do not wrap AssertionErrors in IllegalStateException
> -------------------------------------------------------------------------------
>
>                 Key: ARQGRA-471
>                 URL: https://issues.jboss.org/browse/ARQGRA-471
>             Project: Arquillian Graphene
>          Issue Type: Enhancement
>    Affects Versions: 2.1.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Trivial
>             Fix For: 2.1-Tracking
>
>
> When you perform an assertion in e.g. a page fragment, which leads to throwing an AssertionError, the error is wrapped in IllegalStateException. This is imho an unwanted behaviour and these errors should be forwarded.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Thu Feb  4 10:47:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Thu, 4 Feb 2016 10:47:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in
 WebElementEnricher.enrich() with Arquillian 1.1.5.Final
In-Reply-To: <JIRA.12545062.1404044681000@Atlassian.JIRA>
References: <JIRA.12545062.1404044681000@Atlassian.JIRA>
	<JIRA.12545062.1404044681000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12545062.1404044681000.58829.1454600820667@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-454:
---------------------------------------

Hi, 
this problem should be fixed with the newest version of Arquillian-core (1.1.11.Final).
Just small question - isn't there missing an injected @Drone Webdriver instance in the reproducers? Without that I get the expected exception {{ISE: There is no context available for qualifier.....}}, so just for verification...

> NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final
> --------------------------------------------------------------
>
>                 Key: ARQGRA-454
>                 URL: https://issues.jboss.org/browse/ARQGRA-454
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.3.Final, 2.1.0.Alpha2
>            Reporter: Juergen Zimmermann
>            Assignee: Luk?? Fry?
>             Fix For: 2.0.4.Final, 2.1-Tracking
>
>
> I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final.
> The stacktrace:
> {code}
> org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException:
> Error while initializing: class de.shop.util.IndexPage
>         at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78)
>         at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125)
>         at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120)
>         at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291)
>         at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:483)
>         at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>         at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>         at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
>         at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>         at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267)
>         at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>         at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>         at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>         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:309)
>         at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
>         at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>         at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>         at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.lang.NullPointerException
>         at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68)
>         at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73)
>         at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97)
>         at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76)
>         ... 34 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Mon Feb  8 06:42:00 2016
From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 8 Feb 2016 06:42:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-431) Case insensitive
	matcher
In-Reply-To: <JIRA.12535422.1395242800000@Atlassian.JIRA>
References: <JIRA.12535422.1395242800000@Atlassian.JIRA>
	<JIRA.12535422.1395242800000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535422.1395242800000.65974.1454931720201@Atlassian.JIRA>


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

Ji?? ?tefek commented on ARQGRA-431:
------------------------------------

sent PR ([link|https://github.com/arquillian/arquillian-graphene/pull/149])

> Case insensitive matcher
> ------------------------
>
>                 Key: ARQGRA-431
>                 URL: https://issues.jboss.org/browse/ARQGRA-431
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>          Components: core
>    Affects Versions: 2.0.1.Final
>            Reporter: Karel Piwko
>             Fix For: 2.0-Tracking
>
>
> It is not possible to match text/attribute in case insensitive way.
> {code}
>  Graphene.waitModel().until().element(notify).text().
> {code}
> * .contains(String)
> * .equals(String)
> it should have equalsIgnoreCase as well. A regex matcher would be handy here as well.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Mon Feb  8 07:26:00 2016
From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 8 Feb 2016 07:26:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-417) Support for automatic
 scrolling to element before its usage
In-Reply-To: <JIRA.12529401.1389708311000@Atlassian.JIRA>
References: <JIRA.12529401.1389708311000@Atlassian.JIRA>
	<JIRA.12529401.1389708311000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529401.1389708311000.66198.1454934360165@Atlassian.JIRA>


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

Ji?? ?tefek commented on ARQGRA-417:
------------------------------------

Imho the {{window.scrollTo(x,y)}} function cannot handle elements inside scrollable areas/elements (e.g. div#innerMiddle in https://gist.github.com/jstefek/3bfccc622dfe7c93fe3b). The better choice should be {{element.scrollIntoView()}} ([link|https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView]).

So the code would look like:
{code:java}
jsExecutor.executeScript("arguments[0].scrollIntoView();",element);
{code}


> Support for automatic scrolling to element before its usage
> -----------------------------------------------------------
>
>                 Key: ARQGRA-417
>                 URL: https://issues.jboss.org/browse/ARQGRA-417
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>          Components: core
>    Affects Versions: 2.0.1.Final
>            Reporter: Juraj H?ska
>            Priority: Minor
>             Fix For: 2.2-Tracking
>
>
> It would be nice if Graphene supports automatic scrolling of browser window to {{WebElement}} / Page Fragment before its is used.
> It can be useful for interactions with various popups web components: contextMenu, tooltip, ...
> Those components can not be interacted correctly when they are not in the viewport, and thus one needs to scroll to them manually in his test.
> It is often problem in CI environment, where tests run on screens with lower resolution (smaller part of the page fit the browser window, and lot of elements are not in the viewport).
> My naive implementation of this would look like:
> * intercept all calls to {{WebElements}} and PageFragments root elements
> * in the interceptor method get the location of the element by: {{Point location = element.getLocation();}}
> * a then scroll to it: {{jsExecutor.executeScript("window.scrollTo("" + location.getX() +", " + location.getY() + ")");}}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Wed Feb 10 04:30:00 2016
From: issues at jboss.org (Ondrej Zizka (JIRA))
Date: Wed, 10 Feb 2016 04:30:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-413) Investigate possibility
 of reusing RHQ plugins to implement managed containers.
In-Reply-To: <JIRA.12434930.1302219413000@Atlassian.JIRA>
References: <JIRA.12434930.1302219413000@Atlassian.JIRA>
	<JIRA.12434930.1302219413000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12434930.1302219413000.75813.1455096600830@Atlassian.JIRA>


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

Ondrej Zizka reassigned ARQ-413:
--------------------------------

    Assignee:     (was: Ondrej Zizka)


> Investigate possibility of reusing RHQ plugins to implement managed containers.
> -------------------------------------------------------------------------------
>
>                 Key: ARQ-413
>                 URL: https://issues.jboss.org/browse/ARQ-413
>             Project: Arquillian
>          Issue Type: Task
>            Reporter: Ondrej Zizka
>            Priority: Optional
>
> (01:23:17) OndejZizka: aslak: One more thing, do you know RHQ project?
> (01:23:25) aslak: OndejZizka, yea?
> (01:23:50) OndejZizka: Well then you probably know that it has plugins for many containers
> (01:24:06) OndejZizka: So I thought, this could be re-used to make managed contaiers
> (01:24:26) aslak: hmm.. possible
> (01:24:27) OndejZizka: Basically, they have all it needs - starting, stopping, deploy/undeploy, config
> (01:24:34) OndejZizka: + some extras where possible
> (01:25:01) aslak: OndejZizka, got a url for source?
> (01:25:05) OndejZizka: Sure, sec
> (01:25:08) aslak: container source
> (01:25:21) OndejZizka: aslak: http://git.fedorahosted.org/git/?p=rhq/rhq.git;
> (01:26:00) OndejZizka: aslak:  The source is vast. Not easy to locate concrete functionality, but plugins are separated as modules
> (01:37:52) jshaughn: ozizka-here: The CLI speaks only to the server
> (01:38:12) jshaughn: The only thing that comes close perhaps to what you're asking is the standalone plugin container
> jsanda_afk jshaughn 
> (01:38:30) ozizka-here: jshaughn: Sounds promising, continue pls :)
> (01:38:36) jshaughn: this is a tool that is typically used to help rapid devleopment of plugins
> (01:39:14) jshaughn: it allows a plugin to basically run and gives a command line interface for executing its implementd factes
> (01:39:24) jshaughn: sorry, "facets"
> (01:39:42) jshaughn: I actually have not used it but let me see if I can track down a link
> (01:40:17) jshaughn: Heiko (pilhuhn) is the implementor and resident expert.
> (01:47:53) jshaughn: there is a video of it here: http://wiki.rhq-project.org/display/RHQ/Videos "Using the standalone plugin-container when developing RHQ plugins"
> (01:51:05) jshaughn: http://community.jboss.org/en/jopr/blog/2011/01/20/using-the-standalone-container-for-development



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb 10 06:05:00 2016
From: issues at jboss.org (Ladislav Thon (JIRA))
Date: Wed, 10 Feb 2016 06:05:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue
	with injected deployer
In-Reply-To: <JIRA.12566592.1427106139000@Atlassian.JIRA>
References: <JIRA.12566592.1427106139000@Atlassian.JIRA>
	<JIRA.12566592.1427106139000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12566592.1427106139000.76692.1455102300256@Atlassian.JIRA>


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

Ladislav Thon commented on ARQ-1937:
------------------------------------

I'd like to understand more about this.

In my tests, I'm often intentionally setting my {{@Deployment}} to {{testable = false}}, or I have no {{@Deployment}} at all, with the intention that the test will run as client. I never use {{@RunAsClient}}, simply because it's superfluous. Yet I started to get warnings now.

Am I absolutely positively supposed to use {{@RunAsClient}} when I want the test to run as client?

> Class loading issue with injected deployer 
> -------------------------------------------
>
>                 Key: ARQ-1937
>                 URL: https://issues.jboss.org/browse/ARQ-1937
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.11.Final
>
>
> Steps to reproduce:
> 1) inject a Deployer via @ArquillianResource
> 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container
> 3) run a test method that operates on the deployment
> 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader())
> 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader
> In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in <dependencies> while the older version is downloaded separately via Maven dependency plugin.
> {code}
> package com.jboss.datagrid.test.backwardcompatibility;
> @RunWith(Arquillian.class)
> public class SingleFileStoreBackwardCompatibilityIT {
>     private DefaultCacheManager dfc;
>     private String cacheName = "testCache";
>     private static final String OLD_ISPN = "dep1_with_old_ispn";
>     private static final String NEW_ISPN = "dep2_with_new_ispn";
>     private static Map<String, String> storedMap;
>     @ArquillianResource
>     Deployer deployer;
>     @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1)
>     @TargetsContainer("container1")
>     public static WebArchive createDeploymentOld() {
>         WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous");
>         System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader());
>         return jar;
>     }
>     @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2)
>     @TargetsContainer("container2")
>     public static WebArchive createDeploymentNew() {
>         WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current");
>         return jar;
>     }
>     private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception {
>         GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault()
>                 .globalJmxStatistics().allowDuplicateDomains(true).
>                         build();
>         ConfigurationBuilder c = new ConfigurationBuilder();
>         c.clustering().cacheMode(CacheMode.LOCAL);
>         File tmpStore = new File("/tmp/cache/" + cacheName + ".dat");
>         if (clearCacheStore && tmpStore.exists()) {
>             tmpStore.delete();
>         }
>         c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/");
>         Configuration cnf = c.build();
>         DefaultCacheManager manager = new DefaultCacheManager(glob);
>         manager.defineConfiguration(cacheName, cnf);
>         return manager;
>     }
>     @Test
>     @OperateOnDeployment(OLD_ISPN)
>     @InSequence(1)
>     public void testStoreWithOldJDG() throws Exception {
>         deployer.deploy(OLD_ISPN);
>         dfc = configureCacheManager(true);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("Version: " + cache.getVersion());
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         storedMap = new HashMap<String, String>();
>         storedMap.put("k", "v");
>         cache.put("mapKey", storedMap);
>         dfc.stop();
>         deployer.undeploy(OLD_ISPN);
>     }
>     @Test
>     @OperateOnDeployment(NEW_ISPN)
>     @InSequence(2)
>     public void testReadWithNewJDG() throws Exception {
>         deployer.deploy(NEW_ISPN);
>         dfc = configureCacheManager(false);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         System.out.println("Version: " + cache.getVersion());
>         assertEquals(storedMap, cache.get("mapKey"));
>         dfc.stop();
>         deployer.undeploy(NEW_ISPN);
>     }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb 10 06:13:00 2016
From: issues at jboss.org (Ladislav Thon (JIRA))
Date: Wed, 10 Feb 2016 06:13:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue
	with injected deployer
In-Reply-To: <JIRA.12566592.1427106139000@Atlassian.JIRA>
References: <JIRA.12566592.1427106139000@Atlassian.JIRA>
	<JIRA.12566592.1427106139000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12566592.1427106139000.76750.1455102780391@Atlassian.JIRA>


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

Ladislav Thon commented on ARQ-1937:
------------------------------------

After looking at Arquillian code and my project where I'm getting the warnings, I need to clarify my previous comment -- I'm only getting warnings when there is no {{@Deployment}} at all. This might be a corner case, but I actually have quite a lot of tests like that :-)

> Class loading issue with injected deployer 
> -------------------------------------------
>
>                 Key: ARQ-1937
>                 URL: https://issues.jboss.org/browse/ARQ-1937
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.11.Final
>
>
> Steps to reproduce:
> 1) inject a Deployer via @ArquillianResource
> 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container
> 3) run a test method that operates on the deployment
> 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader())
> 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader
> In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in <dependencies> while the older version is downloaded separately via Maven dependency plugin.
> {code}
> package com.jboss.datagrid.test.backwardcompatibility;
> @RunWith(Arquillian.class)
> public class SingleFileStoreBackwardCompatibilityIT {
>     private DefaultCacheManager dfc;
>     private String cacheName = "testCache";
>     private static final String OLD_ISPN = "dep1_with_old_ispn";
>     private static final String NEW_ISPN = "dep2_with_new_ispn";
>     private static Map<String, String> storedMap;
>     @ArquillianResource
>     Deployer deployer;
>     @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1)
>     @TargetsContainer("container1")
>     public static WebArchive createDeploymentOld() {
>         WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous");
>         System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader());
>         return jar;
>     }
>     @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2)
>     @TargetsContainer("container2")
>     public static WebArchive createDeploymentNew() {
>         WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current");
>         return jar;
>     }
>     private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception {
>         GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault()
>                 .globalJmxStatistics().allowDuplicateDomains(true).
>                         build();
>         ConfigurationBuilder c = new ConfigurationBuilder();
>         c.clustering().cacheMode(CacheMode.LOCAL);
>         File tmpStore = new File("/tmp/cache/" + cacheName + ".dat");
>         if (clearCacheStore && tmpStore.exists()) {
>             tmpStore.delete();
>         }
>         c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/");
>         Configuration cnf = c.build();
>         DefaultCacheManager manager = new DefaultCacheManager(glob);
>         manager.defineConfiguration(cacheName, cnf);
>         return manager;
>     }
>     @Test
>     @OperateOnDeployment(OLD_ISPN)
>     @InSequence(1)
>     public void testStoreWithOldJDG() throws Exception {
>         deployer.deploy(OLD_ISPN);
>         dfc = configureCacheManager(true);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("Version: " + cache.getVersion());
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         storedMap = new HashMap<String, String>();
>         storedMap.put("k", "v");
>         cache.put("mapKey", storedMap);
>         dfc.stop();
>         deployer.undeploy(OLD_ISPN);
>     }
>     @Test
>     @OperateOnDeployment(NEW_ISPN)
>     @InSequence(2)
>     public void testReadWithNewJDG() throws Exception {
>         deployer.deploy(NEW_ISPN);
>         dfc = configureCacheManager(false);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         System.out.println("Version: " + cache.getVersion());
>         assertEquals(storedMap, cache.get("mapKey"));
>         dfc.stop();
>         deployer.undeploy(NEW_ISPN);
>     }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb 10 07:12:01 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 10 Feb 2016 07:12:01 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue
	with injected deployer
In-Reply-To: <JIRA.12566592.1427106139000@Atlassian.JIRA>
References: <JIRA.12566592.1427106139000@Atlassian.JIRA>
	<JIRA.12566592.1427106139000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12566592.1427106139000.77121.1455106321102@Atlassian.JIRA>


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

Matous Jobanek commented on ARQ-1937:
-------------------------------------

Hi,
yeah, I have to admit that the warning wasn't good idea - I will fix it.

> Class loading issue with injected deployer 
> -------------------------------------------
>
>                 Key: ARQ-1937
>                 URL: https://issues.jboss.org/browse/ARQ-1937
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.11.Final
>
>
> Steps to reproduce:
> 1) inject a Deployer via @ArquillianResource
> 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container
> 3) run a test method that operates on the deployment
> 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader())
> 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader
> In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in <dependencies> while the older version is downloaded separately via Maven dependency plugin.
> {code}
> package com.jboss.datagrid.test.backwardcompatibility;
> @RunWith(Arquillian.class)
> public class SingleFileStoreBackwardCompatibilityIT {
>     private DefaultCacheManager dfc;
>     private String cacheName = "testCache";
>     private static final String OLD_ISPN = "dep1_with_old_ispn";
>     private static final String NEW_ISPN = "dep2_with_new_ispn";
>     private static Map<String, String> storedMap;
>     @ArquillianResource
>     Deployer deployer;
>     @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1)
>     @TargetsContainer("container1")
>     public static WebArchive createDeploymentOld() {
>         WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous");
>         System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader());
>         return jar;
>     }
>     @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2)
>     @TargetsContainer("container2")
>     public static WebArchive createDeploymentNew() {
>         WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current");
>         return jar;
>     }
>     private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception {
>         GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault()
>                 .globalJmxStatistics().allowDuplicateDomains(true).
>                         build();
>         ConfigurationBuilder c = new ConfigurationBuilder();
>         c.clustering().cacheMode(CacheMode.LOCAL);
>         File tmpStore = new File("/tmp/cache/" + cacheName + ".dat");
>         if (clearCacheStore && tmpStore.exists()) {
>             tmpStore.delete();
>         }
>         c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/");
>         Configuration cnf = c.build();
>         DefaultCacheManager manager = new DefaultCacheManager(glob);
>         manager.defineConfiguration(cacheName, cnf);
>         return manager;
>     }
>     @Test
>     @OperateOnDeployment(OLD_ISPN)
>     @InSequence(1)
>     public void testStoreWithOldJDG() throws Exception {
>         deployer.deploy(OLD_ISPN);
>         dfc = configureCacheManager(true);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("Version: " + cache.getVersion());
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         storedMap = new HashMap<String, String>();
>         storedMap.put("k", "v");
>         cache.put("mapKey", storedMap);
>         dfc.stop();
>         deployer.undeploy(OLD_ISPN);
>     }
>     @Test
>     @OperateOnDeployment(NEW_ISPN)
>     @InSequence(2)
>     public void testReadWithNewJDG() throws Exception {
>         deployer.deploy(NEW_ISPN);
>         dfc = configureCacheManager(false);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         System.out.println("Version: " + cache.getVersion());
>         assertEquals(storedMap, cache.get("mapKey"));
>         dfc.stop();
>         deployer.undeploy(NEW_ISPN);
>     }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Fri Feb 12 09:23:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 12 Feb 2016 09:23:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-473)
 ClassNotFoundException: org.openqa.selenium.html5.DatabaseStorage with
 Selenium 2.46.0
In-Reply-To: <JIRA.12577773.1436774011000@Atlassian.JIRA>
References: <JIRA.12577773.1436774011000@Atlassian.JIRA>
	<JIRA.12577773.1436774011000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12577773.1436774011000.87156.1455286980567@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-473:
---------------------------------------

I would recommend to close this issue as won't fix and keep the code there - because of backward compatibility. 

> ClassNotFoundException: org.openqa.selenium.html5.DatabaseStorage with Selenium 2.46.0
> --------------------------------------------------------------------------------------
>
>                 Key: ARQGRA-473
>                 URL: https://issues.jboss.org/browse/ARQGRA-473
>             Project: Arquillian Graphene
>          Issue Type: Bug
>    Affects Versions: 2.1.0.Alpha2
>            Reporter: Matous Jobanek
>             Fix For: 2.1-Tracking
>
>
> Graphene is not compatible with the latest Selenium 2.46.0. It throws {{ClassNotFoundException: org.openqa.selenium.html5.DatabaseStorage}}
> DatabaseStorage is deprecated class, that is not included it the latest Selenium.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Fri Feb 12 09:26:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 12 Feb 2016 09:26:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-454) NPE in
 WebElementEnricher.enrich() with Arquillian 1.1.5.Final
In-Reply-To: <JIRA.12545062.1404044681000@Atlassian.JIRA>
References: <JIRA.12545062.1404044681000@Atlassian.JIRA>
	<JIRA.12545062.1404044681000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12545062.1404044681000.87170.1455287160816@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-454:
---------------------------------------

Here is PR with the test case https://github.com/arquillian/arquillian-graphene/pull/148

> NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final
> --------------------------------------------------------------
>
>                 Key: ARQGRA-454
>                 URL: https://issues.jboss.org/browse/ARQGRA-454
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.3.Final, 2.1.0.Alpha2
>            Reporter: Juergen Zimmermann
>            Assignee: Luk?? Fry?
>             Fix For: 2.0.4.Final, 2.1-Tracking
>
>
> I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final.
> The stacktrace:
> {code}
> org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException:
> Error while initializing: class de.shop.util.IndexPage
>         at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78)
>         at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125)
>         at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120)
>         at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291)
>         at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:483)
>         at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>         at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>         at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
>         at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>         at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267)
>         at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>         at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>         at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>         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:309)
>         at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
>         at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>         at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>         at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> Caused by: java.lang.NullPointerException
>         at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68)
>         at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73)
>         at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97)
>         at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76)
>         ... 34 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Fri Feb 12 10:21:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 12 Feb 2016 10:21:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-474) Remove
 arquillian-graphene depchain as no one uses it
In-Reply-To: <JIRA.12578263.1437044926000@Atlassian.JIRA>
References: <JIRA.12578263.1437044926000@Atlassian.JIRA>
	<JIRA.12578263.1437044926000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12578263.1437044926000.87597.1455290460124@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-474:
---------------------------------------

PR: https://github.com/arquillian/arquillian-graphene/pull/150

> Remove arquillian-graphene depchain as no one uses it
> -----------------------------------------------------
>
>                 Key: ARQGRA-474
>                 URL: https://issues.jboss.org/browse/ARQGRA-474
>             Project: Arquillian Graphene
>          Issue Type: Task
>            Reporter: Luk?? Fry?
>             Fix For: 2.1-Tracking
>
>
> Docs and tutorials mention graphene-webdriver depchain:
> https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options
> http://arquillian.org/guides/functional_testing_using_graphene/
> The depchains are not used by EAP BOMs too:
> https://issues.jboss.org/browse/JDF-840



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Fri Feb 12 10:58:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Fri, 12 Feb 2016 10:58:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-472) TestCases are
	copy-pasted
In-Reply-To: <JIRA.12576369.1435309046000@Atlassian.JIRA>
References: <JIRA.12576369.1435309046000@Atlassian.JIRA>
	<JIRA.12576369.1435309046000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12576369.1435309046000.87858.1455292680299@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-472:
---------------------------------------

PR: https://github.com/arquillian/arquillian-graphene/pull/151

> TestCases are copy-pasted
> -------------------------
>
>                 Key: ARQGRA-472
>                 URL: https://issues.jboss.org/browse/ARQGRA-472
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: unit-test
>    Affects Versions: 2.1-Tracking
>            Reporter: Vitalii Grygoryuk
>             Fix For: 2.1-Tracking
>
>
> TestHandlingOfStaleElements.testDeletion() and TestHandlingOfStaleElements.testReplacement() are both testing deletion, so there is no test case for node replacement logic:
> {code}
>     @Test
>     public void testDeletion() {
>         rootElement.isDisplayed();
>         executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement);
>         try {
>             rootElement.isDisplayed();
>             fail("rootElement should not be found");
>         } catch (NoSuchElementException e) {
>         }
>     }
>     @Test
>     public void testReplacement() {
>         rootElement.isDisplayed();
>         executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement);
>         try {
>             rootElement.isDisplayed();
>             fail("rootElement should not be found");
>         } catch (NoSuchElementException e) {
>         }
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 02:59:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 15 Feb 2016 02:59:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-458) Graphene can't be
	compiled in Maven 3.1.1
In-Reply-To: <JIRA.12549456.1408124844000@Atlassian.JIRA>
References: <JIRA.12549456.1408124844000@Atlassian.JIRA>
	<JIRA.12549456.1408124844000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12549456.1408124844000.970.1455523140232@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-458:
---------------------------------------

Are you able to provide some more information about the problem you faced when building with this version of maven?
I tried it locally and it passed. It passed on the travis too: 
https://travis-ci.org/MatousJobanek/arquillian-graphene/builds/109287060
the command with specified maven version: https://travis-ci.org/MatousJobanek/arquillian-graphene/builds/109287060#L3829
branch that was build: https://github.com/matousjobanek/arquillian-graphene/tree/maven-3.1.1
there in the .travis.yml file you can see the configuration that should force using maven 3.1.1:
https://github.com/MatousJobanek/arquillian-graphene/blob/maven-3.1.1/.travis.yml

> Graphene can't be compiled in Maven 3.1.1
> -----------------------------------------
>
>                 Key: ARQGRA-458
>                 URL: https://issues.jboss.org/browse/ARQGRA-458
>             Project: Arquillian Graphene
>          Issue Type: Bug
>            Reporter: Luk?? Fry?
>             Fix For: 2.1-Tracking
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Mon Feb 15 03:13:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 15 Feb 2016 03:13:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-477) Upgrade to Core 1.1.8,
 Drone 2.0.0.Alpha5, Selenium 2.47.1
In-Reply-To: <JIRA.12585587.1442867329000@Atlassian.JIRA>
References: <JIRA.12585587.1442867329000@Atlassian.JIRA>
	<JIRA.12585587.1442867329000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12585587.1442867329000.1022.1455523980394@Atlassian.JIRA>


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

Work on ARQGRA-477 started by Matous Jobanek.
---------------------------------------------
> Upgrade to Core 1.1.8,  Drone 2.0.0.Alpha5, Selenium 2.47.1
> -----------------------------------------------------------
>
>                 Key: ARQGRA-477
>                 URL: https://issues.jboss.org/browse/ARQGRA-477
>             Project: Arquillian Graphene
>          Issue Type: Component  Upgrade
>            Reporter: Luk?? Fry?
>            Assignee: Matous Jobanek
>             Fix For: 2.1-Tracking
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Mon Feb 15 03:13:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 15 Feb 2016 03:13:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-472) TestCases are
	copy-pasted
In-Reply-To: <JIRA.12576369.1435309046000@Atlassian.JIRA>
References: <JIRA.12576369.1435309046000@Atlassian.JIRA>
	<JIRA.12576369.1435309046000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12576369.1435309046000.1025.1455523980495@Atlassian.JIRA>


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

Work on ARQGRA-472 started by Matous Jobanek.
---------------------------------------------
> TestCases are copy-pasted
> -------------------------
>
>                 Key: ARQGRA-472
>                 URL: https://issues.jboss.org/browse/ARQGRA-472
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: unit-test
>    Affects Versions: 2.1-Tracking
>            Reporter: Vitalii Grygoryuk
>            Assignee: Matous Jobanek
>             Fix For: 2.1-Tracking
>
>
> TestHandlingOfStaleElements.testDeletion() and TestHandlingOfStaleElements.testReplacement() are both testing deletion, so there is no test case for node replacement logic:
> {code}
>     @Test
>     public void testDeletion() {
>         rootElement.isDisplayed();
>         executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement);
>         try {
>             rootElement.isDisplayed();
>             fail("rootElement should not be found");
>         } catch (NoSuchElementException e) {
>         }
>     }
>     @Test
>     public void testReplacement() {
>         rootElement.isDisplayed();
>         executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement);
>         try {
>             rootElement.isDisplayed();
>             fail("rootElement should not be found");
>         } catch (NoSuchElementException e) {
>         }
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 03:13:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 15 Feb 2016 03:13:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-472) TestCases are
	copy-pasted
In-Reply-To: <JIRA.12576369.1435309046000@Atlassian.JIRA>
References: <JIRA.12576369.1435309046000@Atlassian.JIRA>
	<JIRA.12576369.1435309046000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12576369.1435309046000.1030.1455523980780@Atlassian.JIRA>


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

Work on ARQGRA-472 stopped by Matous Jobanek.
---------------------------------------------
> TestCases are copy-pasted
> -------------------------
>
>                 Key: ARQGRA-472
>                 URL: https://issues.jboss.org/browse/ARQGRA-472
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: unit-test
>    Affects Versions: 2.1-Tracking
>            Reporter: Vitalii Grygoryuk
>            Assignee: Matous Jobanek
>             Fix For: 2.1-Tracking
>
>
> TestHandlingOfStaleElements.testDeletion() and TestHandlingOfStaleElements.testReplacement() are both testing deletion, so there is no test case for node replacement logic:
> {code}
>     @Test
>     public void testDeletion() {
>         rootElement.isDisplayed();
>         executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement);
>         try {
>             rootElement.isDisplayed();
>             fail("rootElement should not be found");
>         } catch (NoSuchElementException e) {
>         }
>     }
>     @Test
>     public void testReplacement() {
>         rootElement.isDisplayed();
>         executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement);
>         try {
>             rootElement.isDisplayed();
>             fail("rootElement should not be found");
>         } catch (NoSuchElementException e) {
>         }
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 03:14:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Mon, 15 Feb 2016 03:14:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-477) Upgrade to Core 1.1.8,
 Drone 2.0.0.Alpha5, Selenium 2.47.1
In-Reply-To: <JIRA.12585587.1442867329000@Atlassian.JIRA>
References: <JIRA.12585587.1442867329000@Atlassian.JIRA>
	<JIRA.12585587.1442867329000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12585587.1442867329000.1034.1455524040336@Atlassian.JIRA>


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

Work on ARQGRA-477 stopped by Matous Jobanek.
---------------------------------------------
> Upgrade to Core 1.1.8,  Drone 2.0.0.Alpha5, Selenium 2.47.1
> -----------------------------------------------------------
>
>                 Key: ARQGRA-477
>                 URL: https://issues.jboss.org/browse/ARQGRA-477
>             Project: Arquillian Graphene
>          Issue Type: Component  Upgrade
>            Reporter: Luk?? Fry?
>            Assignee: Matous Jobanek
>             Fix For: 2.1-Tracking
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Mon Feb 15 05:08:00 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Mon, 15 Feb 2016 05:08:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2011) Upgrade to ShrinkWrap
	Resolvers 2.2.2
In-Reply-To: <JIRA.12603839.1455530854000@Atlassian.JIRA>
References: <JIRA.12603839.1455530854000@Atlassian.JIRA>
	<JIRA.12603839.1455530854554@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12603839.1455530854000.1761.1455530880456@Atlassian.JIRA>

Aslak Knutsen created ARQ-2011:
----------------------------------

             Summary: Upgrade to ShrinkWrap Resolvers 2.2.2
                 Key: ARQ-2011
                 URL: https://issues.jboss.org/browse/ARQ-2011
             Project: Arquillian
          Issue Type: Component  Upgrade
          Components: Base Implementation
    Affects Versions: 1.1.11.Final
            Reporter: Aslak Knutsen






--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 05:13:01 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Mon, 15 Feb 2016 05:13:01 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue
	with injected deployer
In-Reply-To: <JIRA.12566592.1427106139000@Atlassian.JIRA>
References: <JIRA.12566592.1427106139000@Atlassian.JIRA>
	<JIRA.12566592.1427106139000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12566592.1427106139000.1856.1455531181681@Atlassian.JIRA>


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

Aslak Knutsen commented on ARQ-1937:
------------------------------------

Good catch! :)

> Class loading issue with injected deployer 
> -------------------------------------------
>
>                 Key: ARQ-1937
>                 URL: https://issues.jboss.org/browse/ARQ-1937
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.11.Final
>
>
> Steps to reproduce:
> 1) inject a Deployer via @ArquillianResource
> 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container
> 3) run a test method that operates on the deployment
> 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader())
> 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader
> In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in <dependencies> while the older version is downloaded separately via Maven dependency plugin.
> {code}
> package com.jboss.datagrid.test.backwardcompatibility;
> @RunWith(Arquillian.class)
> public class SingleFileStoreBackwardCompatibilityIT {
>     private DefaultCacheManager dfc;
>     private String cacheName = "testCache";
>     private static final String OLD_ISPN = "dep1_with_old_ispn";
>     private static final String NEW_ISPN = "dep2_with_new_ispn";
>     private static Map<String, String> storedMap;
>     @ArquillianResource
>     Deployer deployer;
>     @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1)
>     @TargetsContainer("container1")
>     public static WebArchive createDeploymentOld() {
>         WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous");
>         System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader());
>         return jar;
>     }
>     @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2)
>     @TargetsContainer("container2")
>     public static WebArchive createDeploymentNew() {
>         WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current");
>         return jar;
>     }
>     private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception {
>         GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault()
>                 .globalJmxStatistics().allowDuplicateDomains(true).
>                         build();
>         ConfigurationBuilder c = new ConfigurationBuilder();
>         c.clustering().cacheMode(CacheMode.LOCAL);
>         File tmpStore = new File("/tmp/cache/" + cacheName + ".dat");
>         if (clearCacheStore && tmpStore.exists()) {
>             tmpStore.delete();
>         }
>         c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/");
>         Configuration cnf = c.build();
>         DefaultCacheManager manager = new DefaultCacheManager(glob);
>         manager.defineConfiguration(cacheName, cnf);
>         return manager;
>     }
>     @Test
>     @OperateOnDeployment(OLD_ISPN)
>     @InSequence(1)
>     public void testStoreWithOldJDG() throws Exception {
>         deployer.deploy(OLD_ISPN);
>         dfc = configureCacheManager(true);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("Version: " + cache.getVersion());
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         storedMap = new HashMap<String, String>();
>         storedMap.put("k", "v");
>         cache.put("mapKey", storedMap);
>         dfc.stop();
>         deployer.undeploy(OLD_ISPN);
>     }
>     @Test
>     @OperateOnDeployment(NEW_ISPN)
>     @InSequence(2)
>     public void testReadWithNewJDG() throws Exception {
>         deployer.deploy(NEW_ISPN);
>         dfc = configureCacheManager(false);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         System.out.println("Version: " + cache.getVersion());
>         assertEquals(storedMap, cache.get("mapKey"));
>         dfc.stop();
>         deployer.undeploy(NEW_ISPN);
>     }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 05:14:00 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Mon, 15 Feb 2016 05:14:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2011) Upgrade to ShrinkWrap
	Resolvers 2.2.2
In-Reply-To: <JIRA.12603839.1455530855000@Atlassian.JIRA>
References: <JIRA.12603839.1455530855000@Atlassian.JIRA>
	<JIRA.12603839.1455530855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12603839.1455530855000.1857.1455531240100@Atlassian.JIRA>


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

Aslak Knutsen updated ARQ-2011:
-------------------------------
    Fix Version/s: 1.2.0.Alpha1


> Upgrade to ShrinkWrap Resolvers 2.2.2
> -------------------------------------
>
>                 Key: ARQ-2011
>                 URL: https://issues.jboss.org/browse/ARQ-2011
>             Project: Arquillian
>          Issue Type: Component  Upgrade
>          Components: Base Implementation
>    Affects Versions: 1.1.11.Final
>            Reporter: Aslak Knutsen
>             Fix For: 1.2.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 05:19:00 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Mon, 15 Feb 2016 05:19:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2011) Upgrade to ShrinkWrap
	Resolvers 2.2.2
In-Reply-To: <JIRA.12603839.1455530855000@Atlassian.JIRA>
References: <JIRA.12603839.1455530855000@Atlassian.JIRA>
	<JIRA.12603839.1455530855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12603839.1455530855000.1924.1455531540271@Atlassian.JIRA>


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

Aslak Knutsen updated ARQ-2011:
-------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-core/pull/98


> Upgrade to ShrinkWrap Resolvers 2.2.2
> -------------------------------------
>
>                 Key: ARQ-2011
>                 URL: https://issues.jboss.org/browse/ARQ-2011
>             Project: Arquillian
>          Issue Type: Component  Upgrade
>          Components: Base Implementation
>    Affects Versions: 1.1.11.Final
>            Reporter: Aslak Knutsen
>             Fix For: 1.2.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 05:19:00 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Mon, 15 Feb 2016 05:19:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2011) Upgrade to ShrinkWrap
	Resolvers 2.2.2
In-Reply-To: <JIRA.12603839.1455530855000@Atlassian.JIRA>
References: <JIRA.12603839.1455530855000@Atlassian.JIRA>
	<JIRA.12603839.1455530855000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12603839.1455530855000.1928.1455531540391@Atlassian.JIRA>


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

Aslak Knutsen updated ARQ-2011:
-------------------------------
        Status: Resolved  (was: Pull Request Sent)
      Assignee: Aslak Knutsen
    Resolution: Done


pushed upstream https://github.com/arquillian/arquillian-core/commit/c2ae438796b4bab56a86c6246982ecfe038f4a78

> Upgrade to ShrinkWrap Resolvers 2.2.2
> -------------------------------------
>
>                 Key: ARQ-2011
>                 URL: https://issues.jboss.org/browse/ARQ-2011
>             Project: Arquillian
>          Issue Type: Component  Upgrade
>          Components: Base Implementation
>    Affects Versions: 1.1.11.Final
>            Reporter: Aslak Knutsen
>            Assignee: Aslak Knutsen
>             Fix For: 1.2.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 07:35:00 2016
From: issues at jboss.org (Ladislav Thon (JIRA))
Date: Mon, 15 Feb 2016 07:35:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue
	with injected deployer
In-Reply-To: <JIRA.12566592.1427106139000@Atlassian.JIRA>
References: <JIRA.12566592.1427106139000@Atlassian.JIRA>
	<JIRA.12566592.1427106139000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12566592.1427106139000.2745.1455539700207@Atlassian.JIRA>


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

Ladislav Thon commented on ARQ-1937:
------------------------------------

Do you want me to file a new JIRA for this?

> Class loading issue with injected deployer 
> -------------------------------------------
>
>                 Key: ARQ-1937
>                 URL: https://issues.jboss.org/browse/ARQ-1937
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.11.Final
>
>
> Steps to reproduce:
> 1) inject a Deployer via @ArquillianResource
> 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container
> 3) run a test method that operates on the deployment
> 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader())
> 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader
> In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in <dependencies> while the older version is downloaded separately via Maven dependency plugin.
> {code}
> package com.jboss.datagrid.test.backwardcompatibility;
> @RunWith(Arquillian.class)
> public class SingleFileStoreBackwardCompatibilityIT {
>     private DefaultCacheManager dfc;
>     private String cacheName = "testCache";
>     private static final String OLD_ISPN = "dep1_with_old_ispn";
>     private static final String NEW_ISPN = "dep2_with_new_ispn";
>     private static Map<String, String> storedMap;
>     @ArquillianResource
>     Deployer deployer;
>     @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1)
>     @TargetsContainer("container1")
>     public static WebArchive createDeploymentOld() {
>         WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous");
>         System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader());
>         return jar;
>     }
>     @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2)
>     @TargetsContainer("container2")
>     public static WebArchive createDeploymentNew() {
>         WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current");
>         return jar;
>     }
>     private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception {
>         GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault()
>                 .globalJmxStatistics().allowDuplicateDomains(true).
>                         build();
>         ConfigurationBuilder c = new ConfigurationBuilder();
>         c.clustering().cacheMode(CacheMode.LOCAL);
>         File tmpStore = new File("/tmp/cache/" + cacheName + ".dat");
>         if (clearCacheStore && tmpStore.exists()) {
>             tmpStore.delete();
>         }
>         c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/");
>         Configuration cnf = c.build();
>         DefaultCacheManager manager = new DefaultCacheManager(glob);
>         manager.defineConfiguration(cacheName, cnf);
>         return manager;
>     }
>     @Test
>     @OperateOnDeployment(OLD_ISPN)
>     @InSequence(1)
>     public void testStoreWithOldJDG() throws Exception {
>         deployer.deploy(OLD_ISPN);
>         dfc = configureCacheManager(true);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("Version: " + cache.getVersion());
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         storedMap = new HashMap<String, String>();
>         storedMap.put("k", "v");
>         cache.put("mapKey", storedMap);
>         dfc.stop();
>         deployer.undeploy(OLD_ISPN);
>     }
>     @Test
>     @OperateOnDeployment(NEW_ISPN)
>     @InSequence(2)
>     public void testReadWithNewJDG() throws Exception {
>         deployer.deploy(NEW_ISPN);
>         dfc = configureCacheManager(false);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         System.out.println("Version: " + cache.getVersion());
>         assertEquals(storedMap, cache.get("mapKey"));
>         dfc.stop();
>         deployer.undeploy(NEW_ISPN);
>     }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 09:07:00 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Mon, 15 Feb 2016 09:07:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue
	with injected deployer
In-Reply-To: <JIRA.12566592.1427106139000@Atlassian.JIRA>
References: <JIRA.12566592.1427106139000@Atlassian.JIRA>
	<JIRA.12566592.1427106139000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12566592.1427106139000.3489.1455545220175@Atlassian.JIRA>


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

Aslak Knutsen commented on ARQ-1937:
------------------------------------

[~lthon] Yes, please do.

> Class loading issue with injected deployer 
> -------------------------------------------
>
>                 Key: ARQ-1937
>                 URL: https://issues.jboss.org/browse/ARQ-1937
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.11.Final
>
>
> Steps to reproduce:
> 1) inject a Deployer via @ArquillianResource
> 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container
> 3) run a test method that operates on the deployment
> 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader())
> 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader
> In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in <dependencies> while the older version is downloaded separately via Maven dependency plugin.
> {code}
> package com.jboss.datagrid.test.backwardcompatibility;
> @RunWith(Arquillian.class)
> public class SingleFileStoreBackwardCompatibilityIT {
>     private DefaultCacheManager dfc;
>     private String cacheName = "testCache";
>     private static final String OLD_ISPN = "dep1_with_old_ispn";
>     private static final String NEW_ISPN = "dep2_with_new_ispn";
>     private static Map<String, String> storedMap;
>     @ArquillianResource
>     Deployer deployer;
>     @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1)
>     @TargetsContainer("container1")
>     public static WebArchive createDeploymentOld() {
>         WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous");
>         System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader());
>         return jar;
>     }
>     @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2)
>     @TargetsContainer("container2")
>     public static WebArchive createDeploymentNew() {
>         WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current");
>         return jar;
>     }
>     private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception {
>         GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault()
>                 .globalJmxStatistics().allowDuplicateDomains(true).
>                         build();
>         ConfigurationBuilder c = new ConfigurationBuilder();
>         c.clustering().cacheMode(CacheMode.LOCAL);
>         File tmpStore = new File("/tmp/cache/" + cacheName + ".dat");
>         if (clearCacheStore && tmpStore.exists()) {
>             tmpStore.delete();
>         }
>         c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/");
>         Configuration cnf = c.build();
>         DefaultCacheManager manager = new DefaultCacheManager(glob);
>         manager.defineConfiguration(cacheName, cnf);
>         return manager;
>     }
>     @Test
>     @OperateOnDeployment(OLD_ISPN)
>     @InSequence(1)
>     public void testStoreWithOldJDG() throws Exception {
>         deployer.deploy(OLD_ISPN);
>         dfc = configureCacheManager(true);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("Version: " + cache.getVersion());
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         storedMap = new HashMap<String, String>();
>         storedMap.put("k", "v");
>         cache.put("mapKey", storedMap);
>         dfc.stop();
>         deployer.undeploy(OLD_ISPN);
>     }
>     @Test
>     @OperateOnDeployment(NEW_ISPN)
>     @InSequence(2)
>     public void testReadWithNewJDG() throws Exception {
>         deployer.deploy(NEW_ISPN);
>         dfc = configureCacheManager(false);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         System.out.println("Version: " + cache.getVersion());
>         assertEquals(storedMap, cache.get("mapKey"));
>         dfc.stop();
>         deployer.undeploy(NEW_ISPN);
>     }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 09:17:00 2016
From: issues at jboss.org (Ladislav Thon (JIRA))
Date: Mon, 15 Feb 2016 09:17:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2012) Warnings when test runs
 as client without @RunAsClient
In-Reply-To: <JIRA.12603912.1455545786000@Atlassian.JIRA>
References: <JIRA.12603912.1455545786000@Atlassian.JIRA>
	<JIRA.12603912.1455545786344@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12603912.1455545786000.3664.1455545820850@Atlassian.JIRA>

Ladislav Thon created ARQ-2012:
----------------------------------

             Summary: Warnings when test runs as client without @RunAsClient
                 Key: ARQ-2012
                 URL: https://issues.jboss.org/browse/ARQ-2012
             Project: Arquillian
          Issue Type: Bug
          Components: Deployable Containers SPI
    Affects Versions: 1.1.11.Final
            Reporter: Ladislav Thon


When I moved to Arquillian 1.1.11.Final, I started getting warnings when my tests run as client but don't use the {{@RunAsClient}} annotation. The cause is ARQ-1937.

I'll just reiterate that I actually never ever use the {{@RunAsClient}} annotation because it's superfluous. I simply set my {{@Deployment}} to {{testable = false}} or I have no {{@Deployment}} at all. I do that intentionally and I _expect_ that the test will run as client, so the warning doesn't make much sense for me.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Feb 15 09:18:00 2016
From: issues at jboss.org (Ladislav Thon (JIRA))
Date: Mon, 15 Feb 2016 09:18:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1937) Class loading issue
	with injected deployer
In-Reply-To: <JIRA.12566592.1427106139000@Atlassian.JIRA>
References: <JIRA.12566592.1427106139000@Atlassian.JIRA>
	<JIRA.12566592.1427106139000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12566592.1427106139000.3676.1455545880367@Atlassian.JIRA>


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

Ladislav Thon commented on ARQ-1937:
------------------------------------

Thanks, filed ARQ-2012

> Class loading issue with injected deployer 
> -------------------------------------------
>
>                 Key: ARQ-1937
>                 URL: https://issues.jboss.org/browse/ARQ-1937
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.1.Final
>            Reporter: Martin Gencur
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.11.Final
>
>
> Steps to reproduce:
> 1) inject a Deployer via @ArquillianResource
> 2) declare a deployment as managed=false, use the deployer to deploy artifacts to a managed container
> 3) run a test method that operates on the deployment
> 4) check that classes inside the test method have the same classloader as the test class itself (see the code below where I call cache.getClass().getClassLoader())
> 5) this does not happen when the deployment is managed=true and deployer API is NOT used. In this case, the classes have a different class loader
> In the test below, I tried to load different versions of Infinispan in two deployments and test backward compatibility. However, due to this class loading issue the Infinispan classes are of the latest version regardless of libraries bundled in the WAR. This is probably due to the fact that the Maven test module has the latest Infinispan libraries defined in <dependencies> while the older version is downloaded separately via Maven dependency plugin.
> {code}
> package com.jboss.datagrid.test.backwardcompatibility;
> @RunWith(Arquillian.class)
> public class SingleFileStoreBackwardCompatibilityIT {
>     private DefaultCacheManager dfc;
>     private String cacheName = "testCache";
>     private static final String OLD_ISPN = "dep1_with_old_ispn";
>     private static final String NEW_ISPN = "dep2_with_new_ispn";
>     private static Map<String, String> storedMap;
>     @ArquillianResource
>     Deployer deployer;
>     @Deployment(name = OLD_ISPN, testable = true, managed = true, order=1)
>     @TargetsContainer("container1")
>     public static WebArchive createDeploymentOld() {
>         WebArchive jar = DeploymentBuilder.createTestArchiveWithPreviousJDG("test1.war", "previous");
>         System.out.println("ClassLoader: " + SingleFileStoreBackwardCompatibilityIT.class.getClassLoader());
>         return jar;
>     }
>     @Deployment(name = NEW_ISPN, testable = true, managed = true, order=2)
>     @TargetsContainer("container2")
>     public static WebArchive createDeploymentNew() {
>         WebArchive jar = DeploymentBuilder.createTestArchive("test2.war", "current");
>         return jar;
>     }
>     private DefaultCacheManager configureCacheManager(boolean clearCacheStore) throws Exception {
>         GlobalConfiguration glob = new GlobalConfigurationBuilder().nonClusteredDefault()
>                 .globalJmxStatistics().allowDuplicateDomains(true).
>                         build();
>         ConfigurationBuilder c = new ConfigurationBuilder();
>         c.clustering().cacheMode(CacheMode.LOCAL);
>         File tmpStore = new File("/tmp/cache/" + cacheName + ".dat");
>         if (clearCacheStore && tmpStore.exists()) {
>             tmpStore.delete();
>         }
>         c.persistence().passivation(false).addSingleFileStore().purgeOnStartup(false).location("/tmp/cache/");
>         Configuration cnf = c.build();
>         DefaultCacheManager manager = new DefaultCacheManager(glob);
>         manager.defineConfiguration(cacheName, cnf);
>         return manager;
>     }
>     @Test
>     @OperateOnDeployment(OLD_ISPN)
>     @InSequence(1)
>     public void testStoreWithOldJDG() throws Exception {
>         deployer.deploy(OLD_ISPN);
>         dfc = configureCacheManager(true);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("Version: " + cache.getVersion());
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         storedMap = new HashMap<String, String>();
>         storedMap.put("k", "v");
>         cache.put("mapKey", storedMap);
>         dfc.stop();
>         deployer.undeploy(OLD_ISPN);
>     }
>     @Test
>     @OperateOnDeployment(NEW_ISPN)
>     @InSequence(2)
>     public void testReadWithNewJDG() throws Exception {
>         deployer.deploy(NEW_ISPN);
>         dfc = configureCacheManager(false);
>         dfc.start();
>         Cache<Object, Object> cache = dfc.getCache(cacheName);
>         System.out.println("ClassLoader: " + cache.getClass().getClassLoader());
>         System.out.println("Version: " + cache.getVersion());
>         assertEquals(storedMap, cache.get("mapKey"));
>         dfc.stop();
>         deployer.undeploy(NEW_ISPN);
>     }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb 17 09:40:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 17 Feb 2016 09:40:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-464) @Page injection
 should support parameter injection
In-Reply-To: <JIRA.12560817.1421146844000@Atlassian.JIRA>
References: <JIRA.12560817.1421146844000@Atlassian.JIRA>
	<JIRA.12560817.1421146844000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12560817.1421146844000.2637.1455720000420@Atlassian.JIRA>


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

Matous Jobanek commented on ARQGRA-464:
---------------------------------------

PR: https://github.com/arquillian/arquillian-graphene/pull/152

> @Page injection should support parameter injection
> --------------------------------------------------
>
>                 Key: ARQGRA-464
>                 URL: https://issues.jboss.org/browse/ARQGRA-464
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>          Components: core
>    Affects Versions: 2.1.0.Alpha1
>            Reporter: Karel Piwko
>             Fix For: 2.1-Tracking
>
>
> Graphene should support @Page injection even for parameter injection in test methods. This would make test case much more compact.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb 24 03:43:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 24 Feb 2016 03:43:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2013) Update Arquillian, Drone,
 Resolver, JaCoCo and JUnit to newer version
In-Reply-To: <JIRA.12607487.1456303320000@Atlassian.JIRA>
References: <JIRA.12607487.1456303320000@Atlassian.JIRA>
	<JIRA.12607487.1456303320502@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12607487.1456303320000.32164.1456303380243@Atlassian.JIRA>

Matous Jobanek created ARQ-2013:
-----------------------------------

             Summary: Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version
                 Key: ARQ-2013
                 URL: https://issues.jboss.org/browse/ARQ-2013
             Project: Arquillian
          Issue Type: Component  Upgrade
          Components: Extension - Warp
    Affects Versions: warp_1.0.0.Alpha7
            Reporter: Matous Jobanek


Please update to newer versions to use the latest and greatest implementations.
In case of JaCoCo - the current version {{0.6.0.201210061924}} is not compatible with JDK8



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb 24 03:49:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 24 Feb 2016 03:49:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2013) Update Arquillian, Drone,
 Resolver, JaCoCo and JUnit to newer version
In-Reply-To: <JIRA.12607487.1456303321000@Atlassian.JIRA>
References: <JIRA.12607487.1456303321000@Atlassian.JIRA>
	<JIRA.12607487.1456303321000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12607487.1456303321000.32188.1456303740211@Atlassian.JIRA>


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

Matous Jobanek updated ARQ-2013:
--------------------------------
    Git Pull Request: https://github.com/arquillian/arquillian-extension-warp/pull/32


> Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version
> ---------------------------------------------------------------------
>
>                 Key: ARQ-2013
>                 URL: https://issues.jboss.org/browse/ARQ-2013
>             Project: Arquillian
>          Issue Type: Component  Upgrade
>          Components: Extension - Warp
>    Affects Versions: warp_1.0.0.Alpha7
>            Reporter: Matous Jobanek
>
> Please update to newer versions to use the latest and greatest implementations.
> In case of JaCoCo - the current version {{0.6.0.201210061924}} is not compatible with JDK8



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Feb 24 03:50:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 24 Feb 2016 03:50:00 -0500 (EST)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2013) Update Arquillian, Drone,
 Resolver, JaCoCo and JUnit to newer version
In-Reply-To: <JIRA.12607487.1456303321000@Atlassian.JIRA>
References: <JIRA.12607487.1456303321000@Atlassian.JIRA>
	<JIRA.12607487.1456303321000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12607487.1456303321000.32195.1456303800719@Atlassian.JIRA>


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

Matous Jobanek reassigned ARQ-2013:
-----------------------------------

    Assignee: Matous Jobanek


> Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version
> ---------------------------------------------------------------------
>
>                 Key: ARQ-2013
>                 URL: https://issues.jboss.org/browse/ARQ-2013
>             Project: Arquillian
>          Issue Type: Component  Upgrade
>          Components: Extension - Warp
>    Affects Versions: warp_1.0.0.Alpha7
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>
> Please update to newer versions to use the latest and greatest implementations.
> In case of JaCoCo - the current version {{0.6.0.201210061924}} is not compatible with JDK8



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sat Feb 27 03:55:00 2016
From: issues at jboss.org (Christian Schlichtherle (JIRA))
Date: Sat, 27 Feb 2016 03:55:00 -0500 (EST)
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.49095.1456563300390@Atlassian.JIRA>


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

Christian Schlichtherle commented on ARQ-1987:
----------------------------------------------

Does anybody care?

> 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
(v6.4.11#64026)


From issues at jboss.org  Sat Feb 27 03:55:00 2016
From: issues at jboss.org (Christian Schlichtherle (JIRA))
Date: Sat, 27 Feb 2016 03:55:00 -0500 (EST)
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.49097.1456563300484@Atlassian.JIRA>


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

Christian Schlichtherle edited comment on ARQ-1987 at 2/27/16 3:54 AM:
-----------------------------------------------------------------------

Does anybody care? It's truly a blocker for me.


was (Author: christians):
Does anybody care?

> 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
(v6.4.11#64026)