From issues at jboss.org Tue Jul 4 09:14:00 2017 From: issues at jboss.org (Vaclav Muzikar (JIRA)) Date: Tue, 4 Jul 2017 09:14:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2038) Create Drone extension for Appium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaclav Muzikar updated ARQ-2038: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/101 > Create Drone extension for Appium > --------------------------------- > > Key: ARQ-2038 > URL: https://issues.jboss.org/browse/ARQ-2038 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: vinoth selvaraj > Assignee: Vaclav Muzikar > > Appium is becoming an industry standard for mobile testing. Many large companies like Amazon, Zameron, Perfecto Mobile and others decided to put Appium into their clouds. Appium supports both andriod and ios automation. It would be nice to have a drone-extension for Appium. > More Info on appium: > *https://github.com/appium/appium* -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:02:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1383) Support deployment of container wide resource.xml in GlassFish Managed and Remote In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-1383: -------------------------------- Fix Version/s: (was: glassfish_1.0.0.Final) > Support deployment of container wide resource.xml in GlassFish Managed and Remote > ---------------------------------------------------------------------------------- > > Key: ARQ-1383 > URL: https://issues.jboss.org/browse/ARQ-1383 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Reporter: Aslak Knutsen > > As a User I would like to deploy Container wide resources > Given a Reference to a resource.xml file in ContainerConfiguration > When the Container starts up > Then the resource.xml should be deployed > When the Container shuts down > Then the resource.xml should be undeployed > This is similar to how GlassFish Embedded works. > Configuration: https://github.com/arquillian/arquillian-container-glassfish/blob/master/glassfish-embedded-3.1/src/main/java/org/jboss/arquillian/container/glassfish/embedded_3_1/GlassFishConfiguration.java#L156 > Container Impl: https://github.com/arquillian/arquillian-container-glassfish/blob/master/glassfish-embedded-3.1/src/main/java/org/jboss/arquillian/container/glassfish/embedded_3_1/GlassFishContainer.java#L186 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:02:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:02:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-489) Support Descriptor deployment GlassFish containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-489: ------------------------------- Fix Version/s: (was: glassfish_1.0.0.Final) > Support Descriptor deployment GlassFish containers > -------------------------------------------------- > > Key: ARQ-489 > URL: https://issues.jboss.org/browse/ARQ-489 > Project: Arquillian > Issue Type: Feature Request > Components: GlassFish Containers > Affects Versions: 1.0.0.Alpha5 > Reporter: Aslak Knutsen > Labels: community_contribution > > sunResourceXML support be added as Descriptor Deployment support (resourceXML pr testclass). > GlassFish support adding a resource.xml in one go, but the resources must be individual removed. Need to parse the xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:04:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2123) Support for starting derby database automatically In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2123: ----------------------------------- Summary: Support for starting derby database automatically Key: ARQ-2123 URL: https://issues.jboss.org/browse/ARQ-2123 Project: Arquillian Issue Type: Enhancement Components: GlassFish Containers Reporter: Bartosz Majsak -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:04:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:04:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2123) Support for starting derby database automatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2123: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-glassfish/pull/34 > Support for starting derby database automatically > ------------------------------------------------- > > Key: ARQ-2123 > URL: https://issues.jboss.org/browse/ARQ-2123 > Project: Arquillian > Issue Type: Enhancement > Components: GlassFish Containers > Reporter: Bartosz Majsak > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:05:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:05:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2123) Support for starting derby database automatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2123: -------------------------------- Description: t would be very handy to let the derby database start automatically (on demand) in the managed environment. I was forced to bump the glassfish version used for testing from 4.0-b72 to 4.1.1. This was due to a bug that refused me to start the derby database failing with this error: {{AccessControlException: access denied ("java.net.SocketPermission" "localhost:1527" "listen,resolve")}} The configuration option in the arquillian.xml is startDerby = true/false Generally glassfish 3 has exactly the same feature. The error is the bug that I've mentioned in the initial comment. You can see more output be dafining outputToConcoleto true. Here are more details about the bug in glassfish: https://java.net/jira/browse/GLASSFISH-21004 and the root cause form the bundled derby https://issues.apache.org/jira/browse/DERBY-6438 > Support for starting derby database automatically > ------------------------------------------------- > > Key: ARQ-2123 > URL: https://issues.jboss.org/browse/ARQ-2123 > Project: Arquillian > Issue Type: Enhancement > Components: GlassFish Containers > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.0.Final > > > t would be very handy to let the derby database start automatically (on demand) in the managed environment. > I was forced to bump the glassfish version used for testing from 4.0-b72 to 4.1.1. This was due to a bug that refused me to start the derby database failing with this error: > {{AccessControlException: access denied ("java.net.SocketPermission" "localhost:1527" "listen,resolve")}} > The configuration option in the arquillian.xml is startDerby = true/false > Generally glassfish 3 has exactly the same feature. The error is the bug that I've mentioned in the initial comment. You can see more output be dafining outputToConcoleto true. Here are more details about the bug in glassfish: > https://java.net/jira/browse/GLASSFISH-21004 > and the root cause form the bundled derby > https://issues.apache.org/jira/browse/DERBY-6438 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:05:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:05:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2123) Support for starting derby database automatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2123: -------------------------------- Fix Version/s: glassfish_1.0.0.Final > Support for starting derby database automatically > ------------------------------------------------- > > Key: ARQ-2123 > URL: https://issues.jboss.org/browse/ARQ-2123 > Project: Arquillian > Issue Type: Enhancement > Components: GlassFish Containers > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.0.Final > > > t would be very handy to let the derby database start automatically (on demand) in the managed environment. > I was forced to bump the glassfish version used for testing from 4.0-b72 to 4.1.1. This was due to a bug that refused me to start the derby database failing with this error: > {{AccessControlException: access denied ("java.net.SocketPermission" "localhost:1527" "listen,resolve")}} > The configuration option in the arquillian.xml is startDerby = true/false > Generally glassfish 3 has exactly the same feature. The error is the bug that I've mentioned in the initial comment. You can see more output be dafining outputToConcoleto true. Here are more details about the bug in glassfish: > https://java.net/jira/browse/GLASSFISH-21004 > and the root cause form the bundled derby > https://issues.apache.org/jira/browse/DERBY-6438 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:06:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2123) Support for starting derby database automatically In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2123: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Support for starting derby database automatically > ------------------------------------------------- > > Key: ARQ-2123 > URL: https://issues.jboss.org/browse/ARQ-2123 > Project: Arquillian > Issue Type: Enhancement > Components: GlassFish Containers > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.0.Final > > > t would be very handy to let the derby database start automatically (on demand) in the managed environment. > I was forced to bump the glassfish version used for testing from 4.0-b72 to 4.1.1. This was due to a bug that refused me to start the derby database failing with this error: > {{AccessControlException: access denied ("java.net.SocketPermission" "localhost:1527" "listen,resolve")}} > The configuration option in the arquillian.xml is startDerby = true/false > Generally glassfish 3 has exactly the same feature. The error is the bug that I've mentioned in the initial comment. You can see more output be dafining outputToConcoleto true. Here are more details about the bug in glassfish: > https://java.net/jira/browse/GLASSFISH-21004 > and the root cause form the bundled derby > https://issues.apache.org/jira/browse/DERBY-6438 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:07:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:07:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2124) Proper way of passing arguments to glassfish cli In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2124: ----------------------------------- Summary: Proper way of passing arguments to glassfish cli Key: ARQ-2124 URL: https://issues.jboss.org/browse/ARQ-2124 Project: Arquillian Issue Type: Bug Components: GlassFish Containers Affects Versions: glassfish_1.0.0.Final Reporter: Bartosz Majsak Replace the empty list implementation with a full list implementation to remove the unsupported operation exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:07:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:07:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2124) Proper way of passing arguments to glassfish cli In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2124: -------------------------------- Fix Version/s: glassfish_1.0.1 > Proper way of passing arguments to glassfish cli > ------------------------------------------------ > > Key: ARQ-2124 > URL: https://issues.jboss.org/browse/ARQ-2124 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.Final > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.1 > > > Replace the empty list implementation with a full list implementation to remove > the unsupported operation exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:07:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:07:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2124) Proper way of passing arguments to glassfish cli In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2124: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-glassfish/pull/35 > Proper way of passing arguments to glassfish cli > ------------------------------------------------ > > Key: ARQ-2124 > URL: https://issues.jboss.org/browse/ARQ-2124 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.Final > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.1 > > > Replace the empty list implementation with a full list implementation to remove > the unsupported operation exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:08:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:08:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2124) Proper way of passing arguments to glassfish cli In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2124: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Proper way of passing arguments to glassfish cli > ------------------------------------------------ > > Key: ARQ-2124 > URL: https://issues.jboss.org/browse/ARQ-2124 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.Final > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.1 > > > Replace the empty list implementation with a full list implementation to remove > the unsupported operation exceptions. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:08:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:08:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2125) Adding wait option for Glassfish container In-Reply-To: References: Message-ID: Bartosz Majsak created ARQ-2125: ----------------------------------- Summary: Adding wait option for Glassfish container Key: ARQ-2125 URL: https://issues.jboss.org/browse/ARQ-2125 Project: Arquillian Issue Type: Bug Components: GlassFish Containers Affects Versions: glassfish_1.0.0.Final Reporter: Bartosz Majsak It seems arquillian conatiner is looking for glassfish even before glassfish has started properly. Adding some wait time to resolve the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:09:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:09:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2125) Adding wait option for Glassfish container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2125: -------------------------------- Fix Version/s: glassfish_1.0.1 > Adding wait option for Glassfish container > ------------------------------------------ > > Key: ARQ-2125 > URL: https://issues.jboss.org/browse/ARQ-2125 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.Final > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.1 > > > It seems arquillian conatiner is looking for glassfish even before glassfish has started properly. > Adding some wait time to resolve the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:09:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:09:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2125) Adding wait option for Glassfish container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2125: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-glassfish/pull/38 > Adding wait option for Glassfish container > ------------------------------------------ > > Key: ARQ-2125 > URL: https://issues.jboss.org/browse/ARQ-2125 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.Final > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.1 > > > It seems arquillian conatiner is looking for glassfish even before glassfish has started properly. > Adding some wait time to resolve the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Sat Jul 8 05:09:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Sat, 8 Jul 2017 05:09:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2125) Adding wait option for Glassfish container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bartosz Majsak updated ARQ-2125: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Adding wait option for Glassfish container > ------------------------------------------ > > Key: ARQ-2125 > URL: https://issues.jboss.org/browse/ARQ-2125 > Project: Arquillian > Issue Type: Bug > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.Final > Reporter: Bartosz Majsak > Fix For: glassfish_1.0.1 > > > It seems arquillian conatiner is looking for glassfish even before glassfish has started properly. > Adding some wait time to resolve the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 10 04:51:00 2017 From: issues at jboss.org (Falko Modler (JIRA)) Date: Mon, 10 Jul 2017 04:51:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1949) Memory leak in DeploymentContextImpl.stores In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Falko Modler resolved ARQ-1949. ------------------------------- Resolution: Out of Date Closing this as I cannot reproduce the leak anymore on 1.1.13.Final. Probably fixed in 1.1.10.Final via ARQ-1992. > Memory leak in DeploymentContextImpl.stores > ------------------------------------------- > > Key: ARQ-1949 > URL: https://issues.jboss.org/browse/ARQ-1949 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.1.3.Final, 1.1.7.Final > Environment: Java 1.7.0_80 > Maven 3.2.5 > Surefire-Plugin 2.18.1 > Windows7 x64 and CentOS 6.5 > Reporter: Falko Modler > > The {{Deployment}} (which also holds the {{Archive}}) for each test class is added to {{DeploymentContextImpl.stores}}. A {{Deployment}} is deactivated properly but it is *not* getting removed until the {{Manager}} shuts down. > This can easily blow the heap of the executing JVM in case you have *many* test classes and/or *large* archives to deploy. > In our environment the JVM forked by maven surefire dies with an OOM after just ~20 test classes. Xmx is set to 512m. > PS: Another user came across this problem too: https://developer.jboss.org/thread/250124 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 12 04:29:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 12 Jul 2017 04:29:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2126) Drone sets the size twice when a DroneInstanceEnhancer is used In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2126: ----------------------------------- Summary: Drone sets the size twice when a DroneInstanceEnhancer is used Key: ARQ-2126 URL: https://issues.jboss.org/browse/ARQ-2126 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.2.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.3.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 12 04:31:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 12 Jul 2017 04:31:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2126) Drone sets the size twice when a DroneInstanceEnhancer is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2126: -------------------------------- Description: Drone sets the size twice when a DroneInstanceEnhancer is used which can cause unexpected behavior and delay > Drone sets the size twice when a DroneInstanceEnhancer is used > -------------------------------------------------------------- > > Key: ARQ-2126 > URL: https://issues.jboss.org/browse/ARQ-2126 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.0 > > > Drone sets the size twice when a DroneInstanceEnhancer is used which can cause unexpected behavior and delay -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 12 04:31:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 12 Jul 2017 04:31:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2126) Drone sets the size twice when a DroneInstanceEnhancer is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2126: -------------------------------- Forum Reference: https://github.com/arquillian/arquillian-extension-drone/issues/100 > Drone sets the size twice when a DroneInstanceEnhancer is used > -------------------------------------------------------------- > > Key: ARQ-2126 > URL: https://issues.jboss.org/browse/ARQ-2126 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.0 > > > Drone sets the size twice when a DroneInstanceEnhancer is used which can cause unexpected behavior and delay -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 12 06:27:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 12 Jul 2017 06:27:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2038) Create Drone extension for Appium In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2038. ------------------------------- Fix Version/s: drone_2.3.0 Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/bf4eaac0e0f3488afa6b841680bde4a174d94934 > Create Drone extension for Appium > --------------------------------- > > Key: ARQ-2038 > URL: https://issues.jboss.org/browse/ARQ-2038 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Reporter: vinoth selvaraj > Assignee: Vaclav Muzikar > Fix For: drone_2.3.0 > > > Appium is becoming an industry standard for mobile testing. Many large companies like Amazon, Zameron, Perfecto Mobile and others decided to put Appium into their clouds. Appium supports both andriod and ios automation. It would be nice to have a drone-extension for Appium. > More Info on appium: > *https://github.com/appium/appium* -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 12 10:57:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 12 Jul 2017 10:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-508) Update cglib to 3.2.5 In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-508: ------------------------------------- Summary: Update cglib to 3.2.5 Key: ARQGRA-508 URL: https://issues.jboss.org/browse/ARQGRA-508 Project: Arquillian Graphene Issue Type: Component Upgrade Affects Versions: 2.2.1 Reporter: Matous Jobanek Fix For: 2.2.2 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 12 11:00:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 12 Jul 2017 11:00:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-508) Update cglib to 3.2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQGRA-508: ------------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/171 Assignee: Dipak Pawar > Update cglib to 3.2.5 > --------------------- > > Key: ARQGRA-508 > URL: https://issues.jboss.org/browse/ARQGRA-508 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 2.2.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 12 11:01:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 12 Jul 2017 11:01:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-508) Update cglib to 3.2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-508. --------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-graphene/commit/ab542e4e6421b48242c304b809de49f74f1201da > Update cglib to 3.2.5 > --------------------- > > Key: ARQGRA-508 > URL: https://issues.jboss.org/browse/ARQGRA-508 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 2.2.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 13 04:20:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 13 Jul 2017 04:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2127) It is not possible to set fullscreen for chromeHeadless In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2127: ----------------------------------- Summary: It is not possible to set fullscreen for chromeHeadless Key: ARQ-2127 URL: https://issues.jboss.org/browse/ARQ-2127 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.2.0 Reporter: Matous Jobanek Assignee: Hemani Katyal Fix For: drone_2.3.0 Some websites and pages are broken if loaded in a browser window that is half the total screen size of the monitor. Resizing chrome is buggy in latest chrome-drivers and explicitly setting the window size when a browser is opened is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 13 04:21:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 13 Jul 2017 04:21:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2127) It is not possible to set fullscreen for chromeHeadless In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2127: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/98 > It is not possible to set fullscreen for chromeHeadless > ------------------------------------------------------- > > Key: ARQ-2127 > URL: https://issues.jboss.org/browse/ARQ-2127 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Hemani Katyal > Fix For: drone_2.3.0 > > > Some websites and pages are broken if loaded in a browser window that is half the total screen size of the monitor. Resizing chrome is buggy in latest chrome-drivers and explicitly setting the window size when a browser is opened is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 13 04:22:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 13 Jul 2017 04:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2127) It is not possible to set fullscreen for chromeHeadless In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-2127: ----------------------------------- Assignee: Matous Jobanek (was: Hemani Katyal) > It is not possible to set fullscreen for chromeHeadless > ------------------------------------------------------- > > Key: ARQ-2127 > URL: https://issues.jboss.org/browse/ARQ-2127 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.0 > > > Some websites and pages are broken if loaded in a browser window that is half the total screen size of the monitor. Resizing chrome is buggy in latest chrome-drivers and explicitly setting the window size when a browser is opened is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 13 04:22:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 13 Jul 2017 04:22:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2127) It is not possible to set fullscreen for chromeHeadless In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQ-2127: ----------------------------------- Assignee: Hemani Katyal (was: Matous Jobanek) > It is not possible to set fullscreen for chromeHeadless > ------------------------------------------------------- > > Key: ARQ-2127 > URL: https://issues.jboss.org/browse/ARQ-2127 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Hemani Katyal > Fix For: drone_2.3.0 > > > Some websites and pages are broken if loaded in a browser window that is half the total screen size of the monitor. Resizing chrome is buggy in latest chrome-drivers and explicitly setting the window size when a browser is opened is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 13 04:22:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 13 Jul 2017 04:22:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2127) It is not possible to set window size for chromeHeadless In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2127: -------------------------------- Summary: It is not possible to set window size for chromeHeadless (was: It is not possible to set fullscreen for chromeHeadless) > It is not possible to set window size for chromeHeadless > -------------------------------------------------------- > > Key: ARQ-2127 > URL: https://issues.jboss.org/browse/ARQ-2127 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Hemani Katyal > Fix For: drone_2.3.0 > > > Some websites and pages are broken if loaded in a browser window that is half the total screen size of the monitor. Resizing chrome is buggy in latest chrome-drivers and explicitly setting the window size when a browser is opened is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 13 04:24:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 13 Jul 2017 04:24:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2127) It is not possible to set window size for chromeHeadless In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2127. ------------------------------- Resolution: Done pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/5c40833654737da59a97c413ae504ca2c86cdbae > It is not possible to set window size for chromeHeadless > -------------------------------------------------------- > > Key: ARQ-2127 > URL: https://issues.jboss.org/browse/ARQ-2127 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Hemani Katyal > Fix For: drone_2.3.0 > > > Some websites and pages are broken if loaded in a browser window that is half the total screen size of the monitor. Resizing chrome is buggy in latest chrome-drivers and explicitly setting the window size when a browser is opened is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 13 05:20:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 13 Jul 2017 05:20:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2126) Drone sets the size twice when a DroneInstanceEnhancer is used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2126. ------------------------------- Resolution: Done pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/b18016683d884812dba735ced76254c3a6f55018 > Drone sets the size twice when a DroneInstanceEnhancer is used > -------------------------------------------------------------- > > Key: ARQ-2126 > URL: https://issues.jboss.org/browse/ARQ-2126 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.2.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.0 > > > Drone sets the size twice when a DroneInstanceEnhancer is used which can cause unexpected behavior and delay -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:56:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-507) Update Arquillian Drone to 2.3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-507: ---------------------------------- Summary: Update Arquillian Drone to 2.3.0 (was: Update Arquillian Drone to 2.1.2) > Update Arquillian Drone to 2.3.0 > -------------------------------- > > Key: ARQGRA-507 > URL: https://issues.jboss.org/browse/ARQGRA-507 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Components: core > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.2.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:57:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-507) Update Arquillian Drone to 2.3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-507: ---------------------------------- Fix Version/s: 2.3.0 (was: 2.2.2) > Update Arquillian Drone to 2.3.0 > -------------------------------- > > Key: ARQGRA-507 > URL: https://issues.jboss.org/browse/ARQGRA-507 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Components: core > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:57:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-501) Error when checking for the invisibility of elements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-501: ---------------------------------- Fix Version/s: 2.3.0 > Error when checking for the invisibility of elements > ---------------------------------------------------- > > Key: ARQGRA-501 > URL: https://issues.jboss.org/browse/ARQGRA-501 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.2.0 > Reporter: Krassimir Valev > Fix For: 2.3.0 > > > I get the following error message, when waiting for an element to disappear: > {code:java} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$3.getTarget(WebElementUtils.java:104) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:189) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:47) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:43) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:43) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208) > at com.sun.proxy.$Proxy316.isDisplayed(Unknown Source) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:585) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:581) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > {code} > The wait condition looks like this: > {code:java} > return waitGui() > .withTimeout(timeout, TimeUnit.SECONDS) > .pollingEvery(100, TimeUnit.MILLISECONDS) > .ignoring(NoSuchElementException.class, StaleElementReferenceException.class) > .ignoring(InvocationTargetException.class) > .until(ExpectedConditions.invisibilityOfElementLocated(locator)); > {code} > The very same condition used to work with graphene-webdriver 2.0.3.Final and selenium-bom 2.50.1, but it fails now after upgrading to graphene-webdriver 2.2.0 and selenium-bom 3.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:57:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-501) Error when checking for the invisibility of elements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQGRA-501: ------------------------------------- Assignee: Matous Jobanek > Error when checking for the invisibility of elements > ---------------------------------------------------- > > Key: ARQGRA-501 > URL: https://issues.jboss.org/browse/ARQGRA-501 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.2.0 > Reporter: Krassimir Valev > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > I get the following error message, when waiting for an element to disappear: > {code:java} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$3.getTarget(WebElementUtils.java:104) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:189) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:47) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:43) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:43) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208) > at com.sun.proxy.$Proxy316.isDisplayed(Unknown Source) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:585) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:581) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > {code} > The wait condition looks like this: > {code:java} > return waitGui() > .withTimeout(timeout, TimeUnit.SECONDS) > .pollingEvery(100, TimeUnit.MILLISECONDS) > .ignoring(NoSuchElementException.class, StaleElementReferenceException.class) > .ignoring(InvocationTargetException.class) > .until(ExpectedConditions.invisibilityOfElementLocated(locator)); > {code} > The very same condition used to work with graphene-webdriver 2.0.3.Final and selenium-bom 2.50.1, but it fails now after upgrading to graphene-webdriver 2.2.0 and selenium-bom 3.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:58:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:58:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQGRA-505: ----------------------------------- > Implement additional API methods for Action operations directly into Graphene class > ----------------------------------------------------------------------------------- > > Key: ARQGRA-505 > URL: https://issues.jboss.org/browse/ARQGRA-505 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > Methods: > - click() > - doubleClick() > - writeIntoElement() > It should be possible just write: > {code:java} > Graphene.writeIntoElement(element, "my text"); > Graphene.doubleClick(element); > Graphene.click(element); > {code} > Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:58:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:58:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-505: ---------------------------------- Fix Version/s: 2.3.0 (was: 2.2.2) > Implement additional API methods for Action operations directly into Graphene class > ----------------------------------------------------------------------------------- > > Key: ARQGRA-505 > URL: https://issues.jboss.org/browse/ARQGRA-505 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > Methods: > - click() > - doubleClick() > - writeIntoElement() > It should be possible just write: > {code:java} > Graphene.writeIntoElement(element, "my text"); > Graphene.doubleClick(element); > Graphene.click(element); > {code} > Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:59:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-505) Implement additional API methods for Action operations directly into Graphene class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-505. --------------------------------- Resolution: Done > Implement additional API methods for Action operations directly into Graphene class > ----------------------------------------------------------------------------------- > > Key: ARQGRA-505 > URL: https://issues.jboss.org/browse/ARQGRA-505 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > Methods: > - click() > - doubleClick() > - writeIntoElement() > It should be possible just write: > {code:java} > Graphene.writeIntoElement(element, "my text"); > Graphene.doubleClick(element); > Graphene.click(element); > {code} > Or invoke it directly on {{GrapheneElement}} class -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:59:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQGRA-504: ----------------------------------- > Implemented a new method "clickable" in wait API > -------------------------------------------------- > > Key: ARQGRA-504 > URL: https://issues.jboss.org/browse/ARQGRA-504 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:59:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-504: ---------------------------------- Fix Version/s: 2.3.0 (was: 2.2.2) > Implemented a new method "clickable" in wait API > -------------------------------------------------- > > Key: ARQGRA-504 > URL: https://issues.jboss.org/browse/ARQGRA-504 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:59:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-508) Update cglib to 3.2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reopened ARQGRA-508: ----------------------------------- > Update cglib to 3.2.5 > --------------------- > > Key: ARQGRA-508 > URL: https://issues.jboss.org/browse/ARQGRA-508 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 2.2.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 03:59:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 03:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-504) Implemented a new method "clickable" in wait API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-504. --------------------------------- Resolution: Done > Implemented a new method "clickable" in wait API > -------------------------------------------------- > > Key: ARQGRA-504 > URL: https://issues.jboss.org/browse/ARQGRA-504 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > It should wait till an element is visible & enabled -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 04:00:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 04:00:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-508) Update cglib to 3.2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-508: ---------------------------------- Fix Version/s: 2.3.0 (was: 2.2.2) > Update cglib to 3.2.5 > --------------------- > > Key: ARQGRA-508 > URL: https://issues.jboss.org/browse/ARQGRA-508 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 2.3.0 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 04:00:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 04:00:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-508) Update cglib to 3.2.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-508. --------------------------------- Resolution: Done > Update cglib to 3.2.5 > --------------------- > > Key: ARQGRA-508 > URL: https://issues.jboss.org/browse/ARQGRA-508 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Dipak Pawar > Fix For: 2.3.0 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 04:00:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 04:00:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-506) Implement "hover" functionality in Graphene API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-506: ---------------------------------- Fix Version/s: (was: 2.2.2) > Implement "hover" functionality in Graphene API > ----------------------------------------------- > > Key: ARQGRA-506 > URL: https://issues.jboss.org/browse/ARQGRA-506 > Project: Arquillian Graphene > Issue Type: Enhancement > Components: api > Reporter: Matous Jobanek > > Currently, people face challenges in accessing dropdown submenus. > A current implementation of the dropdown submenu hover functionality looks like this: > {code:java} > @Drone > private WebDriver driver; > > @ArquillianResource > private Actions action; > > driver.get("https://www.bootply.com/render/6FC76YQ4Nh"); > > Consumer hover = (By by) -> { > action.moveToElement(driver.findElement(by)) > .perform(); > > }; > > hover.accept(By.linkText("Dropdown")); > hover.accept(By.linkText("Dropdown Link 5")); > hover.accept(By.linkText("Dropdown Submenu Link 5.4")); > hover.accept(By.linkText("Dropdown Submenu Link 5.4.1")); > {code} > An example of the usage of the new Graphene API: > {code:java} > Graphene.hover(WebElement element) > .hover(By by) > .hover(WebElement element) > .toGrapheneElement() > .doubleClick(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 11:46:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 11:46:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2128) Window size is tried to be set to 0x0 when no dimensions are set In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2128: ----------------------------------- Summary: Window size is tried to be set to 0x0 when no dimensions are set Key: ARQ-2128 URL: https://issues.jboss.org/browse/ARQ-2128 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.3.0 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 14 12:19:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 14 Jul 2017 12:19:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-509) Update Arquillian Drone to 2.3.1 In-Reply-To: References: Message-ID: Matous Jobanek created ARQGRA-509: ------------------------------------- Summary: Update Arquillian Drone to 2.3.1 Key: ARQGRA-509 URL: https://issues.jboss.org/browse/ARQGRA-509 Project: Arquillian Graphene Issue Type: Component Upgrade Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: 2.3.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 17 04:28:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 17 Jul 2017 04:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2128) Window size is tried to be set to 0x0 when no dimensions are specified In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2128: -------------------------------- Summary: Window size is tried to be set to 0x0 when no dimensions are specified (was: Window size is tried to be set to 0x0 when no dimensions are set) > Window size is tried to be set to 0x0 when no dimensions are specified > ---------------------------------------------------------------------- > > Key: ARQ-2128 > URL: https://issues.jboss.org/browse/ARQ-2128 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.3.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 17 06:44:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 17 Jul 2017 06:44:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2128) Window size is tried to be set to 0x0 when no dimensions are specified In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQ-2128. ------------------------------- Resolution: Done pushed upstream in https://github.com/arquillian/arquillian-extension-drone/commit/ddedf40bd46a76f7664328722b0663e6b1b2bbdd > Window size is tried to be set to 0x0 when no dimensions are specified > ---------------------------------------------------------------------- > > Key: ARQ-2128 > URL: https://issues.jboss.org/browse/ARQ-2128 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.3.0 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 17 07:44:01 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 17 Jul 2017 07:44:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-501) Error when checking for the invisibility of elements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-501. --------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-graphene/commit/cd1e4b5028c4861fa12134e0d18f9c51537a196e > Error when checking for the invisibility of elements > ---------------------------------------------------- > > Key: ARQGRA-501 > URL: https://issues.jboss.org/browse/ARQGRA-501 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.2.0 > Reporter: Krassimir Valev > Assignee: Matous Jobanek > Fix For: 2.3.0 > > > I get the following error message, when waiting for an element to disappear: > {code:java} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at org.jboss.arquillian.graphene.enricher.WebElementUtils$3.getTarget(WebElementUtils.java:104) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.getTarget(GrapheneProxyHandler.java:149) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.getTarget(GrapheneContextualHandler.java:189) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:162) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:47) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:43) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:43) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.intercept.InterceptorBuilder$2.intercept(InterceptorBuilder.java:139) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:212) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:208) > at com.sun.proxy.$Proxy316.isDisplayed(Unknown Source) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:585) > at org.openqa.selenium.support.ui.ExpectedConditions$20.apply(ExpectedConditions.java:581) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:209) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:96) > {code} > The wait condition looks like this: > {code:java} > return waitGui() > .withTimeout(timeout, TimeUnit.SECONDS) > .pollingEvery(100, TimeUnit.MILLISECONDS) > .ignoring(NoSuchElementException.class, StaleElementReferenceException.class) > .ignoring(InvocationTargetException.class) > .until(ExpectedConditions.invisibilityOfElementLocated(locator)); > {code} > The very same condition used to work with graphene-webdriver 2.0.3.Final and selenium-bom 2.50.1, but it fails now after upgrading to graphene-webdriver 2.2.0 and selenium-bom 3.3.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 17 07:45:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 17 Jul 2017 07:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-507) Update Arquillian Drone to 2.3.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-507. --------------------------------- Resolution: Done Updated in https://github.com/arquillian/arquillian-graphene/commit/49eb5ca47569ffa93179e600816bb96aac0fed33 > Update Arquillian Drone to 2.3.0 > -------------------------------- > > Key: ARQGRA-507 > URL: https://issues.jboss.org/browse/ARQGRA-507 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Components: core > Affects Versions: 2.2.1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 17 07:46:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Mon, 17 Jul 2017 07:46:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-509) Update Arquillian Drone to 2.3.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek closed ARQGRA-509. --------------------------------- Resolution: Done Updated in https://github.com/arquillian/arquillian-graphene/commit/d7425df130056d02e9ee1f53e65be6a1eeba6f62 > Update Arquillian Drone to 2.3.1 > -------------------------------- > > Key: ARQGRA-509 > URL: https://issues.jboss.org/browse/ARQGRA-509 > Project: Arquillian Graphene > Issue Type: Component Upgrade > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: 2.3.0 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jul 18 11:00:00 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Jul 2017 11:00:00 -0400 (EDT) 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:all-tabpanel ] Bartosz Majsak updated ARQ-2107: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/127 > 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 > Reporter: Ladislav Thon > > 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.2.3#72005) From issues at jboss.org Tue Jul 18 11:01:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Jul 2017 11:01:01 -0400 (EDT) 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:all-tabpanel ] Bartosz Majsak updated ARQ-2107: -------------------------------- Affects Version/s: 1.1.13.Final > 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 > > 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.2.3#72005) From issues at jboss.org Tue Jul 18 11:01:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Jul 2017 11:01:01 -0400 (EDT) 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:all-tabpanel ] Bartosz Majsak updated ARQ-2107: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 > > 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.2.3#72005) From issues at jboss.org Tue Jul 18 11:01:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Jul 2017 11:01:01 -0400 (EDT) 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:all-tabpanel ] Bartosz Majsak updated ARQ-2109: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/127 > 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 > > 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.2.3#72005) From issues at jboss.org Tue Jul 18 11:01:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Jul 2017 11:01:01 -0400 (EDT) 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:all-tabpanel ] Bartosz Majsak updated ARQ-2109: -------------------------------- Affects Version/s: 1.1.13.Final > 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 > > 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.2.3#72005) From issues at jboss.org Tue Jul 18 11:01:01 2017 From: issues at jboss.org (Bartosz Majsak (JIRA)) Date: Tue, 18 Jul 2017 11:01:01 -0400 (EDT) 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:all-tabpanel ] Bartosz Majsak updated ARQ-2109: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 > > 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.2.3#72005) From issues at jboss.org Thu Jul 20 08:15:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 20 Jul 2017 08:15:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2129) Operations Binary download/extraction/marking as executable are not thread-safe In-Reply-To: References: Message-ID: Matous Jobanek created ARQ-2129: ----------------------------------- Summary: Operations Binary download/extraction/marking as executable are not thread-safe Key: ARQ-2129 URL: https://issues.jboss.org/browse/ARQ-2129 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.3.1 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.3.2 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 20 08:17:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Thu, 20 Jul 2017 08:17:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2129) Operations Binary download/extraction/marking as executable are not thread-safe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2129: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/104 > Operations Binary download/extraction/marking as executable are not thread-safe > ------------------------------------------------------------------------------- > > Key: ARQ-2129 > URL: https://issues.jboss.org/browse/ARQ-2129 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.3.1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 21 03:17:05 2017 From: issues at jboss.org (Daniel G (JIRA)) Date: Fri, 21 Jul 2017 03:17:05 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438477#comment-13438477 ] Daniel G commented on ARQ-567: ------------------------------ Is the work on this task continued? For us this is a blocker to even think about Arquillian. We have huge EARs where deployments take at least a minute. With hundreds of test classes, this is just impossible to handle with a per test class deployment. > Supporting Test Suites (@ArquillianSuite) > ----------------------------------------- > > Key: ARQ-567 > URL: https://issues.jboss.org/browse/ARQ-567 > Project: Arquillian > Issue Type: Feature Request > Reporter: Mousavi Jahan Abadi S. M. > Assignee: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > > Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: > @RunWith(ArquillianSuite.class) > @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) > public class AllTests{ > @Deployment > public static JavaArchive createTestArchive(){ > return ShrinkWrap.create(JavaArchive.class,"test.jar"); > } > } > The advantages of above approach for users of Arquillian framework are: > - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). > - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. > The advantage of above approach for framework itself is: > - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jul 25 09:21:00 2017 From: issues at jboss.org (Vlastislav Ramik (JIRA)) Date: Tue, 25 Jul 2017 09:21:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: Vlastislav Ramik created ARQ-2130: ------------------------------------- Summary: Unaccessible arquillian-was-remote-8.5 Key: ARQ-2130 URL: https://issues.jboss.org/browse/ARQ-2130 Project: Arquillian Issue Type: Bug Components: WebSphere Containers Reporter: Vlastislav Ramik Assignee: Gerhard Poul I'm not able to get {noformat} org.jboss.arquillian.container arquillian-was-remote-8.5 1.0.0.Beta2 {noformat} It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue Jul 25 10:33:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Tue, 25 Jul 2017 10:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQ-2130: -------------------------------- Affects Version/s: was_1.0.0.Beta2 > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > > I'm not able to get > {noformat} > org.jboss.arquillian.container > arquillian-was-remote-8.5 > 1.0.0.Beta2 > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 26 02:54:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 26 Jul 2017 02:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-2130: ------------------------------ Issue Type: Enhancement (was: Bug) > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > > I'm not able to get > {noformat} > org.jboss.arquillian.container > arquillian-was-remote-8.5 > 1.0.0.Beta2 > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 26 02:54:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 26 Jul 2017 02:54:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul updated ARQ-2130: ------------------------------ Priority: Critical (was: Major) > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > Priority: Critical > > I'm not able to get > {noformat} > org.jboss.arquillian.container > arquillian-was-remote-8.5 > 1.0.0.Beta2 > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 26 02:56:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 26 Jul 2017 02:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440274#comment-13440274 ] Gerhard Poul commented on ARQ-2130: ----------------------------------- [~vramik] If I understand your issue correctly it is about the arquillian-was-remote-8.5 not being available from the official maven repository? FYI: This is mentioned in the documentation at https://docs.jboss.org/author/display/ARQ/WAS+V8.5+-+Remote which is why I categorized this as an enhancement instead of a bug > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > Priority: Critical > > I'm not able to get > {noformat} > org.jboss.arquillian.container > arquillian-was-remote-8.5 > 1.0.0.Beta2 > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 26 05:17:00 2017 From: issues at jboss.org (Vlastislav Ramik (JIRA)) Date: Wed, 26 Jul 2017 05:17:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440368#comment-13440368 ] Vlastislav Ramik commented on ARQ-2130: --------------------------------------- [~gpoul] oh, I missed the info in the docs. Basically yes, the issue is about not being available from maven central or http://repository.jboss.org/nexus and it's uncomfortable to build it with every jenkins build. Anyway, I was able to build it locally with given instructions. But now I have an issue with using it. Maven says: {noformat}[WARNING] The POM for org.jboss.arquillian.container:arquillian-was-remote-8.5:jar:1.0.0.Beta2 is invalid, transitive dependencies (if any) will not be available{noformat} and then I get {noformat} java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor Caused by: java.lang.reflect.InvocationTargetException Caused by: java.lang.NoClassDefFoundError: Lcom/ibm/websphere/management/AdminClient; Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClient {noformat} I guess it might be related to dependencies with system : * https://github.com/arquillian/arquillian-container-was/blob/master/was-remote-8.5/pom.xml#L105-L111 * https://github.com/arquillian/arquillian-container-was/blob/master/was-remote-8.5/pom.xml#L136-L150 I know it's OT, should I open anothe issue on that? > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > Priority: Critical > > I'm not able to get > {noformat} > org.jboss.arquillian.container > arquillian-was-remote-8.5 > 1.0.0.Beta2 > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed Jul 26 05:41:00 2017 From: issues at jboss.org (Vlastislav Ramik (JIRA)) Date: Wed, 26 Jul 2017 05:41:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440368#comment-13440368 ] Vlastislav Ramik edited comment on ARQ-2130 at 7/26/17 5:40 AM: ---------------------------------------------------------------- [~gpoul] oh, I missed the info in the docs. Basically yes, the issue is about not being available from maven central or http://repository.jboss.org/nexus and it's uncomfortable to build it with every jenkins build. Anyway, I was able to build it locally with given instructions. But now I have an issue with using it. Maven says: {noformat}[WARNING] The POM for org.jboss.arquillian.container:arquillian-was-remote-8.5:jar:1.0.0.Beta2 is invalid, transitive dependencies (if any) will not be available{noformat} and then I get {noformat} java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor Caused by: java.lang.reflect.InvocationTargetException Caused by: java.lang.NoClassDefFoundError: Lcom/ibm/websphere/management/AdminClient; Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClient {noformat} Edit: the problem is that I have to set WAS85_HOME for the test build to have access to transitive dependencies, shoudn't be also documented? was (Author: vramik): [~gpoul] oh, I missed the info in the docs. Basically yes, the issue is about not being available from maven central or http://repository.jboss.org/nexus and it's uncomfortable to build it with every jenkins build. Anyway, I was able to build it locally with given instructions. But now I have an issue with using it. Maven says: {noformat}[WARNING] The POM for org.jboss.arquillian.container:arquillian-was-remote-8.5:jar:1.0.0.Beta2 is invalid, transitive dependencies (if any) will not be available{noformat} and then I get {noformat} java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor Caused by: java.lang.reflect.InvocationTargetException Caused by: java.lang.NoClassDefFoundError: Lcom/ibm/websphere/management/AdminClient; Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.management.AdminClient {noformat} I guess it might be related to dependencies with system : * https://github.com/arquillian/arquillian-container-was/blob/master/was-remote-8.5/pom.xml#L105-L111 * https://github.com/arquillian/arquillian-container-was/blob/master/was-remote-8.5/pom.xml#L136-L150 I know it's OT, should I open anothe issue on that? > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > Priority: Critical > > I'm not able to get > {noformat} > org.jboss.arquillian.container > arquillian-was-remote-8.5 > 1.0.0.Beta2 > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 27 08:41:00 2017 From: issues at jboss.org (Benjamin Marwell (JIRA)) Date: Thu, 27 Jul 2017 08:41:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2131) Fix for multiple JVM arguments not release In-Reply-To: References: Message-ID: Benjamin Marwell created ARQ-2131: ------------------------------------- Summary: Fix for multiple JVM arguments not release Key: ARQ-2131 URL: https://issues.jboss.org/browse/ARQ-2131 Project: Arquillian Issue Type: Feature Request Components: WebSphere Containers Environment: {code}arquillian-container-was-1.0.0.Beta2{code} {{arquillian.xml}} snippet: {code:xml} xml -Dsetting1=x -Dsetting2=y {code} Reporter: Benjamin Marwell Assignee: Gerhard Poul Hello, h2. expected output Process started with (from Debug): {{FINER: Starting server with command: [java, -Dsetting1=x, -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} h2. actual output note the missing comma betweed setting1 and setting2: {{FINER: Starting server with command: [java, -Dsetting1=x -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} h2. Solution Already exists. This commit is currently not in a release: https://github.com/arquillian/arquillian-container-was/commit/a1a77fe92418f49943a97a57a4dd1ff7ebc2bd25#diff-957685487719c29ce4c464fc2ec9cf39 What can't be seen from here: this commit is needed to have multiple JVM args. Otherwise all jvm args are concatenated into a single String. So, the bug is fixed in trunk, but not released. h2. Proposed test case It is also missing a test case. Please add a test case with two or more {{-D}}-Parameters and check in your servlet if they are set. Thank you very much! -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 27 11:58:00 2017 From: issues at jboss.org (Benjamin Marwell (JIRA)) Date: Thu, 27 Jul 2017 11:58:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2131) Fix for multiple JVM arguments not release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Marwell updated ARQ-2131: ---------------------------------- Issue Type: Task (was: Feature Request) > Fix for multiple JVM arguments not release > ------------------------------------------ > > Key: ARQ-2131 > URL: https://issues.jboss.org/browse/ARQ-2131 > Project: Arquillian > Issue Type: Task > Components: WebSphere Containers > Environment: {code}arquillian-container-was-1.0.0.Beta2{code} > {{arquillian.xml}} snippet: > {code:xml} > > xml > -Dsetting1=x -Dsetting2=y > > {code} > Reporter: Benjamin Marwell > Assignee: Gerhard Poul > > Hello, > h2. expected output > Process started with (from Debug): > {{FINER: Starting server with command: [java, -Dsetting1=x, -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} > h2. actual output > note the missing comma betweed setting1 and setting2: > {{FINER: Starting server with command: [java, -Dsetting1=x -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} > h2. Solution > Already exists. This commit is currently not in a release: > https://github.com/arquillian/arquillian-container-was/commit/a1a77fe92418f49943a97a57a4dd1ff7ebc2bd25#diff-957685487719c29ce4c464fc2ec9cf39 > What can't be seen from here: this commit is needed to have multiple JVM args. Otherwise all jvm args are concatenated into a single String. > So, the bug is fixed in trunk, but not released. > h2. Proposed test case > It is also missing a test case. > Please add a test case with two or more {{-D}}-Parameters and check in your servlet if they are set. > Thank you very much! -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu Jul 27 11:59:00 2017 From: issues at jboss.org (Benjamin Marwell (JIRA)) Date: Thu, 27 Jul 2017 11:59:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2131) Fix for multiple JVM arguments not release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Marwell updated ARQ-2131: ---------------------------------- Issue Type: Bug (was: Task) > Fix for multiple JVM arguments not release > ------------------------------------------ > > Key: ARQ-2131 > URL: https://issues.jboss.org/browse/ARQ-2131 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: {code}arquillian-container-was-1.0.0.Beta2{code} > {{arquillian.xml}} snippet: > {code:xml} > > xml > -Dsetting1=x -Dsetting2=y > > {code} > Reporter: Benjamin Marwell > Assignee: Gerhard Poul > > Hello, > h2. expected output > Process started with (from Debug): > {{FINER: Starting server with command: [java, -Dsetting1=x, -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} > h2. actual output > note the missing comma betweed setting1 and setting2: > {{FINER: Starting server with command: [java, -Dsetting1=x -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} > h2. Solution > Already exists. This commit is currently not in a release: > https://github.com/arquillian/arquillian-container-was/commit/a1a77fe92418f49943a97a57a4dd1ff7ebc2bd25#diff-957685487719c29ce4c464fc2ec9cf39 > What can't be seen from here: this commit is needed to have multiple JVM args. Otherwise all jvm args are concatenated into a single String. > So, the bug is fixed in trunk, but not released. > h2. Proposed test case > It is also missing a test case. > Please add a test case with two or more {{-D}}-Parameters and check in your servlet if they are set. > Thank you very much! -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 28 10:06:00 2017 From: issues at jboss.org (Vaclav Muzikar (JIRA)) Date: Fri, 28 Jul 2017 10:06:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-510) cglib is causing warnings in FieldAccessValidatorEnricher In-Reply-To: References: Message-ID: Vaclav Muzikar created ARQGRA-510: ------------------------------------- Summary: cglib is causing warnings in FieldAccessValidatorEnricher Key: ARQGRA-510 URL: https://issues.jboss.org/browse/ARQGRA-510 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.3.0 Reporter: Vaclav Muzikar Priority: Critical In Graphene 2.3.0, cglib dependency was updated to version 3.2.5. When using a Page Object, many warning messages (one for each Page Object) are printed to the log (which could then be literally flooded with those messages). This is probably caused by the cglib update. {noformat} Jul 28, 2017 3:52:42 PM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity WARNING: Package-friendly field 'CGLIB$FACTORY_DATA' found in org.test.TestPage$$EnhancerByGraphene$$260509ea. Direct access to fields outside of the declaring class is not allowed. {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 28 10:56:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 28 Jul 2017 10:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-510) cglib is causing warnings in FieldAccessValidatorEnricher In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated ARQGRA-510: ---------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/172 > cglib is causing warnings in FieldAccessValidatorEnricher > --------------------------------------------------------- > > Key: ARQGRA-510 > URL: https://issues.jboss.org/browse/ARQGRA-510 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.3.0 > Reporter: Vaclav Muzikar > Priority: Critical > > In Graphene 2.3.0, cglib dependency was updated to version 3.2.5. > When using a Page Object, many warning messages (one for each Page Object) are printed to the log (which could then be literally flooded with those messages). This is probably caused by the cglib update. > {noformat} > Jul 28, 2017 3:52:42 PM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field 'CGLIB$FACTORY_DATA' found in org.test.TestPage$$EnhancerByGraphene$$260509ea. Direct access to fields outside of the declaring class is not allowed. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri Jul 28 10:56:00 2017 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Fri, 28 Jul 2017 10:56:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-510) cglib is causing warnings in FieldAccessValidatorEnricher In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQGRA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek reassigned ARQGRA-510: ------------------------------------- Assignee: Matous Jobanek > cglib is causing warnings in FieldAccessValidatorEnricher > --------------------------------------------------------- > > Key: ARQGRA-510 > URL: https://issues.jboss.org/browse/ARQGRA-510 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.3.0 > Reporter: Vaclav Muzikar > Assignee: Matous Jobanek > Priority: Critical > > In Graphene 2.3.0, cglib dependency was updated to version 3.2.5. > When using a Page Object, many warning messages (one for each Page Object) are printed to the log (which could then be literally flooded with those messages). This is probably caused by the cglib update. > {noformat} > Jul 28, 2017 3:52:42 PM org.jboss.arquillian.graphene.enricher.FieldAccessValidatorEnricher checkFieldValidity > WARNING: Package-friendly field 'CGLIB$FACTORY_DATA' found in org.test.TestPage$$EnhancerByGraphene$$260509ea. Direct access to fields outside of the declaring class is not allowed. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 31 12:24:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 31 Jul 2017 12:24:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442317#comment-13442317 ] Gerhard Poul commented on ARQ-2130: ----------------------------------- [~vramik] yes, so we currently only document this in the build instructions at https://developer.jboss.org/wiki/BuildingArquillianWASContainer; do you think it would make sense to also document this in the documentation at https://docs.jboss.org/author/display/ARQ/WAS+V8.5+-+Remote or is the reference from the document to the build instructions not easy enough to find? Let me know what might help in this case. > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > Priority: Critical > > I'm not able to get > {noformat} > org.jboss.arquillian.container > arquillian-was-remote-8.5 > 1.0.0.Beta2 > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xml#L79-L88 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon Jul 31 12:28:00 2017 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Mon, 31 Jul 2017 12:28:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2131) Fix for multiple JVM arguments not release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Poul resolved ARQ-2131. ------------------------------- Fix Version/s: was_1.0.0.next Resolution: Duplicate Issue Duplicate of ARQ-2121; will be fixed in next release [~bmarwell] if you care strongly about a test, please send me a pull request; otherwise I'd suggest to release this as-is. > Fix for multiple JVM arguments not release > ------------------------------------------ > > Key: ARQ-2131 > URL: https://issues.jboss.org/browse/ARQ-2131 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: {code}arquillian-container-was-1.0.0.Beta2{code} > {{arquillian.xml}} snippet: > {code:xml} > > xml > -Dsetting1=x -Dsetting2=y > > {code} > Reporter: Benjamin Marwell > Assignee: Gerhard Poul > Fix For: was_1.0.0.next > > > Hello, > h2. expected output > Process started with (from Debug): > {{FINER: Starting server with command: [java, -Dsetting1=x, -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} > h2. actual output > note the missing comma betweed setting1 and setting2: > {{FINER: Starting server with command: [java, -Dsetting1=x -Dsetting2=y, -javaagent:lib/bootstrap-agent.jar, -jar, lib/ws-launch.jar, defaultServer]}} > h2. Solution > Already exists. This commit is currently not in a release: > https://github.com/arquillian/arquillian-container-was/commit/a1a77fe92418f49943a97a57a4dd1ff7ebc2bd25#diff-957685487719c29ce4c464fc2ec9cf39 > What can't be seen from here: this commit is needed to have multiple JVM args. Otherwise all jvm args are concatenated into a single String. > So, the bug is fixed in trunk, but not released. > h2. Proposed test case > It is also missing a test case. > Please add a test case with two or more {{-D}}-Parameters and check in your servlet if they are set. > Thank you very much! -- This message was sent by Atlassian JIRA (v7.2.3#72005)