October 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1237) Warp: use PortProber to determine free ports for proxy

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-1237?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-1237: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Warp: use PortProber to determine free ports for proxy > ------------------------------------------------------ > > Key: ARQ-1237 > URL: https://issues.jboss.org/browse/ARQ-1237 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Christian Schulz > Priority: Minor > Fix For: warp_1.0.0.Alpha8 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Selenium 2 uses {{PortProber}} to check free ports to run Selenium Server on. > We can leverage that component too for Warp proxy and avoid conflicting ports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2026) Client activity failures should have more priority over server activities

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2026?page=com.atlassian.jira.plugin.s... ] Matous Jobanek closed ARQ-2026. ------------------------------- Resolution: Done > Client activity failures should have more priority over server activities > ------------------------------------------------------------------------- > > Key: ARQ-2026 > URL: https://issues.jboss.org/browse/ARQ-2026 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Christian Schulz > Assignee: Christian Schulz > Fix For: warp_1.0.0.Alpha8 > > > I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException. > In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures. > In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts. > I would suggest to ignore AssertionErrors from server activities if there is a catched client exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2026) Client activity failures should have more priority over server activities

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2026?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2026: -------------------------------- Fix Version/s: warp_1.0.0.Alpha8 (was: warp_1.0.0.Beta1) > Client activity failures should have more priority over server activities > ------------------------------------------------------------------------- > > Key: ARQ-2026 > URL: https://issues.jboss.org/browse/ARQ-2026 > Project: Arquillian > Issue Type: Enhancement > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7 > Reporter: Christian Schulz > Assignee: Christian Schulz > Fix For: warp_1.0.0.Alpha8 > > > I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException. > In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures. > In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts. > I would suggest to ignore AssertionErrors from server activities if there is a catched client exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2048) Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/ARQ-2048?page=com.atlassian.jira.plugin.s... ] Tomas Remes updated ARQ-2048: ----------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: weld_2.0.0.Beta4 Resolution: Done > Excluded elements in beans.xml by the Weld Arquillian plugin is an all check instead of an any > ---------------------------------------------------------------------------------------------- > > Key: ARQ-2048 > URL: https://issues.jboss.org/browse/ARQ-2048 > Project: Arquillian > Issue Type: Bug > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > Fix For: weld_2.0.0.Beta4 > > > Since ARQ-2039, exclude elements in beans.xml are taken into account. However, the logic only exclude classes which match all elements instead of any one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.s... ] Tomas Remes updated ARQ-2023: ----------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > Priority: Minor > Fix For: weld_2.0.0.Beta4 > > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.s... ] Tomas Remes updated ARQ-2023: ----------------------------- Fix Version/s: weld_2.0.0.Beta4 Affects Version/s: weld_2.0.0.Beta3 > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Affects Versions: weld_2.0.0.Beta3 > Reporter: Antonin Stefanutti > Priority: Minor > Fix For: weld_2.0.0.Beta4 > > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment

by Antonin Stefanutti (JIRA)

[ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.s... ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Description: Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. was: Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter for the SE environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment

by Antonin Stefanutti (JIRA)

[ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.s... ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Git Pull Request: https://github.com/arquillian/arquillian-container-weld/pull/36 (was: https://github.com/arquillian/arquillian-container-weld/pull/23) > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2023) Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment

by Antonin Stefanutti (JIRA)

[ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.s... ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Summary: Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment (was: Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter) > Use relaxed default constructor configuration in Arquillian Weld embedded adapter for SE environment > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2023) Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter

by Antonin Stefanutti (JIRA)

[ https://issues.jboss.org/browse/ARQ-2023?page=com.atlassian.jira.plugin.s... ] Antonin Stefanutti updated ARQ-2023: ------------------------------------ Summary: Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter (was: Use Weld relaxed default constructor configuration in Arquillian Weld SE embedded 1.1 adapter) > Use Weld relaxed default constructor configuration in Arquillian Weld embedded adapter > -------------------------------------------------------------------------------------- > > Key: ARQ-2023 > URL: https://issues.jboss.org/browse/ARQ-2023 > Project: Arquillian > Issue Type: Enhancement > Components: Weld Containers > Reporter: Antonin Stefanutti > Priority: Minor > > Weld exposes a relaxed default constructor configuration that enables to relax the constraint of having to declare a default constructor for proxied bean types. > This configuration is very useful in a number of use cases, notably when integrating with third-parties libraries that do some _heavy_ initialisation in their default constructors, like Apache Camel. > This is enabled by default in Weld SE so it would be consistent to enable that mode as well when using the corresponding Arquillian adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2016