August 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-994) Allow Arquillian Drone to wait asynchronously for instance creation

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-994?page=com.atlassian.jira.plugin.sy... ] Karel Piwko closed ARQ-994. --------------------------- > Allow Arquillian Drone to wait asynchronously for instance creation > ------------------------------------------------------------------- > > Key: ARQ-994 > URL: https://issues.jboss.org/browse/ARQ-994 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.0.0.Final > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Alpha3 > > > Drone should create WebDriver/Selenium instances using a Future<> call or similar construction. > Sometime, an opening of browser fails (e.g. on Solaris, when something goes wrong, like machine having too many opened files) and create instance never actually returns, causing tests to hang forever.dron -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1435) Update Arquillian Core in Drone to 1.1.0.Final

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1435?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1435. ---------------------------- > Update Arquillian Core in Drone to 1.1.0.Final > ---------------------------------------------- > > Key: ARQ-1435 > URL: https://issues.jboss.org/browse/ARQ-1435 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Alpha3 > > > In order to make usage of ShrinkWrap Resolvers easier with Drone (required by phantomjs driver), bump Arquillian Core to 1.1.0.Final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1452) Update selenium to 2.33.0

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1452?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1452. ---------------------------- > Update selenium to 2.33.0 > ------------------------- > > Key: ARQ-1452 > URL: https://issues.jboss.org/browse/ARQ-1452 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.2.0.Alpha2 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Alpha3 > > > Update Selenium BOM version in Drone -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-754) Change the way how Drone context is initialized

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-754?page=com.atlassian.jira.plugin.sy... ] Karel Piwko closed ARQ-754. --------------------------- > Change the way how Drone context is initialized > ----------------------------------------------- > > Key: ARQ-754 > URL: https://issues.jboss.org/browse/ARQ-754 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.0.0.CR3 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: drone_1.2.0.Alpha3 > > > Introduce either a lazy loading or storing some lightweight object in the Arquillian session to allow jbehave extension to inject Drone instances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1424) Automatic resolution of PhantomJS binary for PhantomJS driver use

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1424?page=com.atlassian.jira.plugin.s... ] Karel Piwko closed ARQ-1424. ---------------------------- > Automatic resolution of PhantomJS binary for PhantomJS driver use > ----------------------------------------------------------------- > > Key: ARQ-1424 > URL: https://issues.jboss.org/browse/ARQ-1424 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Labels: graphene-sprint > Fix For: drone_1.2.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ

by David Mann (JIRA)

[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ] David Mann updated ARQ-1455: ---------------------------- Description: When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM. I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container - Managed server was not started within [60] s Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on. After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-) This bug report is mainly to help people that run into the same problem. Kind regards, and cheers for an awesome product :-) David was: Someone should add the following to the arquillian getting started tutorial (http://arquillian.org/guides/getting_started/)  <defaultProtocol type="Servlet 3.0" /> See attached test case, which can be resolved using the snippet above. > BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ > -------------------------------------------------------------------- > > Key: ARQ-1455 > URL: https://issues.jboss.org/browse/ARQ-1455 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: David Mann > Attachments: arquillian-tutorial.zip, runtime-BOM.zip > > > When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM. > I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with > - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > - Managed server was not started within [60] s > Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on. > After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-) > This bug report is mainly to help people that run into the same problem. > Kind regards, > and cheers for an awesome product :-) > David -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ

by David Mann (JIRA)

[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ] David Mann updated ARQ-1455: ---------------------------- Component/s: Build Infrastructure > BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ > -------------------------------------------------------------------- > > Key: ARQ-1455 > URL: https://issues.jboss.org/browse/ARQ-1455 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build Infrastructure, Documentation > Reporter: David Mann > Attachments: arquillian-tutorial.zip, runtime-BOM.zip > > > When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM. > I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with > - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > - Managed server was not started within [60] s > Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on. > After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-) > This bug report is mainly to help people that run into the same problem. > Kind regards, > and cheers for an awesome product :-) > David -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ

by David Mann (JIRA)

[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ] David Mann updated ARQ-1455: ---------------------------- Attachment: runtime-BOM.zip > BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ > -------------------------------------------------------------------- > > Key: ARQ-1455 > URL: https://issues.jboss.org/browse/ARQ-1455 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: David Mann > Attachments: arquillian-tutorial.zip, runtime-BOM.zip > > > Someone should add the following to the arquillian getting started tutorial (http://arquillian.org/guides/getting_started/) >  > <defaultProtocol type="Servlet 3.0" /> > See attached test case, which can be resolved using the snippet above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ

by David Mann (JIRA)

[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ] David Mann commented on ARQ-1455: --------------------------------- You are right :-) still this doesn't solve the problem completely After some further digging, I think I got it right now: - the BOM Versions 1.0.0 through 1.0.3 are okay, they reference the 7.1.1. runtime - the BOM Versions from 1.0.4 onwards are broken, as they reference the 7.1.3. runtime => see attached runtime-BOM.zip: - run 'mvn clean test' => fails - run 'mvn clean test -Pforce-711-runtime' => works Workaround for BOM Versions 1.0.4.Final and onwards is adding <defaultProtocol type="Servlet 3.0" /> to arquillian.xml > BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ > -------------------------------------------------------------------- > > Key: ARQ-1455 > URL: https://issues.jboss.org/browse/ARQ-1455 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: David Mann > Attachments: arquillian-tutorial.zip, runtime-BOM.zip > > > Someone should add the following to the arquillian getting started tutorial (http://arquillian.org/guides/getting_started/) >  > <defaultProtocol type="Servlet 3.0" /> > See attached test case, which can be resolved using the snippet above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1455) BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1455: ------------------------------------ JBoss BOM and Arquillian BOM are not meant to be used together. JBoss BOM contain Arquillian BOM. > BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ > -------------------------------------------------------------------- > > Key: ARQ-1455 > URL: https://issues.jboss.org/browse/ARQ-1455 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: David Mann > Attachments: arquillian-tutorial.zip > > > Someone should add the following to the arquillian getting started tutorial (http://arquillian.org/guides/getting_started/) >  > <defaultProtocol type="Servlet 3.0" /> > See attached test case, which can be resolved using the snippet above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues August 2013