From issues at jboss.org Fri Dec 1 09:09:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 1 Dec 2017 09:09:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2160) Upgrade to Selenium 3.8.0 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2160: ----------------------------------- Summary: Upgrade to Selenium 3.8.0 Key: ARQ-2160 URL: https://issues.jboss.org/browse/ARQ-2160 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.4.5 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.4.6 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Dec 1 09:09:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 1 Dec 2017 09:09:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2161) Update HtmlUnit driver to 2.28 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2161: ----------------------------------- Summary: Update HtmlUnit driver to 2.28 Key: ARQ-2161 URL: https://issues.jboss.org/browse/ARQ-2161 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.4.5 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.4.6 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Dec 1 15:34:00 2017 From: issues at jboss.org (Charles Tian (JIRA)) Date: Fri, 1 Dec 2017 15:34:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2162) New release for wlp-managed container In-Reply-To: References: Message-ID: Charles Tian created ARQ-2162: --------------------------------- Summary: New release for wlp-managed container Key: ARQ-2162 URL: https://issues.jboss.org/browse/ARQ-2162 Project: Arquillian Issue Type: Release Components: WebSphere Containers Reporter: Charles Tian Assignee: Gerhard Poul I'm a developer at IBM currently working on some updates for the Arquillian WLP managed container. I have some improvements which I'm planning to push out in the next couple of weeks. Once these changed get reviewed and merged, could we make a new release for the WLP managed container on Maven Central? The current version is 1.0.0.Beta2 and was released almost three years ago (Jan. 2015). Since then, there have been many updates made to the container (including the changes that I will be providing) that are not part of any release. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Sun Dec 3 03:00:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 3 Dec 2017 03:00:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2162) New release for wlp-managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496531#comment-13496531 ] Gerhard Poul commented on ARQ-2162: ----------------------------------- [~aslak] would you be able to take a look at the updates that will be made in https://github.com/arquillian/arquillian-container-was/pull/33 - and potentially new ones - when they're created and after that push a new release while I'm away? That would be great. > New release for wlp-managed container > ------------------------------------- > > Key: ARQ-2162 > URL: https://issues.jboss.org/browse/ARQ-2162 > Project: Arquillian > Issue Type: Release > Components: WebSphere Containers > Reporter: Charles Tian > Assignee: Gerhard Poul > > I'm a developer at IBM currently working on some updates for the Arquillian WLP managed container. I have some improvements which I'm planning to push out in the next couple of weeks. > Once these changed get reviewed and merged, could we make a new release for the WLP managed container on Maven Central? The current version is 1.0.0.Beta2 and was released almost three years ago (Jan. 2015). Since then, there have been many updates made to the container (including the changes that I will be providing) that are not part of any release. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Sun Dec 3 03:00:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Sun, 3 Dec 2017 03:00:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2162) New release for wlp-managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul reassigned ARQ-2162: --------------------------------- Assignee: Aslak Knutsen (was: Gerhard Poul) > New release for wlp-managed container > ------------------------------------- > > Key: ARQ-2162 > URL: https://issues.jboss.org/browse/ARQ-2162 > Project: Arquillian > Issue Type: Release > Components: WebSphere Containers > Reporter: Charles Tian > Assignee: Aslak Knutsen > > I'm a developer at IBM currently working on some updates for the Arquillian WLP managed container. I have some improvements which I'm planning to push out in the next couple of weeks. > Once these changed get reviewed and merged, could we make a new release for the WLP managed container on Maven Central? The current version is 1.0.0.Beta2 and was released almost three years ago (Jan. 2015). Since then, there have been many updates made to the container (including the changes that I will be providing) that are not part of any release. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Dec 4 07:25:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 4 Dec 2017 07:25:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2163) SessionNotCreatedException when running PhantomJS as remotewebdriver with Selenium 3.8.0 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2163: ----------------------------------- Summary: SessionNotCreatedException when running PhantomJS as remotewebdriver with Selenium 3.8.0 Key: ARQ-2163 URL: https://issues.jboss.org/browse/ARQ-2163 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.4.5 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.4.6 When running test with PhantomJS as a remote webdriver, and selenium server 3.8.0 the SessionNotCreatedException is thrown: {noformat} INFO: Running Selenium server process: java -Dphantomjs.binary.path=/home/mjobanek/arquillian/arquillian-extension-drone/drone-webdriver/target/drone/1c947d57fce2f21ce0b43fe2ed7cd361/phantomjs-2.1.1-linux-x86_64/bin/phantomjs -jar target/drone/ef4afb633c4a177144798c17036e2e64/selenium-server-standalone-3.8.0.jar -port 4444 Dec 04, 2017 1:24:05 PM org.arquillian.spacelift.Spacelift$SpaceliftInstance INFO: Initialized Spacelift from defaults, workspace: /home/mjobanek/arquillian/arquillian-extension-drone/drone-webdriver, cache: /home/mjobanek/.spacelift/cache [Selenium server] 13:24:05.716 INFO - Selenium build info: version: '3.8.0', revision: '924c4067df' [Selenium server] 13:24:05.717 INFO - Launching a standalone Selenium Server [Selenium server] 2017-12-04 13:24:05.782:INFO::main: Logging initialized @244ms to org.seleniumhq.jetty9.util.log.StdErrLog [Selenium server] 13:24:05.811 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` [Selenium server] 13:24:05.824 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` [Selenium server] 13:24:05.826 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()` [Selenium server] 13:24:05.827 INFO - Driver class not found: com.opera.core.systems.OperaDriver [Selenium server] 13:24:05.827 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()` [Selenium server] 13:24:05.827 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` [Selenium server] 13:24:05.828 INFO - Driver class not found: org.openqa.selenium.phantomjs.PhantomJSDriver [Selenium server] 13:24:05.857 INFO - Driver provider class org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: [Selenium server] registration capabilities Capabilities {browserName: internet explorer, ensureCleanSession: true, platform: WINDOWS, version: } does not match the current platform LINUX [Selenium server] 13:24:05.857 INFO - Driver provider class org.openqa.selenium.edge.EdgeDriver registration is skipped: [Selenium server] registration capabilities Capabilities {browserName: MicrosoftEdge, platform: WINDOWS, version: } does not match the current platform LINUX [Selenium server] 13:24:05.858 INFO - Driver provider class org.openqa.selenium.safari.SafariDriver registration is skipped: [Selenium server] registration capabilities Capabilities {browserName: safari, platform: MAC, version: } does not match the current platform LINUX [Selenium server] 13:24:05.887 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` [Selenium server] 13:24:05.888 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()` [Selenium server] 13:24:05.888 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` [Selenium server] 13:24:05.888 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()` [Selenium server] 13:24:05.888 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` [Selenium server] 13:24:05.895 INFO - Using the passthrough mode handler [Selenium server] 2017-12-04 13:24:05.917:INFO:osjs.Server:main: jetty-9.4.7.v20170914 [Selenium server] 2017-12-04 13:24:05.942:WARN:osjs.SecurityHandler:main: ServletContext at o.s.j.s.ServletContextHandler@2db7a79b{/,null,STARTING} has uncovered http methods for path: / [Selenium server] 2017-12-04 13:24:05.945:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler at 2db7a79b{/,null,AVAILABLE} [Selenium server] 2017-12-04 13:24:05.960:INFO:osjs.AbstractConnector:main: Started ServerConnector at 54b45561{HTTP/1.1,[http/1.1]}{0.0.0.0:4444} [Selenium server] 2017-12-04 13:24:05.961:INFO:osjs.Server:main: Started @423ms [Selenium server] 13:24:05.961 INFO - Selenium Server is up and running [Selenium server] 2017-12-04 13:24:06.350:INFO:osjshC.ROOT:qtp1612799726-14: org.openqa.selenium.remote.server.WebDriverServlet-6895a785: Initialising WebDriverServlet [Selenium server] 13:24:06.379 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.NoSessionHandler at 35178a93 [Selenium server] 13:24:06.381 INFO - /session/3f6b96b0-d8e7-11e7-8b89-71db65b1fafa/url: Executing GET on /session/3f6b96b0-d8e7-11e7-8b89-71db65b1fafa/url (handler: NoSessionHandler) Dec 04, 2017 1:24:06 PM org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory createReusableDriver WARNING: Unable to reuse session: 3f6b96b0-d8e7-11e7-8b89-71db65b1fafa [Selenium server] 13:24:06.525 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.BeginSession at 7a9815d3 [Selenium server] 13:24:06.525 INFO - /session: Executing POST on /session (handler: BeginSession) [Selenium server] 13:24:06.572 INFO - Capabilities are: Capabilities {acceptSslCerts: true, browserName: phantomjs, firefoxUserPreferences: target/test-classes/prefs.js, loggingPrefs: org.openqa.selenium.logging..., seleniumServerVersion: 3.8.0, version: , webStorageEnabled: true, webdriver.firefox.profile: selenium} [Selenium server] 13:24:06.577 INFO - Capabilities are: Capabilities {browserName: phantomjs} [Selenium server] 13:24:06.578 INFO - Using default factory: org.openqa.selenium.chrome.ChromeDriverService org.openqa.selenium.SessionNotCreatedException: Unable to create new service: ChromeDriverService Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:37:19.049Z' System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' Driver info: driver.version: unknown Command duration or timeout: 82 milliseconds at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214) at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166) at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53) at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91) at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:123) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958) at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464) at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:126) at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:73) at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601) at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:219) at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:142) at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:155) at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createRemoteDriver(RemoteWebDriverFactory.java:220) at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createReusableDriver(RemoteWebDriverFactory.java:248) at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:131) at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:56) at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:89) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.openqa.selenium.SessionNotCreatedException: Unable to create new service: ChromeDriverService Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:37:19.049Z' System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' Driver info: driver.version: unknown Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:20:39.408Z' System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' Driver info: driver.version: unknown at org.openqa.selenium.remote.server.ServicedSession$Factory.lambda$get$0(ServicedSession.java:208) at org.openqa.selenium.remote.server.ServicedSession$Factory.apply(ServicedSession.java:218) at org.openqa.selenium.remote.server.DefaultPipeline.lambda$null$1(DefaultPipeline.java:59) at org.openqa.selenium.remote.server.NewSessionPipeline.lambda$createNewSession$4(NewSessionPipeline.java:52) at java.util.Optional.orElseGet(Optional.java:267) at org.openqa.selenium.remote.server.NewSessionPipeline.createNewSession(NewSessionPipeline.java:51) at org.openqa.selenium.remote.server.commandhandler.BeginSession.execute(BeginSession.java:77) at org.openqa.selenium.remote.server.WebDriverServlet.lambda$handle$0(WebDriverServlet.java:240) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ... 4 more {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Dec 4 07:30:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 4 Dec 2017 07:30:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2163) SessionNotCreatedException when running PhantomJS as remotewebdriver with Selenium 3.8.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496789#comment-13496789 ] Matous Jobanek commented on ARQ-2163: ------------------------------------- The reason is that PhantomJS dependency was removed from the Selenium project since 3.8.0. See this commit: https://github.com/SeleniumHQ/selenium/commit/de5c81fd86a3228195d2f6d5d9526bbc4b3c3534 There are two workarounds: * use any older version of selenium server by adding {{3.7.1}} to your {{arquillian.xml}} file * start selenium server by hand on command line and add the PhantomJS driver jar on classpath (the jar has to contain {{org.openqa.selenium.phantomjs.PhantomJSDriverService}} class) > SessionNotCreatedException when running PhantomJS as remotewebdriver with Selenium 3.8.0 > ---------------------------------------------------------------------------------------- > > Key: ARQ-2163 > URL: https://issues.jboss.org/browse/ARQ-2163 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.4.5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.4.6 > > > When running test with PhantomJS as a remote webdriver, and selenium server 3.8.0 the SessionNotCreatedException is thrown: > {noformat} > INFO: Running Selenium server process: java -Dphantomjs.binary.path=/home/mjobanek/arquillian/arquillian-extension-drone/drone-webdriver/target/drone/1c947d57fce2f21ce0b43fe2ed7cd361/phantomjs-2.1.1-linux-x86_64/bin/phantomjs -jar target/drone/ef4afb633c4a177144798c17036e2e64/selenium-server-standalone-3.8.0.jar -port 4444 > Dec 04, 2017 1:24:05 PM org.arquillian.spacelift.Spacelift$SpaceliftInstance > INFO: Initialized Spacelift from defaults, workspace: /home/mjobanek/arquillian/arquillian-extension-drone/drone-webdriver, cache: /home/mjobanek/.spacelift/cache > [Selenium server] 13:24:05.716 INFO - Selenium build info: version: '3.8.0', revision: '924c4067df' > [Selenium server] 13:24:05.717 INFO - Launching a standalone Selenium Server > [Selenium server] 2017-12-04 13:24:05.782:INFO::main: Logging initialized @244ms to org.seleniumhq.jetty9.util.log.StdErrLog > [Selenium server] 13:24:05.811 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` > [Selenium server] 13:24:05.824 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` > [Selenium server] 13:24:05.826 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()` > [Selenium server] 13:24:05.827 INFO - Driver class not found: com.opera.core.systems.OperaDriver > [Selenium server] 13:24:05.827 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()` > [Selenium server] 13:24:05.827 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` > [Selenium server] 13:24:05.828 INFO - Driver class not found: org.openqa.selenium.phantomjs.PhantomJSDriver > [Selenium server] 13:24:05.857 INFO - Driver provider class org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: > [Selenium server] registration capabilities Capabilities {browserName: internet explorer, ensureCleanSession: true, platform: WINDOWS, version: } does not match the current platform LINUX > [Selenium server] 13:24:05.857 INFO - Driver provider class org.openqa.selenium.edge.EdgeDriver registration is skipped: > [Selenium server] registration capabilities Capabilities {browserName: MicrosoftEdge, platform: WINDOWS, version: } does not match the current platform LINUX > [Selenium server] 13:24:05.858 INFO - Driver provider class org.openqa.selenium.safari.SafariDriver registration is skipped: > [Selenium server] registration capabilities Capabilities {browserName: safari, platform: MAC, version: } does not match the current platform LINUX > [Selenium server] 13:24:05.887 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` > [Selenium server] 13:24:05.888 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()` > [Selenium server] 13:24:05.888 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` > [Selenium server] 13:24:05.888 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()` > [Selenium server] 13:24:05.888 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` > [Selenium server] 13:24:05.895 INFO - Using the passthrough mode handler > [Selenium server] 2017-12-04 13:24:05.917:INFO:osjs.Server:main: jetty-9.4.7.v20170914 > [Selenium server] 2017-12-04 13:24:05.942:WARN:osjs.SecurityHandler:main: ServletContext at o.s.j.s.ServletContextHandler@2db7a79b{/,null,STARTING} has uncovered http methods for path: / > [Selenium server] 2017-12-04 13:24:05.945:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler at 2db7a79b{/,null,AVAILABLE} > [Selenium server] 2017-12-04 13:24:05.960:INFO:osjs.AbstractConnector:main: Started ServerConnector at 54b45561{HTTP/1.1,[http/1.1]}{0.0.0.0:4444} > [Selenium server] 2017-12-04 13:24:05.961:INFO:osjs.Server:main: Started @423ms > [Selenium server] 13:24:05.961 INFO - Selenium Server is up and running > [Selenium server] 2017-12-04 13:24:06.350:INFO:osjshC.ROOT:qtp1612799726-14: org.openqa.selenium.remote.server.WebDriverServlet-6895a785: Initialising WebDriverServlet > [Selenium server] 13:24:06.379 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.NoSessionHandler at 35178a93 > [Selenium server] 13:24:06.381 INFO - /session/3f6b96b0-d8e7-11e7-8b89-71db65b1fafa/url: Executing GET on /session/3f6b96b0-d8e7-11e7-8b89-71db65b1fafa/url (handler: NoSessionHandler) > Dec 04, 2017 1:24:06 PM org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory createReusableDriver > WARNING: Unable to reuse session: 3f6b96b0-d8e7-11e7-8b89-71db65b1fafa > [Selenium server] 13:24:06.525 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.BeginSession at 7a9815d3 > [Selenium server] 13:24:06.525 INFO - /session: Executing POST on /session (handler: BeginSession) > [Selenium server] 13:24:06.572 INFO - Capabilities are: Capabilities {acceptSslCerts: true, browserName: phantomjs, firefoxUserPreferences: target/test-classes/prefs.js, loggingPrefs: org.openqa.selenium.logging..., seleniumServerVersion: 3.8.0, version: , webStorageEnabled: true, webdriver.firefox.profile: selenium} > [Selenium server] 13:24:06.577 INFO - Capabilities are: Capabilities {browserName: phantomjs} > [Selenium server] 13:24:06.578 INFO - Using default factory: org.openqa.selenium.chrome.ChromeDriverService > org.openqa.selenium.SessionNotCreatedException: Unable to create new service: ChromeDriverService > Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:37:19.049Z' > System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' > Driver info: driver.version: unknown > Command duration or timeout: 82 milliseconds > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214) > at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166) > at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53) > at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91) > at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:123) > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) > at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958) > at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) > at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464) > at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:126) > at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:73) > at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142) > at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601) > at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:219) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:142) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:155) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createRemoteDriver(RemoteWebDriverFactory.java:220) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createReusableDriver(RemoteWebDriverFactory.java:248) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:131) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:56) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) > at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) > at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) > at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.openqa.selenium.SessionNotCreatedException: Unable to create new service: ChromeDriverService > Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:37:19.049Z' > System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' > Driver info: driver.version: unknown > Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:20:39.408Z' > System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' > Driver info: driver.version: unknown > at org.openqa.selenium.remote.server.ServicedSession$Factory.lambda$get$0(ServicedSession.java:208) > at org.openqa.selenium.remote.server.ServicedSession$Factory.apply(ServicedSession.java:218) > at org.openqa.selenium.remote.server.DefaultPipeline.lambda$null$1(DefaultPipeline.java:59) > at org.openqa.selenium.remote.server.NewSessionPipeline.lambda$createNewSession$4(NewSessionPipeline.java:52) > at java.util.Optional.orElseGet(Optional.java:267) > at org.openqa.selenium.remote.server.NewSessionPipeline.createNewSession(NewSessionPipeline.java:51) > at org.openqa.selenium.remote.server.commandhandler.BeginSession.execute(BeginSession.java:77) > at org.openqa.selenium.remote.server.WebDriverServlet.lambda$handle$0(WebDriverServlet.java:240) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 6 03:27:00 2017 From: issues at jboss.org (Ladislav Thon (JIRA)) Date: Wed, 6 Dec 2017 03:27:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2107) ResourceInjectionEnricher doesn't consult the @Resource(lookup = "...") value In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497707#comment-13497707 ] Ladislav Thon commented on ARQ-2107: ------------------------------------ Just FYI, since this happened in WildFly Swarm, there's now a test in WildFly Swarm, see SWARM-1713. > ResourceInjectionEnricher doesn't consult the @Resource(lookup = "...") value > ----------------------------------------------------------------------------- > > Key: ARQ-2107 > URL: https://issues.jboss.org/browse/ARQ-2107 > Project: Arquillian > Issue Type: Bug > Components: Runtime Enricher SPI > Affects Versions: 1.1.13.Final > Reporter: Ladislav Thon > Fix For: 1.1.14.Final > > > The {{ResourceInjectionEnricher}} supports injecting the test instance fields annotated with {{javax.annotation.Resource}}. However, looking at the {{ResourceInjectionEnricher.getResourceName}} method, it only consults the annotation's {{name}} and {{mappedName}} attributes, falling back to some default afterward. The annotation's {{lookup}} attribute isn't considered at all. This might be because the {{lookup}} attribute was only added in Java EE 6 / Java SE 7, and Arquillian still supports Java 6, but that can be solved with a little bit of reflection. > I don't know if this omission was intentional or not, but it could have easily gone unnoticed for a long while, because if CDI is present, the {{CDIInjectionEnricher}} will inject such field. However, CDI doesn't necessarily have to be present -- for example with WildFly Swarm. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 6 03:27:00 2017 From: issues at jboss.org (Ladislav Thon (JIRA)) Date: Wed, 6 Dec 2017 03:27:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2109) EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497708#comment-13497708 ] Ladislav Thon commented on ARQ-2109: ------------------------------------ Just FYI, since this happened in WildFly Swarm, there's now a test in WildFly Swarm, see SWARM-1713. > EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case > ------------------------------------------------------------------------------------------ > > Key: ARQ-2109 > URL: https://issues.jboss.org/browse/ARQ-2109 > Project: Arquillian > Issue Type: Bug > Components: Runtime Enricher SPI > Affects Versions: 1.1.13.Final > Reporter: Ladislav Thon > Fix For: 1.1.14.Final > > > The {{EJBInjectionEnricher}} supports injecting the test instance fields annotated with {{javax.ejb.EJB}}. However, looking at the {{EJBInjectionEnricher.getJndiNamesForAnonymousEJB}} method, it makes too strong assumptions about the JNDI name. Specifically, it assumes the {{test.ear}} and {{test}} names. That doesn't necessarily have to be correct (e.g. WildFly Swarm Arquillian adapter doesn't use these names). There's an easy way to improve this for some situations: also consider the {{java:module}} portable namespace. It can't fix all situations, but it does fix some of them. (For Swarm, it's completely enough, since Swarm doesn't support EARs.) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 05:00:00 2017 From: issues at jboss.org (moritz l (JIRA)) Date: Tue, 12 Dec 2017 05:00:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2164) Support RandomBeans to create instances in Arquillian tests (e.g. JPA) In-Reply-To: References: Message-ID: moritz l created ARQ-2164: ----------------------------- Summary: Support RandomBeans to create instances in Arquillian tests (e.g. JPA) Key: ARQ-2164 URL: https://issues.jboss.org/browse/ARQ-2164 Project: Arquillian Issue Type: Feature Request Reporter: moritz l Long time ago i created this thread: https://developer.jboss.org/thread/273321?_sscc=t and i was suggested to create a ticket here. [RandomBeans|https://github.com/benas/random-beans] is great (test) framework to generate instances of classes. Especially for nested/ complex class structure it is very handy to just create the object you want and RandomBeans creates all needed/ nested objects. It would be nice to be able to use RandomBeans in Arquillian tests - in my case JPA Tests on Wildfly. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 08:37:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 12 Dec 2017 08:37:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2165) Properties are not loaded correctly when searching for /META-INF In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2165: ----------------------------------- Summary: Properties are not loaded correctly when searching for /META-INF Key: ARQ-2165 URL: https://issues.jboss.org/browse/ARQ-2165 Project: Arquillian Issue Type: Bug Components: Weld Containers Affects Versions: weld_2.0.0.Beta5 Reporter: Bartosz Majsak Priority: Minor *Issue Overview* While inside a Weld archive WAR file, the classloader used is unable to locate /META-INF/somefile.properties. *Expected Behaviour* Searching for /META-INF/somefile.properties and META-INF/somefile.properties should work fine. *Current Behaviour* Looking up META-INF/somefile.properties works, but having the leading / causes it to fail -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 08:38:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 12 Dec 2017 08:38:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2165) Properties are not loaded correctly when searching for /META-INF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2165: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-weld/pull/44 > Properties are not loaded correctly when searching for /META-INF > ---------------------------------------------------------------- > > Key: ARQ-2165 > URL: https://issues.jboss.org/browse/ARQ-2165 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta5 > Reporter: Bartosz Majsak > Priority: Minor > Fix For: Weld_2.0.0.Final > > > *Issue Overview* > While inside a Weld archive WAR file, the classloader used is unable to locate /META-INF/somefile.properties. > *Expected Behaviour* > Searching for /META-INF/somefile.properties and META-INF/somefile.properties should work fine. > *Current Behaviour* > Looking up META-INF/somefile.properties works, but having the leading / causes it to fail -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 08:38:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 12 Dec 2017 08:38:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2165) Properties are not loaded correctly when searching for /META-INF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-2165: ----------------------------------- Assignee: Bartosz Majsak > Properties are not loaded correctly when searching for /META-INF > ---------------------------------------------------------------- > > Key: ARQ-2165 > URL: https://issues.jboss.org/browse/ARQ-2165 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta5 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > Fix For: Weld_2.0.0.Final > > > *Issue Overview* > While inside a Weld archive WAR file, the classloader used is unable to locate /META-INF/somefile.properties. > *Expected Behaviour* > Searching for /META-INF/somefile.properties and META-INF/somefile.properties should work fine. > *Current Behaviour* > Looking up META-INF/somefile.properties works, but having the leading / causes it to fail -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 08:38:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 12 Dec 2017 08:38:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2165) Properties are not loaded correctly when searching for /META-INF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2165: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Properties are not loaded correctly when searching for /META-INF > ---------------------------------------------------------------- > > Key: ARQ-2165 > URL: https://issues.jboss.org/browse/ARQ-2165 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta5 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > > *Issue Overview* > While inside a Weld archive WAR file, the classloader used is unable to locate /META-INF/somefile.properties. > *Expected Behaviour* > Searching for /META-INF/somefile.properties and META-INF/somefile.properties should work fine. > *Current Behaviour* > Looking up META-INF/somefile.properties works, but having the leading / causes it to fail -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 08:38:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 12 Dec 2017 08:38:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2165) Properties are not loaded correctly when searching for /META-INF In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2165: -------------------------------- Fix Version/s: Weld_2.0.0.Final > Properties are not loaded correctly when searching for /META-INF > ---------------------------------------------------------------- > > Key: ARQ-2165 > URL: https://issues.jboss.org/browse/ARQ-2165 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta5 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > Fix For: Weld_2.0.0.Final > > > *Issue Overview* > While inside a Weld archive WAR file, the classloader used is unable to locate /META-INF/somefile.properties. > *Expected Behaviour* > Searching for /META-INF/somefile.properties and META-INF/somefile.properties should work fine. > *Current Behaviour* > Looking up META-INF/somefile.properties works, but having the leading / causes it to fail -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 11:16:00 2017 From: issues at jboss.org (Radoslav Husar (JIRA)) Date: Tue, 12 Dec 2017 11:16:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2166) IllegalArgumentException when accessing @Inject-ed instances from a different thread In-Reply-To: References: Message-ID: Radoslav Husar created ARQ-2166: ----------------------------------- Summary: IllegalArgumentException when accessing @Inject-ed instances from a different thread Key: ARQ-2166 URL: https://issues.jboss.org/browse/ARQ-2166 Project: Arquillian Issue Type: Task Components: Base Implementation Affects Versions: 1.1.15.Final Reporter: Radoslav Husar The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers. This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: {noformat} org.jboss.arquillian.core.spi.context.AbstractContext#activeStore org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts org.jboss.arquillian.core.impl.ManagerImpl#resolve org.jboss.arquillian.core.impl.InstanceImpl#get org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) {noformat} and example stack trace, trying to use container controller would be: {noformat} java.lang.IllegalArgumentException: No container registry in context at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 11:18:00 2017 From: issues at jboss.org (Radoslav Husar (JIRA)) Date: Tue, 12 Dec 2017 11:18:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2166) IllegalArgumentException when accessing @Inject-ed instances from a different thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radoslav Husar updated ARQ-2166: -------------------------------- Description: The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: {noformat} org.jboss.arquillian.core.spi.context.AbstractContext#activeStore org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts org.jboss.arquillian.core.impl.ManagerImpl#resolve org.jboss.arquillian.core.impl.InstanceImpl#get org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) {noformat} and example stack trace, trying to use container controller would be: {noformat} java.lang.IllegalArgumentException: No container registry in context at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} was: The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers. This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: {noformat} org.jboss.arquillian.core.spi.context.AbstractContext#activeStore org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts org.jboss.arquillian.core.impl.ManagerImpl#resolve org.jboss.arquillian.core.impl.InstanceImpl#get org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) {noformat} and example stack trace, trying to use container controller would be: {noformat} java.lang.IllegalArgumentException: No container registry in context at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} > IllegalArgumentException when accessing @Inject-ed instances from a different thread > ------------------------------------------------------------------------------------ > > Key: ARQ-2166 > URL: https://issues.jboss.org/browse/ARQ-2166 > Project: Arquillian > Issue Type: Task > Components: Base Implementation > Affects Versions: 1.1.15.Final > Reporter: Radoslav Husar > > The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. > This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: > {noformat} > org.jboss.arquillian.core.spi.context.AbstractContext#activeStore > org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts > org.jboss.arquillian.core.impl.ManagerImpl#resolve > org.jboss.arquillian.core.impl.InstanceImpl#get > org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) > {noformat} > and example stack trace, trying to use container controller would be: > {noformat} > java.lang.IllegalArgumentException: No container registry in context > at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) > at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) > at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 11:28:00 2017 From: issues at jboss.org (Radoslav Husar (JIRA)) Date: Tue, 12 Dec 2017 11:28:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2166) IllegalArgumentException when accessing @Inject-ed instances from a different thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radoslav Husar updated ARQ-2166: -------------------------------- Description: The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: {noformat} org.jboss.arquillian.core.spi.context.AbstractContext#activeStore org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts org.jboss.arquillian.core.impl.ManagerImpl#resolve org.jboss.arquillian.core.impl.InstanceImpl#get org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) {noformat} and example stack trace, trying to use container controller from a different thread would be: {noformat} java.lang.IllegalArgumentException: No container registry in context at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} was: The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: {noformat} org.jboss.arquillian.core.spi.context.AbstractContext#activeStore org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts org.jboss.arquillian.core.impl.ManagerImpl#resolve org.jboss.arquillian.core.impl.InstanceImpl#get org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) {noformat} and example stack trace, trying to use container controller would be: {noformat} java.lang.IllegalArgumentException: No container registry in context at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} > IllegalArgumentException when accessing @Inject-ed instances from a different thread > ------------------------------------------------------------------------------------ > > Key: ARQ-2166 > URL: https://issues.jboss.org/browse/ARQ-2166 > Project: Arquillian > Issue Type: Task > Components: Base Implementation > Affects Versions: 1.1.15.Final > Reporter: Radoslav Husar > > The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. > This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: > {noformat} > org.jboss.arquillian.core.spi.context.AbstractContext#activeStore > org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts > org.jboss.arquillian.core.impl.ManagerImpl#resolve > org.jboss.arquillian.core.impl.InstanceImpl#get > org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) > {noformat} > and example stack trace, trying to use container controller from a different thread would be: > {noformat} > java.lang.IllegalArgumentException: No container registry in context > at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) > at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) > at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 11:29:00 2017 From: issues at jboss.org (Radoslav Husar (JIRA)) Date: Tue, 12 Dec 2017 11:29:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2166) IllegalArgumentException when accessing @Inject-ed instances from a different thread In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radoslav Husar updated ARQ-2166: -------------------------------- Description: The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. The root cause of the issue is that ARQ is using ThreadLocal for storing the context. An example call stack would be the following: {noformat} org.jboss.arquillian.core.spi.context.AbstractContext#activeStore org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts org.jboss.arquillian.core.impl.ManagerImpl#resolve org.jboss.arquillian.core.impl.InstanceImpl#get org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) {noformat} and example stack trace, trying to use container controller from a different thread would be: {noformat} java.lang.IllegalArgumentException: No container registry in context at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} was: The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. This is because ARQ is using ThreadLocal for storing the context. An example call stack would be the following: {noformat} org.jboss.arquillian.core.spi.context.AbstractContext#activeStore org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts org.jboss.arquillian.core.impl.ManagerImpl#resolve org.jboss.arquillian.core.impl.InstanceImpl#get org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) {noformat} and example stack trace, trying to use container controller from a different thread would be: {noformat} java.lang.IllegalArgumentException: No container registry in context at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} > IllegalArgumentException when accessing @Inject-ed instances from a different thread > ------------------------------------------------------------------------------------ > > Key: ARQ-2166 > URL: https://issues.jboss.org/browse/ARQ-2166 > Project: Arquillian > Issue Type: Task > Components: Base Implementation > Affects Versions: 1.1.15.Final > Reporter: Radoslav Husar > > The use case for using multiple threads is to for instance start containers or deployments concurrently, which could be employed to speed up a testsuites using multiple containers where the tests control their lifecycle using container controller. > The root cause of the issue is that ARQ is using ThreadLocal for storing the context. An example call stack would be the following: > {noformat} > org.jboss.arquillian.core.spi.context.AbstractContext#activeStore > org.jboss.arquillian.core.impl.ManagerImpl#resolveActiveContexts > org.jboss.arquillian.core.impl.ManagerImpl#resolve > org.jboss.arquillian.core.impl.InstanceImpl#get > org.jboss.arquillian.container.test.impl.client.container.ClientContainerController#start(java.lang.String) > {noformat} > and example stack trace, trying to use container controller from a different thread would be: > {noformat} > java.lang.IllegalArgumentException: No container registry in context > at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.isStarted(ClientContainerController.java:216) > at org.jboss.as.test.clustering.NodeUtil.start(NodeUtil.java:104) > at org.jboss.as.test.clustering.NodeUtil.lambda$start$1(NodeUtil.java:85) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 14:12:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 14:12:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2167) Upgrade to Selenium 3.8.1 In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2167: ----------------------------------- Summary: Upgrade to Selenium 3.8.1 Key: ARQ-2167 URL: https://issues.jboss.org/browse/ARQ-2167 Project: Arquillian Issue Type: Component Upgrade Components: Extension - Drone Affects Versions: drone_2.4.5 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.4.6 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 14:17:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 14:17:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2154) phantomjs download and extraction remains without effect if Maven is started in a parent or aggregator project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2154: -------------------------------- Fix Version/s: drone_2.5.0 > phantomjs download and extraction remains without effect if Maven is started in a parent or aggregator project > -------------------------------------------------------------------------------------------------------------- > > Key: ARQ-2154 > URL: https://issues.jboss.org/browse/ARQ-2154 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.14.Final > Reporter: Karl-Philipp Richter > Assignee: Matous Jobanek > Fix For: drone_2.5.0 > > > Arquillian Spacelift and Arquillian Drone Webdriver don't resolve the directory where to findd the downloaded Selenium driver for phantomjs consistently. They seem to use the working directory which isn't changed if Maven is started in an aggregator project root and the Maven basedir property so that the `@Deployment` method fails due to > {code:java} > java.lang.IllegalStateException: Something bad happened when Drone was trying to download and prepare a binary. For more information see the cause. > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:62) > at org.jboss.arquillian.drone.webdriver.factory.PhantomJSDriverFactory.getCapabilities(PhantomJSDriverFactory.java:99) > at org.jboss.arquillian.drone.webdriver.factory.PhantomJSDriverFactory.createInstance(PhantomJSDriverFactory.java:72) > at org.jboss.arquillian.drone.webdriver.factory.PhantomJSDriverFactory.createInstance(PhantomJSDriverFactory.java:37) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) > at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) > at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) > at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:88) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.arquillian.spacelift.execution.ExecutionException: Execution of a task failed. Unable to execute task UntarTool > at org.arquillian.spacelift.execution.ExecutionException.prependMessage(ExecutionException.java:63) > at org.arquillian.spacelift.execution.impl.FutureBasedExecution.unwrapException(FutureBasedExecution.java:71) > at org.arquillian.spacelift.execution.impl.FutureBasedExecution.await(FutureBasedExecution.java:130) > at org.jboss.arquillian.drone.webdriver.binary.BinaryFilesUtils.extract(BinaryFilesUtils.java:58) > at org.jboss.arquillian.drone.webdriver.binary.handler.PhantomJSDriverBinaryHandler.prepare(PhantomJSDriverBinaryHandler.java:43) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:226) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:208) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:175) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:60) > ... 12 more > Caused by: java.io.FileNotFoundException: target/drone/1c947d57fce2f21ce0b43fe2ed7cd361/phantomjs-2.1.1-linux-x86_64/examples/colorwheel.js (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.(FileOutputStream.java:213) > at java.io.FileOutputStream.(FileOutputStream.java:162) > at org.arquillian.spacelift.task.archive.UncompressTool.process(UncompressTool.java:118) > at org.arquillian.spacelift.task.archive.UncompressTool.process(UncompressTool.java:36) > at org.arquillian.spacelift.task.Task.run(Task.java:100) > at org.arquillian.spacelift.task.Task$1.call(Task.java:71) > ... 4 more > {code} > I don't know how this usecase is specified in the requirements specification. If it's unspecified, maybe there's a way to make both invokations of Maven in the project and its parent or aggregator work. In case this is not supported it'd be nice to fail with a clear feedback similar to `the invokation of Maven has to take place in the project containing the Arquillian @Deployment method, see [documentation link] for an explanation` since it took me for example several days and 100 stackoverflow bounty points to figure out what the exception above is meaning. > I provided https://gitlab.com/krichter/gitlab-ci-file-creation-aggregator/ referencing https://gitlab.com/krichter/gitlab-ci-file-creation as module which demonstrates the issue, e.g. at https://gitlab.com/krichter/gitlab-ci-file-creation-aggregator/-/jobs/40825021. It performs the compilation skipping integration tests and then runs `mvn verify` in the submodule's directory which succeeds and then in the aggregator directory which fails (see `.gitlab-ci.yml`). The essence of these three calls is to invoke `mvn install` in the aggregator directory which should succeed, but doesn't. > I asked https://stackoverflow.com/questions/47217087/why-does-my-arquillian-drone-functional-test-not-work-on-gitlab-ci for support which might contain more details. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 16:55:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 16:55:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2154) phantomjs download and extraction remains without effect if Maven is started in a parent or aggregator project In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2154. ------------------------------- Resolution: Done > phantomjs download and extraction remains without effect if Maven is started in a parent or aggregator project > -------------------------------------------------------------------------------------------------------------- > > Key: ARQ-2154 > URL: https://issues.jboss.org/browse/ARQ-2154 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.14.Final > Reporter: Karl-Philipp Richter > Assignee: Matous Jobanek > Fix For: drone_2.5.0 > > > Arquillian Spacelift and Arquillian Drone Webdriver don't resolve the directory where to findd the downloaded Selenium driver for phantomjs consistently. They seem to use the working directory which isn't changed if Maven is started in an aggregator project root and the Maven basedir property so that the `@Deployment` method fails due to > {code:java} > java.lang.IllegalStateException: Something bad happened when Drone was trying to download and prepare a binary. For more information see the cause. > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:62) > at org.jboss.arquillian.drone.webdriver.factory.PhantomJSDriverFactory.getCapabilities(PhantomJSDriverFactory.java:99) > at org.jboss.arquillian.drone.webdriver.factory.PhantomJSDriverFactory.createInstance(PhantomJSDriverFactory.java:72) > at org.jboss.arquillian.drone.webdriver.factory.PhantomJSDriverFactory.createInstance(PhantomJSDriverFactory.java:37) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) > at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) > at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) > at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:88) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.arquillian.spacelift.execution.ExecutionException: Execution of a task failed. Unable to execute task UntarTool > at org.arquillian.spacelift.execution.ExecutionException.prependMessage(ExecutionException.java:63) > at org.arquillian.spacelift.execution.impl.FutureBasedExecution.unwrapException(FutureBasedExecution.java:71) > at org.arquillian.spacelift.execution.impl.FutureBasedExecution.await(FutureBasedExecution.java:130) > at org.jboss.arquillian.drone.webdriver.binary.BinaryFilesUtils.extract(BinaryFilesUtils.java:58) > at org.jboss.arquillian.drone.webdriver.binary.handler.PhantomJSDriverBinaryHandler.prepare(PhantomJSDriverBinaryHandler.java:43) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:226) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:208) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:175) > at org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:60) > ... 12 more > Caused by: java.io.FileNotFoundException: target/drone/1c947d57fce2f21ce0b43fe2ed7cd361/phantomjs-2.1.1-linux-x86_64/examples/colorwheel.js (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.(FileOutputStream.java:213) > at java.io.FileOutputStream.(FileOutputStream.java:162) > at org.arquillian.spacelift.task.archive.UncompressTool.process(UncompressTool.java:118) > at org.arquillian.spacelift.task.archive.UncompressTool.process(UncompressTool.java:36) > at org.arquillian.spacelift.task.Task.run(Task.java:100) > at org.arquillian.spacelift.task.Task$1.call(Task.java:71) > ... 4 more > {code} > I don't know how this usecase is specified in the requirements specification. If it's unspecified, maybe there's a way to make both invokations of Maven in the project and its parent or aggregator work. In case this is not supported it'd be nice to fail with a clear feedback similar to `the invokation of Maven has to take place in the project containing the Arquillian @Deployment method, see [documentation link] for an explanation` since it took me for example several days and 100 stackoverflow bounty points to figure out what the exception above is meaning. > I provided https://gitlab.com/krichter/gitlab-ci-file-creation-aggregator/ referencing https://gitlab.com/krichter/gitlab-ci-file-creation as module which demonstrates the issue, e.g. at https://gitlab.com/krichter/gitlab-ci-file-creation-aggregator/-/jobs/40825021. It performs the compilation skipping integration tests and then runs `mvn verify` in the submodule's directory which succeeds and then in the aggregator directory which fails (see `.gitlab-ci.yml`). The essence of these three calls is to invoke `mvn install` in the aggregator directory which should succeed, but doesn't. > I asked https://stackoverflow.com/questions/47217087/why-does-my-arquillian-drone-functional-test-not-work-on-gitlab-ci for support which might contain more details. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 16:56:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 16:56:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2159) Update Arquillian core to 1.1.15.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2159. ------------------------------- Resolution: Done > Update Arquillian core to 1.1.15.Final > -------------------------------------- > > Key: ARQ-2159 > URL: https://issues.jboss.org/browse/ARQ-2159 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.4.5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.5.0 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 16:56:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 16:56:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2160) Upgrade to Selenium 3.8.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2160. ------------------------------- Resolution: Done > Upgrade to Selenium 3.8.0 > ------------------------- > > Key: ARQ-2160 > URL: https://issues.jboss.org/browse/ARQ-2160 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.4.5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.5.0 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 16:56:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 16:56:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2161) Update HtmlUnit driver to 2.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2161. ------------------------------- Resolution: Done > Update HtmlUnit driver to 2.28 > ------------------------------ > > Key: ARQ-2161 > URL: https://issues.jboss.org/browse/ARQ-2161 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.4.5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.5.0 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 16:56:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 16:56:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2163) SessionNotCreatedException when running PhantomJS as remotewebdriver with Selenium 3.8.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2163. ------------------------------- Resolution: Done > SessionNotCreatedException when running PhantomJS as remotewebdriver with Selenium 3.8.0 > ---------------------------------------------------------------------------------------- > > Key: ARQ-2163 > URL: https://issues.jboss.org/browse/ARQ-2163 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.4.5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.5.0 > > > When running test with PhantomJS as a remote webdriver, and selenium server 3.8.0 the SessionNotCreatedException is thrown: > {noformat} > INFO: Running Selenium server process: java -Dphantomjs.binary.path=/home/mjobanek/arquillian/arquillian-extension-drone/drone-webdriver/target/drone/1c947d57fce2f21ce0b43fe2ed7cd361/phantomjs-2.1.1-linux-x86_64/bin/phantomjs -jar target/drone/ef4afb633c4a177144798c17036e2e64/selenium-server-standalone-3.8.0.jar -port 4444 > Dec 04, 2017 1:24:05 PM org.arquillian.spacelift.Spacelift$SpaceliftInstance > INFO: Initialized Spacelift from defaults, workspace: /home/mjobanek/arquillian/arquillian-extension-drone/drone-webdriver, cache: /home/mjobanek/.spacelift/cache > [Selenium server] 13:24:05.716 INFO - Selenium build info: version: '3.8.0', revision: '924c4067df' > [Selenium server] 13:24:05.717 INFO - Launching a standalone Selenium Server > [Selenium server] 2017-12-04 13:24:05.782:INFO::main: Logging initialized @244ms to org.seleniumhq.jetty9.util.log.StdErrLog > [Selenium server] 13:24:05.811 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` > [Selenium server] 13:24:05.824 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` > [Selenium server] 13:24:05.826 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()` > [Selenium server] 13:24:05.827 INFO - Driver class not found: com.opera.core.systems.OperaDriver > [Selenium server] 13:24:05.827 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()` > [Selenium server] 13:24:05.827 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` > [Selenium server] 13:24:05.828 INFO - Driver class not found: org.openqa.selenium.phantomjs.PhantomJSDriver > [Selenium server] 13:24:05.857 INFO - Driver provider class org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: > [Selenium server] registration capabilities Capabilities {browserName: internet explorer, ensureCleanSession: true, platform: WINDOWS, version: } does not match the current platform LINUX > [Selenium server] 13:24:05.857 INFO - Driver provider class org.openqa.selenium.edge.EdgeDriver registration is skipped: > [Selenium server] registration capabilities Capabilities {browserName: MicrosoftEdge, platform: WINDOWS, version: } does not match the current platform LINUX > [Selenium server] 13:24:05.858 INFO - Driver provider class org.openqa.selenium.safari.SafariDriver registration is skipped: > [Selenium server] registration capabilities Capabilities {browserName: safari, platform: MAC, version: } does not match the current platform LINUX > [Selenium server] 13:24:05.887 INFO - Using `new ChromeOptions()` is preferred to `DesiredCapabilities.chrome()` > [Selenium server] 13:24:05.888 INFO - Using `new EdgeOptions()` is preferred to `DesiredCapabilities.edge()` > [Selenium server] 13:24:05.888 INFO - Using `new FirefoxOptions()` is preferred to `DesiredCapabilities.firefox()` > [Selenium server] 13:24:05.888 INFO - Using `new OperaOptions()` is preferred to `DesiredCapabilities.operaBlink()` > [Selenium server] 13:24:05.888 INFO - Using `new SafariOptions()` is preferred to `DesiredCapabilities.safari()` > [Selenium server] 13:24:05.895 INFO - Using the passthrough mode handler > [Selenium server] 2017-12-04 13:24:05.917:INFO:osjs.Server:main: jetty-9.4.7.v20170914 > [Selenium server] 2017-12-04 13:24:05.942:WARN:osjs.SecurityHandler:main: ServletContext at o.s.j.s.ServletContextHandler@2db7a79b{/,null,STARTING} has uncovered http methods for path: / > [Selenium server] 2017-12-04 13:24:05.945:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler at 2db7a79b{/,null,AVAILABLE} > [Selenium server] 2017-12-04 13:24:05.960:INFO:osjs.AbstractConnector:main: Started ServerConnector at 54b45561{HTTP/1.1,[http/1.1]}{0.0.0.0:4444} > [Selenium server] 2017-12-04 13:24:05.961:INFO:osjs.Server:main: Started @423ms > [Selenium server] 13:24:05.961 INFO - Selenium Server is up and running > [Selenium server] 2017-12-04 13:24:06.350:INFO:osjshC.ROOT:qtp1612799726-14: org.openqa.selenium.remote.server.WebDriverServlet-6895a785: Initialising WebDriverServlet > [Selenium server] 13:24:06.379 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.NoSessionHandler at 35178a93 > [Selenium server] 13:24:06.381 INFO - /session/3f6b96b0-d8e7-11e7-8b89-71db65b1fafa/url: Executing GET on /session/3f6b96b0-d8e7-11e7-8b89-71db65b1fafa/url (handler: NoSessionHandler) > Dec 04, 2017 1:24:06 PM org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory createReusableDriver > WARNING: Unable to reuse session: 3f6b96b0-d8e7-11e7-8b89-71db65b1fafa > [Selenium server] 13:24:06.525 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.BeginSession at 7a9815d3 > [Selenium server] 13:24:06.525 INFO - /session: Executing POST on /session (handler: BeginSession) > [Selenium server] 13:24:06.572 INFO - Capabilities are: Capabilities {acceptSslCerts: true, browserName: phantomjs, firefoxUserPreferences: target/test-classes/prefs.js, loggingPrefs: org.openqa.selenium.logging..., seleniumServerVersion: 3.8.0, version: , webStorageEnabled: true, webdriver.firefox.profile: selenium} > [Selenium server] 13:24:06.577 INFO - Capabilities are: Capabilities {browserName: phantomjs} > [Selenium server] 13:24:06.578 INFO - Using default factory: org.openqa.selenium.chrome.ChromeDriverService > org.openqa.selenium.SessionNotCreatedException: Unable to create new service: ChromeDriverService > Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:37:19.049Z' > System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' > Driver info: driver.version: unknown > Command duration or timeout: 82 milliseconds > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214) > at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166) > at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53) > at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91) > at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:123) > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) > at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958) > at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) > at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464) > at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:126) > at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:73) > at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142) > at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601) > at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:219) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:142) > at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:155) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createRemoteDriver(RemoteWebDriverFactory.java:220) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createReusableDriver(RemoteWebDriverFactory.java:248) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:131) > at org.jboss.arquillian.drone.webdriver.factory.RemoteWebDriverFactory.createInstance(RemoteWebDriverFactory.java:56) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) > at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) > at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) > at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) > at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:89) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.openqa.selenium.SessionNotCreatedException: Unable to create new service: ChromeDriverService > Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:37:19.049Z' > System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' > Driver info: driver.version: unknown > Build info: version: '3.8.0', revision: '924c4067df', time: '2017-11-30T11:20:39.408Z' > System info: host: 'dhcp-10-40-5-169.brq.redhat.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.12-100.fc24.x86_64', java.version: '1.8.0_101' > Driver info: driver.version: unknown > at org.openqa.selenium.remote.server.ServicedSession$Factory.lambda$get$0(ServicedSession.java:208) > at org.openqa.selenium.remote.server.ServicedSession$Factory.apply(ServicedSession.java:218) > at org.openqa.selenium.remote.server.DefaultPipeline.lambda$null$1(DefaultPipeline.java:59) > at org.openqa.selenium.remote.server.NewSessionPipeline.lambda$createNewSession$4(NewSessionPipeline.java:52) > at java.util.Optional.orElseGet(Optional.java:267) > at org.openqa.selenium.remote.server.NewSessionPipeline.createNewSession(NewSessionPipeline.java:51) > at org.openqa.selenium.remote.server.commandhandler.BeginSession.execute(BeginSession.java:77) > at org.openqa.selenium.remote.server.WebDriverServlet.lambda$handle$0(WebDriverServlet.java:240) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ... 4 more > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 12 16:56:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 12 Dec 2017 16:56:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2167) Upgrade to Selenium 3.8.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2167. ------------------------------- Resolution: Done > Upgrade to Selenium 3.8.1 > ------------------------- > > Key: ARQ-2167 > URL: https://issues.jboss.org/browse/ARQ-2167 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.4.5 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.5.0 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 19 04:02:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Tue, 19 Dec 2017 04:02:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2168) Create a repeat method in Rest API In-Reply-To: References: Message-ID: Alex Soto created ARQ-2168: ------------------------------ Summary: Create a repeat method in Rest API Key: ARQ-2168 URL: https://issues.jboss.org/browse/ARQ-2168 Project: Arquillian Issue Type: Enhancement Components: Extension - Persistence Reporter: Alex Soto Assignee: Bartosz Majsak Priority: Minor Create a `repeat` method in Rest API so you can define one file and execute automatically several times. This might be useful for testing circuit breaker things. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 19 12:15:00 2017 From: issues at jboss.org (Charles Tian (JIRA)) Date: Tue, 19 Dec 2017 12:15:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2162) New release for wlp-managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507209#comment-13507209 ] Charles Tian commented on ARQ-2162: ----------------------------------- I've created a PR with my changes here: https://github.com/arquillian/arquillian-container-was/pull/34 We'd like for these changes, as well as those that are still in progress in PR #33 to go in before the new release is made. Also, can we upgrade the release version to something like 1.0.0.Final from 1.0.0.Beta2 to indicate that the new version is not a beta release? Thanks. > New release for wlp-managed container > ------------------------------------- > > Key: ARQ-2162 > URL: https://issues.jboss.org/browse/ARQ-2162 > Project: Arquillian > Issue Type: Release > Components: WebSphere Containers > Reporter: Charles Tian > Assignee: Aslak Knutsen > > I'm a developer at IBM currently working on some updates for the Arquillian WLP managed container. I have some improvements which I'm planning to push out in the next couple of weeks. > Once these changed get reviewed and merged, could we make a new release for the WLP managed container on Maven Central? The current version is 1.0.0.Beta2 and was released almost three years ago (Jan. 2015). Since then, there have been many updates made to the container (including the changes that I will be providing) that are not part of any release. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 19 12:17:00 2017 From: issues at jboss.org (Charles Tian (JIRA)) Date: Tue, 19 Dec 2017 12:17:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2162) New release for wlp-managed container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Tian updated ARQ-2162: ------------------------------ Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/34 > New release for wlp-managed container > ------------------------------------- > > Key: ARQ-2162 > URL: https://issues.jboss.org/browse/ARQ-2162 > Project: Arquillian > Issue Type: Release > Components: WebSphere Containers > Reporter: Charles Tian > Assignee: Aslak Knutsen > > I'm a developer at IBM currently working on some updates for the Arquillian WLP managed container. I have some improvements which I'm planning to push out in the next couple of weeks. > Once these changed get reviewed and merged, could we make a new release for the WLP managed container on Maven Central? The current version is 1.0.0.Beta2 and was released almost three years ago (Jan. 2015). Since then, there have been many updates made to the container (including the changes that I will be providing) that are not part of any release. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Dec 19 12:18:00 2017 From: issues at jboss.org (Charles Tian (JIRA)) Date: Tue, 19 Dec 2017 12:18:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2162) New release for wlp-managed container (with support for multi-app verification before test app deployment) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Tian updated ARQ-2162: ------------------------------ Summary: New release for wlp-managed container (with support for multi-app verification before test app deployment) (was: New release for wlp-managed container) > New release for wlp-managed container (with support for multi-app verification before test app deployment) > ---------------------------------------------------------------------------------------------------------- > > Key: ARQ-2162 > URL: https://issues.jboss.org/browse/ARQ-2162 > Project: Arquillian > Issue Type: Release > Components: WebSphere Containers > Reporter: Charles Tian > Assignee: Aslak Knutsen > > I'm a developer at IBM currently working on some updates for the Arquillian WLP managed container. I have some improvements which I'm planning to push out in the next couple of weeks. > Once these changed get reviewed and merged, could we make a new release for the WLP managed container on Maven Central? The current version is 1.0.0.Beta2 and was released almost three years ago (Jan. 2015). Since then, there have been many updates made to the container (including the changes that I will be providing) that are not part of any release. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 08:06:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 20 Dec 2017 08:06:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1828) Replace Testrunner with a JUnit-Rule In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1828: -------------------------------- Fix Version/s: 1.2.0.Final > Replace Testrunner with a JUnit-Rule > ------------------------------------ > > Key: ARQ-1828 > URL: https://issues.jboss.org/browse/ARQ-1828 > Project: Arquillian > Issue Type: Feature Request > Reporter: Niels Niels > Fix For: 1.2.0.Final > > > At the moment all tests must run with > @RunWith(Arquillian.class) > This makes trouble if you need a runner with add or remove tests like Parameterized. I can't see what Arquillian.class do which can not be done with a JUnit-Rule. JUnit-Rules can be easily combined. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 08:06:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 20 Dec 2017 08:06:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1828) Replace Testrunner with a JUnit-Rule In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1828: -------------------------------- Component/s: Base Implementation > Replace Testrunner with a JUnit-Rule > ------------------------------------ > > Key: ARQ-1828 > URL: https://issues.jboss.org/browse/ARQ-1828 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Niels Niels > Fix For: 1.2.0.Final > > > At the moment all tests must run with > @RunWith(Arquillian.class) > This makes trouble if you need a runner with add or remove tests like Parameterized. I can't see what Arquillian.class do which can not be done with a JUnit-Rule. JUnit-Rules can be easily combined. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 10:14:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 20 Dec 2017 10:14:01 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1828) Replace Testrunner with a JUnit-Rule In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1828: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/147 > Replace Testrunner with a JUnit-Rule > ------------------------------------ > > Key: ARQ-1828 > URL: https://issues.jboss.org/browse/ARQ-1828 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Niels Niels > Fix For: 1.2.0.Final > > > At the moment all tests must run with > @RunWith(Arquillian.class) > This makes trouble if you need a runner with add or remove tests like Parameterized. I can't see what Arquillian.class do which can not be done with a JUnit-Rule. JUnit-Rules can be easily combined. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 10:15:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 20 Dec 2017 10:15:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1828) Replace Testrunner with a JUnit-Rule In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak reassigned ARQ-1828: ----------------------------------- Assignee: Dipak Pawar > Replace Testrunner with a JUnit-Rule > ------------------------------------ > > Key: ARQ-1828 > URL: https://issues.jboss.org/browse/ARQ-1828 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Niels Niels > Assignee: Dipak Pawar > Fix For: 1.2.0.Final > > > At the moment all tests must run with > @RunWith(Arquillian.class) > This makes trouble if you need a runner with add or remove tests like Parameterized. I can't see what Arquillian.class do which can not be done with a JUnit-Rule. JUnit-Rules can be easily combined. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 10:15:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 20 Dec 2017 10:15:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1828) Replace Testrunner with a JUnit-Rule In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1828: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Replace Testrunner with a JUnit-Rule > ------------------------------------ > > Key: ARQ-1828 > URL: https://issues.jboss.org/browse/ARQ-1828 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Niels Niels > Assignee: Dipak Pawar > Fix For: 1.2.0.Final > > > At the moment all tests must run with > @RunWith(Arquillian.class) > This makes trouble if you need a runner with add or remove tests like Parameterized. I can't see what Arquillian.class do which can not be done with a JUnit-Rule. JUnit-Rules can be easily combined. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 10:17:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Wed, 20 Dec 2017 10:17:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1828) Replace Testrunner with a JUnit-Rule In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507516#comment-13507516 ] Bartosz Majsak commented on ARQ-1828: ------------------------------------- We haven't replaced it but shipped rules as an alternative to the runner. 1.2.0.Final should hit Maven Central pretty soon. You can read all about it here http://arquillian.org/arquillian-core/#_rules > Replace Testrunner with a JUnit-Rule > ------------------------------------ > > Key: ARQ-1828 > URL: https://issues.jboss.org/browse/ARQ-1828 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Reporter: Niels Niels > Assignee: Dipak Pawar > Fix For: 1.2.0.Final > > > At the moment all tests must run with > @RunWith(Arquillian.class) > This makes trouble if you need a runner with add or remove tests like Parameterized. I can't see what Arquillian.class do which can not be done with a JUnit-Rule. JUnit-Rules can be easily combined. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 10:44:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 20 Dec 2017 10:44:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2148) Add support for automatically loading Boot and JPA files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto updated ARQ-2148: --------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Upstream 2cefa2d5d01bcc20d465eda4e881f6d8edb3e0ed https://github.com/arquillian/arquillian-extension-persistence/pull/95 > Add support for automatically loading Boot and JPA files > -------------------------------------------------------- > > Key: ARQ-2148 > URL: https://issues.jboss.org/browse/ARQ-2148 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > > Currently in APE 2.0.0 when using programmatic way you need to set over and over again. > It will be great if you could use the information configured at `application.properties` (Spring Boot) or `persistence.xml` (JPA) to configure the connection. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Dec 20 10:44:00 2017 From: issues at jboss.org (Alex Soto (JIRA)) Date: Wed, 20 Dec 2017 10:44:00 -0500 (EST) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2148) Add support for automatically loading Boot and JPA files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Soto closed ARQ-2148. -------------------------- > Add support for automatically loading Boot and JPA files > -------------------------------------------------------- > > Key: ARQ-2148 > URL: https://issues.jboss.org/browse/ARQ-2148 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Persistence > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > > Currently in APE 2.0.0 when using programmatic way you need to set over and over again. > It will be great if you could use the information configured at `application.properties` (Spring Boot) or `persistence.xml` (JPA) to configure the connection. -- This message was sent by Atlassian JIRA (v7.5.0#75005)