From issues at jboss.org Tue Oct 4 10:07:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 4 Oct 2016 10:07:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13302346#comment-13302346 ] Matous Jobanek commented on ARQ-2034: ------------------------------------- Hi, yeah, there is a way to do it - crating a new event. Here is my proposal: https://github.com/MatousJobanek/arquillian-core/tree/ARQ-2034_new_event > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Bj?rn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 5 11:24:01 2016 From: issues at jboss.org (=?UTF-8?Q?Bj=C3=B6rn_Kautler_=28JIRA=29?=) Date: Wed, 5 Oct 2016 11:24:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13299252#comment-13299252 ] Bj?rn Kautler edited comment on ARQ-2034 at 10/5/16 11:23 AM: -------------------------------------------------------------- [~mjobanek] Are you sure? As far as I remember what I have looked at in Arquillian code you copied some code from the {{BlockJUnit4ClassRunner}}, having own instances of {{withBefore}}, {{withAfter}} and so on, but calling the {{BlockJUnit4ClassRunner}} s {{withRules}} method via reflection. In the {{withRules}} you should also have a test available already I think, as that probably is the code that sets the instance fields that are annotated with {{@Rule}} to the actual rule instances. So I guess you have to change that you not hook into {{withBefore}} but already into {{withRules}} to do the enriching before the rules. was (Author: vampire): [~mjobanek] Are you sure? As far as I remember what I have looked at in Arquillian code you copied some code from the {{BlockJUnit4ClassRunner}}, having own instances of {{withBefore}}, {{withAfter}} and so on, but calling the {{BlockJUnit4ClassRunner}}s {{withRules}} method via reflection. In the {{withRules}} you should also have a test available already I think, as that probably is the code that sets the instance fields that are annotated with {{@Rule}} to the actual rule instances. So I guess you have to change that you not hook into {{withBefore}} but already into {{withRules}} to do the enriching before the rules. > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Bj?rn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 5 11:33:00 2016 From: issues at jboss.org (=?UTF-8?Q?Bj=C3=B6rn_Kautler_=28JIRA=29?=) Date: Wed, 5 Oct 2016 11:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13303064#comment-13303064 ] Bj?rn Kautler commented on ARQ-2034: ------------------------------------ This would solve the second point, or is an alternate solution for the first point? As the branch you point to seems to case about Rules enrichment, I guess it cares about the first point (enriching rules in the container). My question was about the second point (enriching the test method before the rules methods are evaluated), so that you can use fields that get enriched by Arquillian in rule-producing methods to forward injected stuff to rules you don't have under your control and thus cannot be made to receive the inject directly. > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Bj?rn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 6 08:40:00 2016 From: issues at jboss.org (vinoth selvaraj (JIRA)) Date: Thu, 6 Oct 2016 08:40:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-492) Integrate RushEye with Graphene for automated visual validation In-Reply-To: References: Message-ID: vinoth selvaraj created ARQGRA-492: -------------------------------------- Summary: Integrate RushEye with Graphene for automated visual validation Key: ARQGRA-492 URL: https://issues.jboss.org/browse/ARQGRA-492 Project: Arquillian Graphene Issue Type: Feature Request Reporter: vinoth selvaraj I have provided a sample use case of a Page Object. Graphene along with RushEye can compare the whole page or or just specific element (we can get the coordinates of an element - get the corresponding image from the whole image) {code:java} @RushEye(pattern="/resources/login.png") public class LoginPage{ @FindBy private WebElement username; @FindBy private WebElement password; @FindBy private WebElement someDynamicContentElement; @ArquillianResource private ImageComparator imageComparator; @RushEye(pattern="/resources/login/someElementWhichShouldMatchImge.png") @FindBy private WebElement someElementWhichShouldMatchImge; //takes the screenshot of the current page on the fly //compares with baseline & returns the status //it can even highlight the difference in case of mismatch public boolean isPageAsExpected(){ return imageComparator.compare(); } //we might want to exclude some elements //it might have dynamic content like current date/time etc public boolean isPageAsExpectedAfterExcludingElements(){ return imageComparator.mask(someDynamicContentElement) .mask(someOtherElement1) .mask(someOtherElement2) .compare(); } //in some case we might not want to do whole page compare //ex: it might have tons of adds //So we might want to just compare one or more elements - not whole page public boolean isSomeElementAsExpected(){ //take current coordinates of the element and get the image //compare with baseline return imageComparator.element(someElementWhichShouldMatchImge) //or list of elements .compare(); } } {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 6 09:37:00 2016 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Thu, 6 Oct 2016 09:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2030) Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13303475#comment-13303475 ] Thomas Diesler commented on ARQ-2030: ------------------------------------- Is this still relevant? > Upgrade Karaf to version 4.0.4 broke comparability with JBoss Fuse > ------------------------------------------------------------------ > > Key: ARQ-2030 > URL: https://issues.jboss.org/browse/ARQ-2030 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Tom?? Turek > Assignee: Thomas Diesler > Priority: Minor > > [Commit|https://github.com/arquillian/arquillian-container-osgi/commit/31157c2be1600929d47e79b7f4a15bc7b89f9bbd] which upgrade Karaf to version 4.0.4 for managed broke compatibility with JBoss Fuse 6.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 10 10:55:00 2016 From: issues at jboss.org (Razvan Petre (JIRA)) Date: Mon, 10 Oct 2016 10:55:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13304964#comment-13304964 ] Razvan Petre commented on ARQ-1952: ----------------------------------- hi all, Is Warp a dead project? I noticed that there a lot of issues that were raised a long time ago... My project relies heavily on Arquillian/Warp, what are my options? > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Fix For: warp_1.0.0.Beta1 > > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 11 06:06:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 11 Oct 2016 06:06:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2034) Test enrichment and JUnit @Rule do not harmonize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13305359#comment-13305359 ] Matous Jobanek commented on ARQ-2034: ------------------------------------- The branch should solve both of them. This commit: [5015698|https://github.com/MatousJobanek/arquillian-core/commit/5015698d191ce7dcc6f88e9c07366d500d94f04a] is completely same one as that one contained in the referenced [PR110|https://github.com/arquillian/arquillian-core/pull/110] - this solves the first point This commit [f3fe5a5|https://github.com/MatousJobanek/arquillian-core/commit/f3fe5a5658fce7692e901e1d463a35e75c8617d3] should solve the second point > Test enrichment and JUnit @Rule do not harmonize > ------------------------------------------------ > > Key: ARQ-2034 > URL: https://issues.jboss.org/browse/ARQ-2034 > Project: Arquillian > Issue Type: Bug > Components: Base Implementation > Affects Versions: 1.1.11.Final > Environment: junit 4.11 > arquillian-junit-container 1.1.11.Final > wildfly-arquillian-container-remote 8.1.0.Final > Reporter: Bj?rn Kautler > Assignee: Matous Jobanek > > We are starting with Arquillian tests on a remote WildFly instance. > I tried to write a JUnit {{@Rule}}, that can be used to make a login call for all test methods automatically, but I was not yet able to make it work, as I need an injected {{@Ejb}} instance for this. > I tried to add {{@EJB private InterfaceLoginManagement interfaceLoginManagement;}} to the {{TestRule}} implementation, but it stays {{null}}. I've read at ARQ-1954 that this should probably work, but unfortunately it is not, at least not with the remote container runner. {{org.jboss.arquillian.junit.extension.JUnitCoreExtension}} that should register {{org.jboss.arquillian.junit.extension.UpdateTestResultBeforeAfter}} and {{org.jboss.arquillian.junit.RulesEnricher}} is not even loaded on the container side. Maybe the {{META-INF/services/}} file is missing? > Then I tried to simply give the injected instance to the rule from the test class like > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule private LoginRule loginRule = new LoginRule(interfaceLoginManagement); > {code} > or even > {code} > @EJB private InterfaceLoginManagement interfaceLoginManagement; > @Rule public LoginRule getLoginRule() { > return new LoginRule(() -> { > return interfaceLoginManagement; > }); > } > {code} > with the {{LoginRule}} receiving a {{Supplier}} and call it as late as possible, i. e. in the rules {{apply()}} method. But even this is still too early as the EJB is still {{null}} and the test enrichers are only run between the {{@Rule}} applying and {{@Before}} methods. > So I'd like to suggest two things: > # Fix the implementation of ARQ-1954 if it should work on container side which I assume it should > # Make the test enrichments earlier in the lifecycle, i. e. before the {{@Rule}} s are being applied, or rather even before the {{@Rule}} methods are called, so that you at least can use the injected instances in the {{@Rule}} annotated methods to forward them to a rule. This is necessary even if top 1 is taken care of, because you might want to use a 3rd Party rule the code of which you cannot change. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 11 09:09:02 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 11 Oct 2016 09:09:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13305512#comment-13305512 ] Matous Jobanek commented on ARQ-1952: ------------------------------------- Hi, I don't want to say that it is a dead project, it just relies on a community effort. The problem is that we don't have enough time and resources as we would like to have to keep the development of the project alive and to fix all issues that has been raised. We would be delighted to have some more contributions there, so if you are interested feel free to send a PR or ask questions about implementation details. We would really appreciate any input from your or anyone else's side. If you just want to release a new version of Warp containing the latest fixes and improvements, then drop me an email or create an issue on github and I'll do it ASAP. Thanks > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Fix For: warp_1.0.0.Beta1 > > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 11 09:11:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Tue, 11 Oct 2016 09:11:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2048) excluded elements in beans.xml by the Weld Arquillian plugin is ALL check instead of ANY In-Reply-To: References: Message-ID: Antonin Stefanutti created ARQ-2048: --------------------------------------- Summary: excluded elements in beans.xml by the Weld Arquillian plugin is ALL check instead of ANY Key: ARQ-2048 URL: https://issues.jboss.org/browse/ARQ-2048 Project: Arquillian Issue Type: Bug Components: Weld Containers Affects Versions: 2.0.0.CR1 Reporter: Antonin Stefanutti Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 11 09:12:03 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Tue, 11 Oct 2016 09:12:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2048) excluded elements in beans.xml by the Weld Arquillian plugin is ALL check instead of ANY In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2048: ------------------------------------ Affects Version/s: weld_2.0.0.Beta3 (was: 2.0.0.CR1) > excluded elements in beans.xml by the Weld Arquillian plugin is ALL check instead of ANY > ---------------------------------------------------------------------------------------- > > Key: ARQ-2048 > URL: https://issues.jboss.org/browse/ARQ-2048 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > > Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 11 09:25:01 2016 From: issues at jboss.org (Razvan Petre (JIRA)) Date: Tue, 11 Oct 2016 09:25:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13305570#comment-13305570 ] Razvan Petre commented on ARQ-1952: ----------------------------------- hi [~mjobanek], Thank you for your reply. I am trying to migrate from glassfish 3, java 6 to glassfish 4, java 8 a quite large suite of arquillian /warp/ grapehene tests, I would say around 1200 tests in total. I am hitting this problem: https://developer.jboss.org/message/963976#963976 Warp helped me a lot in developing in a TDD style and I feel very confident that this is the way to go. (even though these tests are quite heavy sometimes, but you are sure it will work when deployed in the container). If you could release a new version with the latest changes it would be of great help. I have added below and example of one of my tests. {code:java} @RunAsClient @WarpTest @RunWith(Arquillian.class) public class ErrorInspectorPageManageErrorsTest extends SeleniumTestHelper { private static final String TAG_ERROR_FOR_TESTING = "comment on error"; private static final String ERROR_CODE_100 = "100"; private static final String ERROR_CODE_200 = "200"; private static final String ERROR_CODE_300 = "300"; private static final String ERROR_CODE_100_200 = "100,200"; private static final String ERROR_CODE_100_DESCRIPTION = "Error code 100 description"; private static final String ERROR_CODE_200_DESCRIPTION = "Error code 200 description"; private static final String ERROR_CODE_300_DESCRIPTION = "Error code 300 description"; @Deployment public static WebArchive createDeployment() { return Deployments.createFdsiDeployment(); } @Test public void canCloseErrors() { Warp.initiate(new Activity() { public void perform() { //@formatter:off final ErrorInspectorPage page = new ErrorInspectorPage(selenium).withPath(ErrorInspectorPage.PATH); page.loginAs(BusinessRoles.Role.INTERFACE_ADMIN, ADMIN_USERS).addTestDataFor(CAN_CLOSE_ERRORS); page.open(); assertThat(page.table().count().is(THREE_ERRORS), is(true)); assertThat(page.table.checkBoxes().size(), is(FOURTH)); assertThat(page.table.row(FIRST).cell(STATUS).text(), is(IS_OPEN)); assertThat(page.table.row(SECOND).cell(STATUS).text(), is(IS_OPEN)); assertThat(page.table.row(THIRD).cell(STATUS).text(), is(IS_OPEN)); assertThat(page.button(BULK_ACTION_BUTTON).getText(), is("Bulk Action on 3 errors")); assertThat(page.topActionButton().isDisabled(), is(true)); assertThat(page.topActionButton().getText(), is("Action on selected error(s)")); page.table.row(FIRST).selectionColumnCheckbox().click(); waitForTwoSeconds(); assertThat(page.topActionButton().isEnabled(), is(true)); assertThat(page.topActionButton().getText(), is("Action on 1 error(s)")); page.topActionButton().click(); page.waitUntilPresent(page.topCloseButton()); page.waitUntilVisible(page.topCloseButton()); waitFor(DEFAULT_TIMEOUT).until(new Predicate() { public boolean apply(WebDriver input) { page.button(CLOSE_BUTTON).click(); waitForTwoSeconds(); return page.overlayTextArea(CLOSE_OVERLAY_TEXTAREA).isDisplayed(); } }); assertThat(page.closeErrorscounter().getText(), is("255 characters remaining.")); page.overlayTextArea(CLOSE_OVERLAY_TEXTAREA).typeInto(CLOSING_THE_ERROR_FOR_TESTING); assertThat(page.overlayButton(OK_CLOSE_BUTTON).isPrimary(), is(true)); page.overlayButton(OK_CLOSE_BUTTON).click(); waitForTwoSeconds(); assertThat(page.topActionButton().isDisabled(), is(true)); page.waitUntilPresent(page.table()); assertThat(page.infoMessage(), is("Error(s) closed:You closed 1 error(s). 0 error(s) were skipped.")); assertThat(page.table().count().is(TWO_ERRORS), is(true)); assertThat(page.table.row(FIRST).cell(STATUS).text(), is(IS_OPEN)); assertThat(page.table.row(SECOND).cell(STATUS).text(), is(IS_OPEN)); assertThat(page.button(BULK_ACTION_BUTTON).getText(), is("Bulk Action on 2 errors")); OurPage userAuditPage = new OurPage(selenium).withPath(UserAuditPage.PATH); userAuditPage.open(); assertThat(userAuditPage.table().count().is(2), is(true)); assertThat(userAuditPage.table.row(1).cell(1).text(), is(FixtureBuilder.PRICING_PATTERN)); assertThat(userAuditPage.table.row(1).cell(2).text(), is(UserAction.UPDATE_ERROR.toCamelCase())); assertThat(userAuditPage.table.row(1).cell(3).text(), is("")); assertThat(userAuditPage.table.row(1).cell(4).text(), is("[1] errors were updated to [CLOSED]")); assertThat(userAuditPage.table.row(1).cell(5).text(), is(TEST_USER)); page.assertDatabaseState(AssertTestData.CAN_CLOSE_ERRORS); //@formatter:on } }).inspect(new Inspection() { private static final long serialVersionUID = 1L; }); } {code} > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Fix For: warp_1.0.0.Beta1 > > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 04:42:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 04:42:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2048) excluded elements in beans.xml by the Weld Arquillian plugin is a ALL check instead of ANY In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2048: ------------------------------------ Summary: excluded elements in beans.xml by the Weld Arquillian plugin is a ALL check instead of ANY (was: excluded elements in beans.xml by the Weld Arquillian plugin is ALL check instead of ANY) > excluded elements in beans.xml by the Weld Arquillian plugin is a ALL check instead of ANY > ------------------------------------------------------------------------------------------ > > Key: ARQ-2048 > URL: https://issues.jboss.org/browse/ARQ-2048 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > > Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 04:42:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 04:42:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2048) excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2048: ------------------------------------ Summary: excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any (was: excluded elements in beans.xml by the Weld Arquillian plugin is a ALL check instead of ANY) > excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any > ---------------------------------------------------------------------------------------------- > > Key: ARQ-2048 > URL: https://issues.jboss.org/browse/ARQ-2048 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > > Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 04:42:01 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 04:42:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2048) Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2048: ------------------------------------ Summary: Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any (was: excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any) > Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any > ---------------------------------------------------------------------------------------------- > > Key: ARQ-2048 > URL: https://issues.jboss.org/browse/ARQ-2048 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > > Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 04:47:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 04:47:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2048) Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2048: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-weld/pull/35 > Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any > ---------------------------------------------------------------------------------------------- > > Key: ARQ-2048 > URL: https://issues.jboss.org/browse/ARQ-2048 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > > Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 08:14:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 08:14:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2023) Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Summary: Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter (was: Use Weld relaxed default constructor configuration in Arquillian Weld SE embedded 1.1 adapter) > Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter > -------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 08:14:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 08:14:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Summary: Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment (was: Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter) > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 08:15:04 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 08:15:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Git Pull Request: https://github.com/arquillian/arquillian-container-weld/pull/36 (was: https://github.com/arquillian/arquillian-container-weld/pull/23) > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 12 08:16:00 2016 From: issues at jboss.org (Antonin Stefanutti (JIRA)) Date: Wed, 12 Oct 2016 08:16:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Description: Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. was: Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 13 03:54:01 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Thu, 13 Oct 2016 03:54:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes updated ARQ-2023: ----------------------------- Fix Version/s: weld_2.0.0.Beta4 Affects Version/s: weld_2.0.0.Beta3 > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > Priority: Minor > Fix For: weld_2.0.0.Beta4 > > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 13 03:54:01 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Thu, 13 Oct 2016 03:54:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes updated ARQ-2023: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > Priority: Minor > Fix For: weld_2.0.0.Beta4 > > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Oct 13 09:06:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Thu, 13 Oct 2016 09:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2048) Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes updated ARQ-2048: ----------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: weld_2.0.0.Beta4 Resolution: Done > Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any > ---------------------------------------------------------------------------------------------- > > Key: ARQ-2048 > URL: https://issues.jboss.org/browse/ARQ-2048 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > Fix For: weld_2.0.0.Beta4 > > > Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:52:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2026) Client activity failures should have more priority over server activities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2026: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Client activity failures should have more priority over server activities > ------------------------------------------------------------------------- > > Key: ARQ-2026 > URL: https://issues.jboss.org/browse/ARQ-2026 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Christian Schulz > Assignee: Christian Schulz > Fix For: warp_1.0.0.Alpha8 > > > I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException. > In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures. > In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts. > I would suggest to ignore AssertionErrors from server activities if there is a catched client exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:52:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:52:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2026) Client activity failures should have more priority over server activities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2026. ------------------------------- Resolution: Done > Client activity failures should have more priority over server activities > ------------------------------------------------------------------------- > > Key: ARQ-2026 > URL: https://issues.jboss.org/browse/ARQ-2026 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Christian Schulz > Assignee: Christian Schulz > Fix For: warp_1.0.0.Alpha8 > > > I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException. > In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures. > In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts. > I would suggest to ignore AssertionErrors from server activities if there is a catched client exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:53:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:53:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1237) Warp: use PortProber to determine free ports for proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1237: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Warp: use PortProber to determine free ports for proxy > ------------------------------------------------------ > > Key: ARQ-1237 > URL: https://issues.jboss.org/browse/ARQ-1237 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Christian Schulz > Priority: Minor > Fix For: warp_1.0.0.Alpha8 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Selenium 2 uses {{PortProber}} to check free ports to run Selenium Server on. > We can leverage that component too for Warp proxy and avoid conflicting ports. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:53:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:53:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2029) Tell us the HTTP method in debug mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2029: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Tell us the HTTP method in debug mode > ------------------------------------- > > Key: ARQ-2029 > URL: https://issues.jboss.org/browse/ARQ-2029 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Reporter: Christian Schulz > Assignee: Christian Schulz > Fix For: warp_1.0.0.Alpha8 > > > Prints parallel to requestUri the method. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:54:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2014) When warp is on classpath then almost every non-warp arquillian test fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2014: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > When warp is on classpath then almost every non-warp arquillian test fails > -------------------------------------------------------------------------- > > Key: ARQ-2014 > URL: https://issues.jboss.org/browse/ARQ-2014 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Alpha8 > > > Consider a test suite that contains a warp test (so you need to have the warp dependency on your classpath) and some other non-warp arquillian test. Then the non-warp tests fails with various exceptions depending on the type of the test. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:54:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2013) Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2013: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Update Arquillian, Drone, Resolver, JaCoCo and JUnit to newer version > --------------------------------------------------------------------- > > Key: ARQ-2013 > URL: https://issues.jboss.org/browse/ARQ-2013 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Alpha8 > > > Please update to newer versions to use the latest and greatest implementations. > In case of JaCoCo - the current version {{0.6.0.201210061924}} is not compatible with JDK8 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:54:00 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1988) Warp HTTPCore 4.3 dependency conflict with latest Drone Alpha5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1988: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Warp HTTPCore 4.3 dependency conflict with latest Drone Alpha5 > -------------------------------------------------------------- > > Key: ARQ-1988 > URL: https://issues.jboss.org/browse/ARQ-1988 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: warp_1.0.0.Alpha8 > > > Warp needs to upgrade to HTTPCore 4.4.3 to be compatible with Drone 2.0.0.Alpha5 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:54:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:54:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1923) Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1923: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Cannot build Warp 1.0.0.Alpha7 with OpenJDK 8 > --------------------------------------------- > > Key: ARQ-1923 > URL: https://issues.jboss.org/browse/ARQ-1923 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Pavol Pitonak > Assignee: Matous Jobanek > Fix For: warp_1.0.0.Alpha8 > > > # git clone https://github.com/arquillian/arquillian-extension-warp.git > # mvn clean install > result: > * when launched with OpenJDK 8, one test fails TestExecutedMethod.testSerializedAnnotation > {code} > java.lang.IllegalStateException: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:61) > at org.jboss.arquillian.warp.impl.shared.TestExecutedMethod.testSerializedAnnotation(TestExecutedMethod.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > Caused by: java.lang.IllegalStateException: Error instantiating proxy for annotation. Annotation type: interface org.jboss.arquillian.warp.impl.shared.TestingAnnotation > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:83) > at org.jboss.arquillian.warp.impl.shared.SerializedAnnotation.getAnnotation(SerializedAnnotation.java:59) > ... 24 more > Caused by: java.lang.IllegalAccessException: Class org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider can not access a member of class org.jboss.arquillian.warp.impl.shared.$Proxy5 with modifiers "public" > at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:101) > at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:295) > at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:287) > at java.lang.reflect.Constructor.newInstance(Constructor.java:398) > at org.jboss.arquillian.warp.impl.utils.AnnotationInstanceProvider.get(AnnotationInstanceProvider.java:76) > ... 25 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 08:54:01 2016 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Oct 2016 08:54:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1272) Warp: avoid need for user-defined serialVersionUID In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-1272: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Warp: avoid need for user-defined serialVersionUID > -------------------------------------------------- > > Key: ARQ-1272 > URL: https://issues.jboss.org/browse/ARQ-1272 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: warp_1.0.0.Alpha8 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > One of the options might be to generate serialVersionUID with Lombok: > http://projectlombok.org/mavenrepo/index.html -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Oct 14 16:35:00 2016 From: issues at jboss.org (George Lindholm (JIRA)) Date: Fri, 14 Oct 2016 16:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2049) Database connection closed after first @Test/@UsingDataSet in a class In-Reply-To: References: Message-ID: George Lindholm created ARQ-2049: ------------------------------------ Summary: Database connection closed after first @Test/@UsingDataSet in a class Key: ARQ-2049 URL: https://issues.jboss.org/browse/ARQ-2049 Project: Arquillian Issue Type: Bug Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha7, persistence_1.0.0.next Environment: arquillian-openejb-embedded-4 (4.7.4), derby 10, hibernate 4, java 8 Reporter: George Lindholm Assignee: Bartosz Majsak Once ARQ-2042 was resolved, I rebuilt arquillian-persistence against the new arquillian-core and ran into a problem where the database connection was being closed once the first test in my class had finished. I see the same pattern in some of the integration tests so I don't know what is different with my environment (other than openejb-embedded). After a lot of debugging I finally narrowed the problem down to this change from Alpha6: {code} private void createDatabaseConnection() { try { if (databaseConnectionProducer.get() != null && !databaseConnectionProducer.get().getConnection().isClosed()) { closeDatabaseConnection(); } {code} to Alpha7: {code} private void createDatabaseConnection() { if (databaseConnectionProducer.get()== null) { configureDatabaseConnection(); } } private void configureDatabaseConnection() { try { {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 19 07:10:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 19 Oct 2016 07:10:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2050) Exception thrown when using latest Arquillian Core (1.1.11.Final) In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2050: ----------------------------------- Summary: Exception thrown when using latest Arquillian Core (1.1.11.Final) Key: ARQ-2050 URL: https://issues.jboss.org/browse/ARQ-2050 Project: Arquillian Issue Type: Bug Components: Daemon Affects Versions: daemon_1.0.0.Alpha1 Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: /usr/share/maven/latest Java version: 1.8.0_77, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_77/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.7.7-200.fc24.x86_64", arch: "amd64", family: "unix" Reporter: Bartosz Majsak Assignee: Andrew Rubinger {code:} [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] Arquillian Daemon Aggregator and Build Parent [INFO] Build Resources [INFO] Wire Protocol [INFO] Arquillian Protocol [INFO] Server Daemon [INFO] Common Container Support [INFO] Main Client [INFO] Managed Container [INFO] Remote Container [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Arquillian Daemon Aggregator and Build Parent 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-parent --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-parent --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-parent --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-parent --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-parent --- [INFO] Executing: /bin/sh -c cd '/home/bartek/code/redhat/arquillian/arquillian-daemon' && 'git' 'rev-parse' '--verify' 'HEAD' [INFO] Working directory: /home/bartek/code/redhat/arquillian/arquillian-daemon [INFO] Storing buildNumber: 42e44abd8ab012422d724f2e62db206b70a71c90 at timestamp: 1476875160702 [INFO] Storing buildScmBranch: master [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-parent --- [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-parent --- [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-parent/1.0.0.Final-SNAPSHOT/arquillian-daemon-parent-1.0.0.Final-SNAPSHOT.pom [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Build Resources 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-build-resources --- [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-build-resources --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-build-resources --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-build-resources --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-build-resources --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-build-resources --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 4 resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-build-resources --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-build-resources --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-build-resources --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-build-resources --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-build-resources --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.jar [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-build-resources --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-build-resources --- [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-build-resources/1.0.0.Final-SNAPSHOT/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.jar [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-build-resources/1.0.0.Final-SNAPSHOT/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.pom [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-build-resources/1.0.0.Final-SNAPSHOT/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Wire Protocol 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-protocol-wire --- [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-protocol-wire --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-protocol-wire --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-protocol-wire --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-protocol-wire --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-protocol-wire --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-protocol-wire --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 1 source file to /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/classes [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-protocol-wire --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-protocol-wire --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-protocol-wire --- [INFO] No tests to run. [INFO] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-protocol-wire --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-protocol-wire --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-protocol-wire --- [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-wire/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-wire/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.pom [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-wire/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Arquillian Protocol 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-protocol-arquillian --- [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-protocol-arquillian --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-protocol-arquillian --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-protocol-arquillian --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-protocol-arquillian --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-protocol-arquillian --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-protocol-arquillian --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 5 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/classes [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-protocol-arquillian --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-protocol-arquillian --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-protocol-arquillian --- [INFO] No tests to run. [INFO] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-protocol-arquillian --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.jar [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-protocol-arquillian --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-protocol-arquillian --- [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-arquillian/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.jar [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-arquillian/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.pom [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-arquillian/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Server Daemon 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-server --- [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-server --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-server --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-server --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-server --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-server --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/server/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-server --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 5 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/classes [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-server --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/server/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-server --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 2 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-server --- [WARNING] The parameter forkMode is deprecated since version 2.14. Use forkCount and reuseForks instead. ------------------------------------------------------- T E S T S ------------------------------------------------------- Java HotSpot(TM) 64-Bit Server VM warning: ignoring option UseSplitVerifier; support was removed in 8.0 Running org.jboss.arquillian.daemon.server.ReflectionContractTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec - in org.jboss.arquillian.daemon.server.ReflectionContractTest Java HotSpot(TM) 64-Bit Server VM warning: ignoring option UseSplitVerifier; support was removed in 8.0 Running org.jboss.arquillian.daemon.server.NettyServerTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.622 sec - in org.jboss.arquillian.daemon.server.NettyServerTest Results : Tests run: 11, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-server --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-server --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-server --- [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-server/1.0.0.Final-SNAPSHOT/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/server/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-server/1.0.0.Final-SNAPSHOT/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.pom [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-server/1.0.0.Final-SNAPSHOT/arquillian-daemon-server-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Common Container Support 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-container-common --- [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-container-common --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-container-common --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-container-common --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-container-common --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-container-common --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-container-common --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 3 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/classes [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-container-common --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-container-common --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-container-common --- [INFO] No tests to run. [INFO] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-container-common --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.jar [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-container-common --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-container-common --- [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-container-common/1.0.0.Final-SNAPSHOT/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.jar [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-container-common/1.0.0.Final-SNAPSHOT/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.pom [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-container-common/1.0.0.Final-SNAPSHOT/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Main Client 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-main --- [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-main --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-main --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-main --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-main --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-main --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 4 resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-main --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 3 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-main --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/main/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-main --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-main --- [INFO] No tests to run. [INFO] [INFO] --- maven-dependency-plugin:2.10:copy (copyNetty) @ arquillian-daemon-main --- [INFO] Configured Artifact: io.netty:netty:?:jar [INFO] Copying netty-4.0.0.Alpha5.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/io/netty/main/netty.jar [INFO] [INFO] --- maven-dependency-plugin:2.10:copy (copyServer) @ arquillian-daemon-main --- [INFO] Configured Artifact: org.jboss.arquillian.daemon:arquillian-daemon-server:?:jar [INFO] Copying arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/arquillian/daemon/server/main/arquillian-daemon-server.jar [INFO] [INFO] --- maven-dependency-plugin:2.10:copy (copyWireProtocol) @ arquillian-daemon-main --- [INFO] Configured Artifact: org.jboss.arquillian.daemon:arquillian-daemon-protocol-wire:?:jar [INFO] Copying arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/arquillian/daemon/protocol/wire/main/arquillian-daemon-protocol-wire.jar [INFO] [INFO] --- maven-dependency-plugin:2.10:copy (copyShrinkWrap) @ arquillian-daemon-main --- [INFO] Configured Artifact: org.jboss.shrinkwrap:shrinkwrap-api:?:jar [INFO] Configured Artifact: org.jboss.shrinkwrap:shrinkwrap-spi:?:jar [INFO] Configured Artifact: org.jboss.shrinkwrap:shrinkwrap-impl-base:?:jar [INFO] Copying shrinkwrap-api-1.2.3.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/shrinkwrap/main/shrinkwrap-api.jar [INFO] Copying shrinkwrap-spi-1.2.3.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/shrinkwrap/main/shrinkwrap-spi.jar [INFO] Copying shrinkwrap-impl-base-1.2.3.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/shrinkwrap/main/shrinkwrap-impl-base.jar [INFO] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-main --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-main --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-shade-plugin:2.4.3:shade (default) @ arquillian-daemon-main --- [INFO] Including org.jboss.arquillian.daemon:arquillian-daemon-server:jar:1.0.0.Final-SNAPSHOT in the shaded jar. [INFO] Including org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3 in the shaded jar. [INFO] Including org.jboss.arquillian.daemon:arquillian-daemon-protocol-wire:jar:1.0.0.Final-SNAPSHOT in the shaded jar. [INFO] Including org.jboss.modules:jboss-modules:jar:1.1.3.GA in the shaded jar. [INFO] Replacing original artifact with shaded artifact. [INFO] Replacing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar with /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-shaded.jar [INFO] Dependency-reduced POM written at: /home/bartek/code/redhat/arquillian/arquillian-daemon/main/dependency-reduced-pom.xml [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-main --- [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-main/1.0.0.Final-SNAPSHOT/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/dependency-reduced-pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-main/1.0.0.Final-SNAPSHOT/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.pom [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-main/1.0.0.Final-SNAPSHOT/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Managed Container 1.0.0.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-container-managed --- [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-container-managed --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-container-managed --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-container-managed --- [INFO] [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-container-managed --- [INFO] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-container-managed --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-container-managed --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 3 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/classes [INFO] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-container-managed --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-container-managed --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 2 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-container-managed --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-container-managed --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/arquillian-daemon-container-managed-1.0.0.Final-SNAPSHOT.jar [INFO] [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-container-managed --- [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/arquillian-daemon-container-managed-1.0.0.Final-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-dependency-plugin:2.10:copy (copyMain) @ arquillian-daemon-container-managed --- [INFO] Configured Artifact: org.jboss.arquillian.daemon:arquillian-daemon-main:?:jar [INFO] Copying arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/arquillian-daemon-main.jar [INFO] [INFO] --- maven-surefire-plugin:2.19.1:test (it) @ arquillian-daemon-container-managed --- [WARNING] The parameter forkMode is deprecated since version 2.14. Use forkCount and reuseForks instead. ------------------------------------------------------- T E S T S ------------------------------------------------------- Java HotSpot(TM) 64-Bit Server VM warning: ignoring option UseSplitVerifier; support was removed in 8.0 Running org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.server.ServerBase start INFO: Server started on localhost.localdomain:12345 Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.087 sec <<< FAILURE! - in org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Time elapsed: 1.086 sec <<< ERROR! org.jboss.arquillian.container.spi.client.container.DeploymentException: Did not receive proper response from the server, instead was: java.lang.ExceptionInInitializerError at org.jboss.arquillian.daemon.container.common.DaemonDeployableContainerBase.deploy(DaemonDeployableContainerBase.java:170) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:201) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Time elapsed: 1.087 sec <<< FAILURE! java.lang.AssertionError: Deployment name should be set at org.jboss.arquillian.daemon.container.common.DaemonDeployableContainerBase.undeploy(DaemonDeployableContainerBase.java:209) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$2.perform(ContainerDeployController.java:119) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$2.perform(ContainerDeployController.java:110) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployedDeployment(ContainerDeployController.java:249) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeployManaged(ContainerDeployController.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:108) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:94) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:223) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) [NettyServer] Requesting shutdown... Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.server.ServerBase stop INFO: Requesting shutdown... [NettyServer] Server shutdown. Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.server.ServerBase stop INFO: Server shutdown. Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.main.Main$1 run INFO: Caught signal, shutting down... Results : Tests in error: org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest.org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Run 1: ManagedDaemonContainerTest.org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest ? Deployment Run 2: ManagedDaemonContainerTest.org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Deployment name should be set Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Arquillian Daemon Aggregator and Build Parent ...... SUCCESS [ 0.733 s] [INFO] Build Resources .................................... SUCCESS [ 0.420 s] [INFO] Wire Protocol ...................................... SUCCESS [ 0.478 s] [INFO] Arquillian Protocol ................................ SUCCESS [ 0.642 s] [INFO] Server Daemon ...................................... SUCCESS [ 2.884 s] [INFO] Common Container Support ........................... SUCCESS [ 0.684 s] [INFO] Main Client ........................................ SUCCESS [ 1.212 s] [INFO] Managed Container .................................. FAILURE [ 2.735 s] [INFO] Remote Container ................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 10.160 s [INFO] Finished at: 2016-10-19T13:06:10+02:00 [INFO] Final Memory: 32M/1164M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (it) on project arquillian-daemon-container-managed: There are test failures. [ERROR] [ERROR] Please refer to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :arquillian-daemon-container-managed arquillian-daemon [mvn clean install] {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Oct 19 07:10:00 2016 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 19 Oct 2016 07:10:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2050) Exception thrown when using latest Arquillian Core (1.1.11.Final) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-2050: ----------------------------------- Assignee: (was: Andrew Rubinger) > Exception thrown when using latest Arquillian Core (1.1.11.Final) > ----------------------------------------------------------------- > > Key: ARQ-2050 > URL: https://issues.jboss.org/browse/ARQ-2050 > Project: Arquillian > Issue Type: Bug > Components: Daemon > Affects Versions: daemon_1.0.0.Alpha1 > Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) > Maven home: /usr/share/maven/latest > Java version: 1.8.0_77, vendor: Oracle Corporation > Java home: /usr/java/jdk1.8.0_77/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.7.7-200.fc24.x86_64", arch: "amd64", family: "unix" > Reporter: Bartosz Majsak > > {code:} > [INFO] Scanning for projects... > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Build Order: > [INFO] > [INFO] Arquillian Daemon Aggregator and Build Parent > [INFO] Build Resources > [INFO] Wire Protocol > [INFO] Arquillian Protocol > [INFO] Server Daemon > [INFO] Common Container Support > [INFO] Main Client > [INFO] Managed Container > [INFO] Remote Container > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Arquillian Daemon Aggregator and Build Parent 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-parent --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-parent --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-parent --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-parent --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-parent --- > [INFO] Executing: /bin/sh -c cd '/home/bartek/code/redhat/arquillian/arquillian-daemon' && 'git' 'rev-parse' '--verify' 'HEAD' > [INFO] Working directory: /home/bartek/code/redhat/arquillian/arquillian-daemon > [INFO] Storing buildNumber: 42e44abd8ab012422d724f2e62db206b70a71c90 at timestamp: 1476875160702 > [INFO] Storing buildScmBranch: master > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-parent --- > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-parent --- > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-parent/1.0.0.Final-SNAPSHOT/arquillian-daemon-parent-1.0.0.Final-SNAPSHOT.pom > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Build Resources 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-build-resources --- > [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-build-resources --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-build-resources --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-build-resources --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-build-resources --- > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-build-resources --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 4 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-build-resources --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-build-resources --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-build-resources --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-build-resources --- > [INFO] Tests are skipped. > [INFO] > [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-build-resources --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.jar > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-build-resources --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-build-resources --- > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-build-resources/1.0.0.Final-SNAPSHOT/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.jar > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-build-resources/1.0.0.Final-SNAPSHOT/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT.pom > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/build-resources/target/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-build-resources/1.0.0.Final-SNAPSHOT/arquillian-daemon-build-resources-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Wire Protocol 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-protocol-wire --- > [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-protocol-wire --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-protocol-wire --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-protocol-wire --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-protocol-wire --- > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-protocol-wire --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-protocol-wire --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 1 source file to /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/classes > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-protocol-wire --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-protocol-wire --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-protocol-wire --- > [INFO] No tests to run. > [INFO] > [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-protocol-wire --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-protocol-wire --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-protocol-wire --- > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-wire/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-wire/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.pom > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-wire/target/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-wire/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Arquillian Protocol 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-protocol-arquillian --- > [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-protocol-arquillian --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-protocol-arquillian --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-protocol-arquillian --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-protocol-arquillian --- > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-protocol-arquillian --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-protocol-arquillian --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 5 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/classes > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-protocol-arquillian --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-protocol-arquillian --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-protocol-arquillian --- > [INFO] No tests to run. > [INFO] > [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-protocol-arquillian --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.jar > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-protocol-arquillian --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-protocol-arquillian --- > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-arquillian/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.jar > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-arquillian/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT.pom > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/protocol-arquillian/target/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-protocol-arquillian/1.0.0.Final-SNAPSHOT/arquillian-daemon-protocol-arquillian-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Server Daemon 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-server --- > [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-server --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-server --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-server --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-server --- > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-server --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/server/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-server --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 5 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/classes > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-server --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/server/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-server --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 2 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/test-classes > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-server --- > [WARNING] The parameter forkMode is deprecated since version 2.14. Use forkCount and reuseForks instead. > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option UseSplitVerifier; support was removed in 8.0 > Running org.jboss.arquillian.daemon.server.ReflectionContractTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec - in org.jboss.arquillian.daemon.server.ReflectionContractTest > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option UseSplitVerifier; support was removed in 8.0 > Running org.jboss.arquillian.daemon.server.NettyServerTest > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.622 sec - in org.jboss.arquillian.daemon.server.NettyServerTest > Results : > Tests run: 11, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-server --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-server --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-server --- > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-server/1.0.0.Final-SNAPSHOT/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/server/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-server/1.0.0.Final-SNAPSHOT/arquillian-daemon-server-1.0.0.Final-SNAPSHOT.pom > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/server/target/arquillian-daemon-server-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-server/1.0.0.Final-SNAPSHOT/arquillian-daemon-server-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Common Container Support 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-container-common --- > [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-container-common --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-container-common --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-container-common --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-container-common --- > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-container-common --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/src/main/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-container-common --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 3 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/classes > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-container-common --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-container-common --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-container-common --- > [INFO] No tests to run. > [INFO] > [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-container-common --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.jar > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-container-common --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-container-common --- > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-container-common/1.0.0.Final-SNAPSHOT/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.jar > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-container-common/1.0.0.Final-SNAPSHOT/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT.pom > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/container-common/target/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-container-common/1.0.0.Final-SNAPSHOT/arquillian-daemon-container-common-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Main Client 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-main --- > [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-main --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-main --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-main --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-main --- > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-main --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 4 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-main --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 3 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-main --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory /home/bartek/code/redhat/arquillian/arquillian-daemon/main/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-main --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-main --- > [INFO] No tests to run. > [INFO] > [INFO] --- maven-dependency-plugin:2.10:copy (copyNetty) @ arquillian-daemon-main --- > [INFO] Configured Artifact: io.netty:netty:?:jar > [INFO] Copying netty-4.0.0.Alpha5.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/io/netty/main/netty.jar > [INFO] > [INFO] --- maven-dependency-plugin:2.10:copy (copyServer) @ arquillian-daemon-main --- > [INFO] Configured Artifact: org.jboss.arquillian.daemon:arquillian-daemon-server:?:jar > [INFO] Copying arquillian-daemon-server-1.0.0.Final-SNAPSHOT.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/arquillian/daemon/server/main/arquillian-daemon-server.jar > [INFO] > [INFO] --- maven-dependency-plugin:2.10:copy (copyWireProtocol) @ arquillian-daemon-main --- > [INFO] Configured Artifact: org.jboss.arquillian.daemon:arquillian-daemon-protocol-wire:?:jar > [INFO] Copying arquillian-daemon-protocol-wire-1.0.0.Final-SNAPSHOT.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/arquillian/daemon/protocol/wire/main/arquillian-daemon-protocol-wire.jar > [INFO] > [INFO] --- maven-dependency-plugin:2.10:copy (copyShrinkWrap) @ arquillian-daemon-main --- > [INFO] Configured Artifact: org.jboss.shrinkwrap:shrinkwrap-api:?:jar > [INFO] Configured Artifact: org.jboss.shrinkwrap:shrinkwrap-spi:?:jar > [INFO] Configured Artifact: org.jboss.shrinkwrap:shrinkwrap-impl-base:?:jar > [INFO] Copying shrinkwrap-api-1.2.3.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/shrinkwrap/main/shrinkwrap-api.jar > [INFO] Copying shrinkwrap-spi-1.2.3.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/shrinkwrap/main/shrinkwrap-spi.jar > [INFO] Copying shrinkwrap-impl-base-1.2.3.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/classes/META-INF/modules/org/jboss/shrinkwrap/main/shrinkwrap-impl-base.jar > [INFO] > [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-main --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-main --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-shade-plugin:2.4.3:shade (default) @ arquillian-daemon-main --- > [INFO] Including org.jboss.arquillian.daemon:arquillian-daemon-server:jar:1.0.0.Final-SNAPSHOT in the shaded jar. > [INFO] Including org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3 in the shaded jar. > [INFO] Including org.jboss.arquillian.daemon:arquillian-daemon-protocol-wire:jar:1.0.0.Final-SNAPSHOT in the shaded jar. > [INFO] Including org.jboss.modules:jboss-modules:jar:1.1.3.GA in the shaded jar. > [INFO] Replacing original artifact with shaded artifact. > [INFO] Replacing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar with /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-shaded.jar > [INFO] Dependency-reduced POM written at: /home/bartek/code/redhat/arquillian/arquillian-daemon/main/dependency-reduced-pom.xml > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ arquillian-daemon-main --- > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-main/1.0.0.Final-SNAPSHOT/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/dependency-reduced-pom.xml to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-main/1.0.0.Final-SNAPSHOT/arquillian-daemon-main-1.0.0.Final-SNAPSHOT.pom > [INFO] Installing /home/bartek/code/redhat/arquillian/arquillian-daemon/main/target/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-sources.jar to /home/bartek/.m2/repository/org/jboss/arquillian/daemon/arquillian-daemon-main/1.0.0.Final-SNAPSHOT/arquillian-daemon-main-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Managed Container 1.0.0.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ arquillian-daemon-container-managed --- > [INFO] Deleting /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java-version) @ arquillian-daemon-container-managed --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ arquillian-daemon-container-managed --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-environment) @ arquillian-daemon-container-managed --- > [INFO] > [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ arquillian-daemon-container-managed --- > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ arquillian-daemon-container-managed --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ arquillian-daemon-container-managed --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 3 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/classes > [INFO] > [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ arquillian-daemon-container-managed --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ arquillian-daemon-container-managed --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 2 source files to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/test-classes > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ arquillian-daemon-container-managed --- > [INFO] Tests are skipped. > [INFO] > [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ arquillian-daemon-container-managed --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/arquillian-daemon-container-managed-1.0.0.Final-SNAPSHOT.jar > [INFO] > [INFO] --- maven-source-plugin:3.0.0:jar-no-fork (attach-sources) @ arquillian-daemon-container-managed --- > [INFO] Building jar: /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/arquillian-daemon-container-managed-1.0.0.Final-SNAPSHOT-sources.jar > [INFO] > [INFO] --- maven-dependency-plugin:2.10:copy (copyMain) @ arquillian-daemon-container-managed --- > [INFO] Configured Artifact: org.jboss.arquillian.daemon:arquillian-daemon-main:?:jar > [INFO] Copying arquillian-daemon-main-1.0.0.Final-SNAPSHOT.jar to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/arquillian-daemon-main.jar > [INFO] > [INFO] --- maven-surefire-plugin:2.19.1:test (it) @ arquillian-daemon-container-managed --- > [WARNING] The parameter forkMode is deprecated since version 2.14. Use forkCount and reuseForks instead. > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option UseSplitVerifier; support was removed in 8.0 > Running org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest > Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.server.ServerBase start > INFO: Server started on localhost.localdomain:12345 > Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.087 sec <<< FAILURE! - in org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest > org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Time elapsed: 1.086 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.DeploymentException: Did not receive proper response from the server, instead was: java.lang.ExceptionInInitializerError > at org.jboss.arquillian.daemon.container.common.DaemonDeployableContainerBase.deploy(DaemonDeployableContainerBase.java:170) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:201) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Time elapsed: 1.087 sec <<< FAILURE! > java.lang.AssertionError: Deployment name should be set > at org.jboss.arquillian.daemon.container.common.DaemonDeployableContainerBase.undeploy(DaemonDeployableContainerBase.java:209) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$2.perform(ContainerDeployController.java:119) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$2.perform(ContainerDeployController.java:110) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployedDeployment(ContainerDeployController.java:249) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeployManaged(ContainerDeployController.java:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:108) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:94) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:223) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > [NettyServer] Requesting shutdown... > Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.server.ServerBase stop > INFO: Requesting shutdown... > [NettyServer] Server shutdown. > Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.server.ServerBase stop > INFO: Server shutdown. > Oct 19, 2016 1:06:09 PM org.jboss.arquillian.daemon.main.Main$1 run > INFO: Caught signal, shutting down... > Results : > Tests in error: > org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest.org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest > Run 1: ManagedDaemonContainerTest.org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest ? Deployment > Run 2: ManagedDaemonContainerTest.org.jboss.arquillian.daemon.container.managed.ManagedDaemonContainerTest Deployment name should be set > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Arquillian Daemon Aggregator and Build Parent ...... SUCCESS [ 0.733 s] > [INFO] Build Resources .................................... SUCCESS [ 0.420 s] > [INFO] Wire Protocol ...................................... SUCCESS [ 0.478 s] > [INFO] Arquillian Protocol ................................ SUCCESS [ 0.642 s] > [INFO] Server Daemon ...................................... SUCCESS [ 2.884 s] > [INFO] Common Container Support ........................... SUCCESS [ 0.684 s] > [INFO] Main Client ........................................ SUCCESS [ 1.212 s] > [INFO] Managed Container .................................. FAILURE [ 2.735 s] > [INFO] Remote Container ................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 10.160 s > [INFO] Finished at: 2016-10-19T13:06:10+02:00 > [INFO] Final Memory: 32M/1164M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (it) on project arquillian-daemon-container-managed: There are test failures. > [ERROR] > [ERROR] Please refer to /home/bartek/code/redhat/arquillian/arquillian-daemon/container-managed/target/surefire-reports for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn -rf :arquillian-daemon-container-managed > arquillian-daemon [mvn clean install] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 24 04:55:00 2016 From: issues at jboss.org (arjan tijms (JIRA)) Date: Mon, 24 Oct 2016 04:55:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: arjan tijms created ARQ-2051: -------------------------------- Summary: Add ability to add localconnector feature automatically to server.xml Key: ARQ-2051 URL: https://issues.jboss.org/browse/ARQ-2051 Project: Arquillian Issue Type: Feature Request Components: WebSphere Containers Affects Versions: was_1.0.0.Beta2 Reporter: arjan tijms Assignee: Gerhard Poul For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 24 10:07:00 2016 From: issues at jboss.org (arjan tijms (JIRA)) Date: Mon, 24 Oct 2016 10:07:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] arjan tijms updated ARQ-2051: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/28 > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 24 16:59:00 2016 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 24 Oct 2016 16:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13311086#comment-13311086 ] Gerhard Poul commented on ARQ-2051: ----------------------------------- How are you downloading the liberty instance from Maven? If you're using the liberty:create-server goal it already provides an option for a configFile like we packaged it in our wlp-managed-85 test. Why is this more useful than that? I would think that if we start adding this, we will need further changes to support other features as well and at that point it just might be easier to include the server.xml as part of the test in the first place anyway; What do you think? > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 24 18:03:00 2016 From: issues at jboss.org (arjan tijms (JIRA)) Date: Mon, 24 Oct 2016 18:03:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13311105#comment-13311105 ] arjan tijms commented on ARQ-2051: ---------------------------------- Hi Gerhard, thanks for your comments. {quote}How are you downloading the liberty instance from Maven?{quote} See for example https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L962 It's basically the same method that the other profiles for other servers use as well. {quote}Why is this more useful than that?{quote} Packaging a copy of the server.xml file and then copying it over is quite a bit more work and less obvious then just setting a boolean. Ideally for the managed server variant this would even be the default (if I'm not mistaken TomEE does something like that). {quote}I would think that if we start adding this, we will need further changes to support other features{quote} Adding arbitrary other features (as in feature elements) would be rather trivial to support. The {{addFeatures}} method in the PR is already prepared for that. With that setting something like {{extraFeatures=usr:JaccFeature,JPA-1.0}} depending on conditions in the test setup is a bit higher level and more flexible than having to prepare a set of different full server.xml files for every combination. As a followup issue and PR I wanted to do something like as suggested here: http://stackoverflow.com/questions/39259375/loading-data-source-for-datasourcedefinition-from-application-in-liberty#comment65882759_39259375 That is, adding a jar from from the archive (or project) that's being deployed as a shared library ( tag) and then let the application reference that via the existing {{commonLibraryRef}} support. Doing that all in various combinations with static server.xml files may be a bit too much. > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Oct 24 18:04:00 2016 From: issues at jboss.org (arjan tijms (JIRA)) Date: Mon, 24 Oct 2016 18:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13311105#comment-13311105 ] arjan tijms edited comment on ARQ-2051 at 10/24/16 6:03 PM: ------------------------------------------------------------ Hi Gerhard, thanks for your comments. {quote}How are you downloading the liberty instance from Maven?{quote} See for example https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L962 It's basically the same method that the other profiles for other servers use as well. {quote}Why is this more useful than that?{quote} Packaging a copy of the server.xml file and then copying it over is quite a bit more work and less obvious than just setting a boolean. Ideally for the managed server variant this would even be the default (if I'm not mistaken TomEE does something like that). {quote}I would think that if we start adding this, we will need further changes to support other features{quote} Adding arbitrary other features (as in feature elements) would be rather trivial to support. The {{addFeatures}} method in the PR is already prepared for that. With that setting something like {{extraFeatures=usr:JaccFeature,JPA-1.0}} depending on conditions in the test setup is a bit higher level and more flexible than having to prepare a set of different full server.xml files for every combination. As a followup issue and PR I wanted to do something like as suggested here: http://stackoverflow.com/questions/39259375/loading-data-source-for-datasourcedefinition-from-application-in-liberty#comment65882759_39259375 That is, adding a jar from from the archive (or project) that's being deployed as a shared library ( tag) and then let the application reference that via the existing {{commonLibraryRef}} support. Doing that all in various combinations with static server.xml files may be a bit too much. was (Author: atijms): Hi Gerhard, thanks for your comments. {quote}How are you downloading the liberty instance from Maven?{quote} See for example https://github.com/javaee-samples/javaee7-samples/blob/master/pom.xml#L962 It's basically the same method that the other profiles for other servers use as well. {quote}Why is this more useful than that?{quote} Packaging a copy of the server.xml file and then copying it over is quite a bit more work and less obvious then just setting a boolean. Ideally for the managed server variant this would even be the default (if I'm not mistaken TomEE does something like that). {quote}I would think that if we start adding this, we will need further changes to support other features{quote} Adding arbitrary other features (as in feature elements) would be rather trivial to support. The {{addFeatures}} method in the PR is already prepared for that. With that setting something like {{extraFeatures=usr:JaccFeature,JPA-1.0}} depending on conditions in the test setup is a bit higher level and more flexible than having to prepare a set of different full server.xml files for every combination. As a followup issue and PR I wanted to do something like as suggested here: http://stackoverflow.com/questions/39259375/loading-data-source-for-datasourcedefinition-from-application-in-liberty#comment65882759_39259375 That is, adding a jar from from the archive (or project) that's being deployed as a shared library ( tag) and then let the application reference that via the existing {{commonLibraryRef}} support. Doing that all in various combinations with static server.xml files may be a bit too much. > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Oct 25 12:06:00 2016 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Tue, 25 Oct 2016 12:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13311636#comment-13311636 ] Gerhard Poul commented on ARQ-2051: ----------------------------------- >From a conceptual point of view this is just moving stuff from server.xml into arquillian.xml and it removes the need to use the liberty:create-server module in this specific case. I'm fine with adding this for people that prefer not to use the liberty:create-server module since the localConnector is a prerequisite for the arquillian container working, but I'd rather not duplicate functionality that is available in the liberty:create-server plugin like setting JVM parameters and others and just moving them into arquillian.xml without a good reason. FYI: At this point in time our CI tests on wercker seem not to be working because they changed how they work with the docker containers. I'll need to fix that first before I can test and merge your PR. > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v7.2.2#72004) From issues at jboss.org Tue Oct 25 15:44:00 2016 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Tue, 25 Oct 2016 15:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13311717#comment-13311717 ] Gerhard Poul commented on ARQ-2051: ----------------------------------- I've now created a new docker container that works with the current wercker environment and I also moved to the 1.2 version of the liberty-maven-plugin. The bad news is that at least for me the ApplicationMBean is never shown over the localConnector with the versions I tested with from the public maven repositories. I see a few other WebSphere:* MBeans, but not the ApplicationMBean. [~atijms] are you seeing this MBean? Can you tell me which exact JDK and liberty version you're using? tnx! > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v7.2.2#72004) From issues at jboss.org Tue Oct 25 16:23:00 2016 From: issues at jboss.org (arjan tijms (JIRA)) Date: Tue, 25 Oct 2016 16:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13311727#comment-13311727 ] arjan tijms commented on ARQ-2051: ---------------------------------- Thanks for looking into the PR Gerhard. I was seeing the {{com.ibm.websphere.application.ApplicationMBean}} indeed. The java version I used for the test was: {noformat} java -version java version "1.8.0_102" Java(TM) SE Runtime Environment (build 1.8.0_102-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode) {noformat} Liberty version is the latest from Maven; 16.0.0.3. OS is OS X. For the test I used the Soteria project (https://github.com/javaee-security-spec/soteria) where I removed the ant runt plug-in from line 409 onwards, see: https://github.com/javaee-security-spec/soteria/blob/master/test/pom.xml#L409 Then with the Liberty managed container that incorporated the PR installed I did: {noformat} mvn clean test install -Pliberty,bundled {noformat} _(just "install" should be sufficient but that was the exact command used)_ So it's a "plain" Liberty install without using Docker, wrecker or the Liberty maven plug-in. Hope this helps. > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v7.2.2#72004) From issues at jboss.org Fri Oct 28 13:44:00 2016 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Fri, 28 Oct 2016 13:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13313604#comment-13313604 ] Gerhard Poul commented on ARQ-2051: ----------------------------------- [~atijms] I found the root-cause and will probably be able to get this working over the weekend and finally make progress on your pull request. Sorry for the delay. > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v7.2.2#72004) From issues at jboss.org Fri Oct 28 17:37:00 2016 From: issues at jboss.org (arjan tijms (JIRA)) Date: Fri, 28 Oct 2016 17:37:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13313673#comment-13313673 ] arjan tijms commented on ARQ-2051: ---------------------------------- Great to hear you're making progress with that issue and thanks for the update! > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v7.2.2#72004) From issues at jboss.org Sat Oct 29 10:20:00 2016 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sat, 29 Oct 2016 10:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2051) Add ability to add localconnector feature automatically to server.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-2051: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Add ability to add localconnector feature automatically to server.xml > --------------------------------------------------------------------- > > Key: ARQ-2051 > URL: https://issues.jboss.org/browse/ARQ-2051 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: arjan tijms > Assignee: Gerhard Poul > > For the managed container for Liberty to connect to a liberty instance, the {{localConnector-1.0}} feature needs to be present in {{server.xml}}. > This is somewhat of an obstacle when using a CI managed Liberty, where a Liberty instance is downloaded and installed from Maven during the test. Following the work done in ARQ-1729 it should be relatively easy to add this {{localConnector-1.0}} feature to {{server.xml}}. > I would like to propose adding a new boolean to the configuration for the managed Liberty container, and when set to true the Arquillian container will add the mentioned feature and will thus be able to start Liberty without requiring the user to modify the installation first. > (I'll look into doing a PR for this) -- This message was sent by Atlassian JIRA (v7.2.2#72004)