January 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2070) Add possibility to strip statement delimiter from parsed statements

by Tobias Stadler (JIRA)

Tobias Stadler created ARQ-2070: ----------------------------------- Summary: Add possibility to strip statement delimiter from parsed statements Key: ARQ-2070 URL: https://issues.jboss.org/browse/ARQ-2070 Project: Arquillian Issue Type: Feature Request Components: Extension - Persistence Reporter: Tobias Stadler Assignee: Bartosz Majsak Priority: Minor I would be nice to have the possibility to strip the statement delimiter from the parsed statements. E.g. IBM DB2 (Express-c 11.1) does not accept the delimiter in the executed statement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2036) Migrating to wildfly10, I get an error with the jboss logging

by Manuel Aznar Pérez (JIRA)

[ https://issues.jboss.org/browse/ARQ-2036?page=com.atlassian.jira.plugin.s... ] Manuel Aznar Pérez commented on ARQ-2036: ----------------------------------------- I use wildfly-arquillian-container-managed: version 2.0.2.Final and 2.1.0.Alpha1 with wildfly 10.1.0.final for my test arquillian. > Migrating to wildfly10, I get an error with the jboss logging > ------------------------------------------------------------- > > Key: ARQ-2036 > URL: https://issues.jboss.org/browse/ARQ-2036 > Project: Arquillian > Issue Type: Bug > Environment: WildFly10 mode managed in arquillian: > org.wildfly.arquillian:wildfly-arquillian-parent:2.0.0.Final > org.jboss.arquillian:arquillian-build:1.1.11.Final (modelversion: 4.0.0) > Reporter: lamiae obila > Priority: Blocker > > I was migrating my application from Jboss AS7 to Wildfly10 using arquillian for tests. > But, I get this error : > {code:java} > Exception in thread "Remoting "endpoint" task-4" java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;I)V > at org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:158) > at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:456) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > I use the wildfly-arquillian-container-managed: version 2.0.0.Final for my test arquillian. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-495) Scheme and URL properties might be used in incompatible ways

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-495?page=com.atlassian.jira.plugin... ] Alex Soto updated ARQGRA-495: ----------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/160 > Scheme and URL properties might be used in incompatible ways > ------------------------------------------------------------ > > Key: ARQGRA-495 > URL: https://issues.jboss.org/browse/ARQGRA-495 > Project: Arquillian Graphene > Issue Type: Bug > Reporter: Alex Soto > Priority: Minor > > Graphene allows you to configure two properties, scheme and url. The problem is that Scheme might be http, https, ... and the URL instead of being the host + port + context definition, it is a full URL. SO it means that you could configure URL using https and scheme using http and then internally both values might be used independently. > The ideal scenario would be that URL protocol takes precedence over scheme -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-495) Scheme and URL properties might be used in incompatible ways

by Alex Soto (JIRA)

Alex Soto created ARQGRA-495: -------------------------------- Summary: Scheme and URL properties might be used in incompatible ways Key: ARQGRA-495 URL: https://issues.jboss.org/browse/ARQGRA-495 Project: Arquillian Graphene Issue Type: Bug Reporter: Alex Soto Priority: Minor Graphene allows you to configure two properties, scheme and url. The problem is that Scheme might be http, https, ... and the URL instead of being the host + port + context definition, it is a full URL. SO it means that you could configure URL using https and scheme using http and then internally both values might be used independently. The ideal scenario would be that URL protocol takes precedence over scheme -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-494) Enrich WebElements returned by JavascriptExecutor (to protect against staleness etc)

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-494?page=com.atlassian.jira.plugin... ] Vsevolod Golovanov commented on ARQGRA-494: ------------------------------------------- I should clarify the purpose of this, because I understand that the staleness protection here... -- is probably not necessary, because you don't expect executeScript to be lazy; or at least it's reasonable to not provide protection here; -- is not really doable as there is no By condition and you can't just execute a random script again, because it could have side effects. I really just want the WebElements to be proxified, so that I could easily add my interceptors. I need to intercept all calls to WebElement's, regardless of how they were located. Right now I'm proxifying these myself with org.jboss.arquillian.graphene.proxy.GrapheneProxy. > Enrich WebElements returned by JavascriptExecutor (to protect against staleness etc) > ------------------------------------------------------------------------------------ > > Key: ARQGRA-494 > URL: https://issues.jboss.org/browse/ARQGRA-494 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Final > Reporter: Vsevolod Golovanov > > ARQGRA-252 took care of elements found by manually calling SearchContext#findElement*, but there is still org.openqa.selenium.JavascriptExecutor: > {code} > jsExecutor.executeScript("return $('*').toArray();"); > {code} > This would return unproxified WebElement instances. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-494) Enrich WebElements returned by JavascriptExecutor (to protect against staleness etc)

by Vsevolod Golovanov (JIRA)

Vsevolod Golovanov created ARQGRA-494: ----------------------------------------- Summary: Enrich WebElements returned by JavascriptExecutor (to protect against staleness etc) Key: ARQGRA-494 URL: https://issues.jboss.org/browse/ARQGRA-494 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.1.0.Final Reporter: Vsevolod Golovanov ARQGRA-252 took care of elements found by manually calling SearchContext#findElement*, but there is still org.openqa.selenium.JavascriptExecutor: {code} jsExecutor.executeScript("return $('*').toArray();"); {code} would return unproxified WebElement instances. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-494) Enrich WebElements returned by JavascriptExecutor (to protect against staleness etc)

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-494?page=com.atlassian.jira.plugin... ] Vsevolod Golovanov updated ARQGRA-494: -------------------------------------- Description: ARQGRA-252 took care of elements found by manually calling SearchContext#findElement*, but there is still org.openqa.selenium.JavascriptExecutor: {code} jsExecutor.executeScript("return $('*').toArray();"); {code} This would return unproxified WebElement instances. was: ARQGRA-252 took care of elements found by manually calling SearchContext#findElement*, but there is still org.openqa.selenium.JavascriptExecutor: {code} jsExecutor.executeScript("return $('*').toArray();"); {code} would return unproxified WebElement instances. > Enrich WebElements returned by JavascriptExecutor (to protect against staleness etc) > ------------------------------------------------------------------------------------ > > Key: ARQGRA-494 > URL: https://issues.jboss.org/browse/ARQGRA-494 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Final > Reporter: Vsevolod Golovanov > > ARQGRA-252 took care of elements found by manually calling SearchContext#findElement*, but there is still org.openqa.selenium.JavascriptExecutor: > {code} > jsExecutor.executeScript("return $('*').toArray();"); > {code} > This would return unproxified WebElement instances. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1967) Support 'alternative' deploy of ASM in Jacoco

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1967?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1967: -------------------------------- Fix Version/s: jacoco_1.0.0.Alpha9 (was: jacoco_1.0.0.next) > Support 'alternative' deploy of ASM in Jacoco > ---------------------------------------------- > > Key: ARQ-1967 > URL: https://issues.jboss.org/browse/ARQ-1967 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha8 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2069) JaCoCo include/exclude configuration does not support multiline

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2069?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2069: -------------------------------- Fix Version/s: jacoco_1.0.0.Alpha9 > JaCoCo include/exclude configuration does not support multiline > --------------------------------------------------------------- > > Key: ARQ-2069 > URL: https://issues.jboss.org/browse/ARQ-2069 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha8 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > Fix For: jacoco_1.0.0.Alpha9 > > > JacocoConfiguration already splits multiple includes/excludes in a whitespace aware way using delimiter "\\s*;\\s*". But this only strips the whitespaces around the delimiter, not whitespaces before the first and after the last entry. > Because of this you cannot use newlines to format the entries. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2069) JaCoCo include/exclude configuration does not support multiline

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2069?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-2069. --------------------------------- Resolution: Done > JaCoCo include/exclude configuration does not support multiline > --------------------------------------------------------------- > > Key: ARQ-2069 > URL: https://issues.jboss.org/browse/ARQ-2069 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha8 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > Fix For: jacoco_1.0.0.Alpha9 > > > JacocoConfiguration already splits multiple includes/excludes in a whitespace aware way using delimiter "\\s*;\\s*". But this only strips the whitespaces around the delimiter, not whitespaces before the first and after the last entry. > Because of this you cannot use newlines to format the entries. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2017