December 2016 - arquillian-issues

[JBoss JIRA] (ARQ-2067) Can't use the Arquillian Karaf Extension with a remote container

by Cristina González castellano (JIRA)

Cristina González castellano created ARQ-2067: ------------------------------------------------- Summary: Can't use the Arquillian Karaf Extension with a remote container Key: ARQ-2067 URL: https://issues.jboss.org/browse/ARQ-2067 Project: Arquillian Issue Type: Bug Components: OSGi Containers Affects Versions: osgi_2.1.0.Final Reporter: Cristina González castellano Assignee: Thomas Diesler I have been trying to use the Arquillian OSGi extension with a Docker container, but I have found the next issue: - When we use JMXDeployableContainer, to deploy a OSGi Bundle to a remote OSGi Karaf, we use a local URL, of the type: file:/var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar. - Of course this URL doesn't exist in the remote Docker container. - So I get the exception: Caused by: java.io.IOException: Installation of a bundle with location 253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar failed with the message: /var/folders/nq/p1_j3ycj169dzl1ypg8d5zhh0000gn/T/vfs/osgitmp-8888e08d9dca9b47/urlstream-d8ff47698b0d2150/253ae58a-4ad3-4077-b049-281ef1b9d3eb.jar (No such file or directory) Have you faced this issue before? What do you think is the best solution? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1684) Jacoco extension filters do not work as advertised

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1684?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1684: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/31 > Jacoco extension filters do not work as advertised > -------------------------------------------------- > > Key: ARQ-1684 > URL: https://issues.jboss.org/browse/ARQ-1684 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha6 > Reporter: Rich DiCroce > Fix For: jacoco_1.0.0.next > > > The Jacoco includes/excludes mechanism does not work the way the [1.0.0.Alpha5 release announcement|http://arquillian.org/blog/2012/11/27/arquillian-extension-j...] implies it does. Specifically, the release announcement shows excluding a package and then including some sub-packages. This implies that includes have precedence over excludes, but that is not true. It's clear from looking at the source code that includes and excludes just get turned into filters that are all ANDed together. So if you have > exclude some.package.* > include some.package.foo.* > then some.package.foo will not be included because the exclude for some.package will return false. Effectively, excludes have priority over includes. > This would be fine if not for the fact that an "include everything" filter is automatically added. This, combined with exclusions having priority, breaks a key use case, namely: I want to exclude all packages that are not my own code. I can't just > include my.package.* > because of the automatic include all filter, and I can't > exclude * > include my.package.* > because the exclude blocks out the include. > Including everything is a problem because then so many classes have to be instrumented that the test just hangs and the archive never gets deployed. For me, this makes the Jacoco extension completely unusable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-1684) Jacoco extension filters do not work as advertised

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1684?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak reassigned ARQ-1684: ----------------------------------- Assignee: Bartosz Majsak > Jacoco extension filters do not work as advertised > -------------------------------------------------- > > Key: ARQ-1684 > URL: https://issues.jboss.org/browse/ARQ-1684 > Project: Arquillian > Issue Type: Bug > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha6 > Reporter: Rich DiCroce > Assignee: Bartosz Majsak > Fix For: jacoco_1.0.0.next > > > The Jacoco includes/excludes mechanism does not work the way the [1.0.0.Alpha5 release announcement|http://arquillian.org/blog/2012/11/27/arquillian-extension-j...] implies it does. Specifically, the release announcement shows excluding a package and then including some sub-packages. This implies that includes have precedence over excludes, but that is not true. It's clear from looking at the source code that includes and excludes just get turned into filters that are all ANDed together. So if you have > exclude some.package.* > include some.package.foo.* > then some.package.foo will not be included because the exclude for some.package will return false. Effectively, excludes have priority over includes. > This would be fine if not for the fact that an "include everything" filter is automatically added. This, combined with exclusions having priority, breaks a key use case, namely: I want to exclude all packages that are not my own code. I can't just > include my.package.* > because of the automatic include all filter, and I can't > exclude * > include my.package.* > because the exclude blocks out the include. > Including everything is a problem because then so many classes have to be instrumented that the test just hangs and the archive never gets deployed. For me, this makes the Jacoco extension completely unusable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2066) Supprt for JUnit 5

by Tobias Stadler (JIRA)

Tobias Stadler created ARQ-2066: ----------------------------------- Summary: Supprt for JUnit 5 Key: ARQ-2066 URL: https://issues.jboss.org/browse/ARQ-2066 Project: Arquillian Issue Type: Feature Request Reporter: Tobias Stadler The final relase of JUnit 5 is scheduled for Q1 2017. It would be nice if Arquillian would support it then. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2065) Combine multiple test results

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2065?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2065: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Combine multiple test results > ----------------------------- > > Key: ARQ-2065 > URL: https://issues.jboss.org/browse/ARQ-2065 > Project: Arquillian > Issue Type: Feature Request > Components: core > Affects Versions: 1.1.11.Final > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > > With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. > Even though the {{List<TestResult>}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). > The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2065) Combine multiple test results

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2065?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2065: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-core/pull/120 > Combine multiple test results > ----------------------------- > > Key: ARQ-2065 > URL: https://issues.jboss.org/browse/ARQ-2065 > Project: Arquillian > Issue Type: Feature Request > Components: core > Affects Versions: 1.1.11.Final > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > > With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. > Even though the {{List<TestResult>}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). > The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2065) Combine multiple test results

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2065?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak reassigned ARQ-2065: ----------------------------------- Assignee: Bartosz Majsak > Combine multiple test results > ----------------------------- > > Key: ARQ-2065 > URL: https://issues.jboss.org/browse/ARQ-2065 > Project: Arquillian > Issue Type: Feature Request > Components: core > Affects Versions: 1.1.11.Final > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Minor > > With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. > Even though the {{List<TestResult>}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). > The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2065) Combine multiple test results

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-2065: ----------------------------------- Summary: Combine multiple test results Key: ARQ-2065 URL: https://issues.jboss.org/browse/ARQ-2065 Project: Arquillian Issue Type: Feature Request Components: core Affects Versions: 1.1.11.Final Reporter: Bartosz Majsak Priority: Minor With the current implementation in place splitting single test in several executions can only happen from within Arquillian events (so we run n tests from within single test). This in particular happens for running contract tests for Pact, where one test spawns several verifications based on the content of the contract itself. Even though the {{List<TestResult>}} is used as a container object for TestResult instance passed along when Test event is fired, it can happen one test can be fired multiple times (for example in arquillian-algeron). The temporary solution for this problem could be that all the results are collected into one instance of TestResult. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2063) Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2063?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2063: -------------------------------- Fix Version/s: (was: drone_3.0.0.Alpha1) > Upgrade build.gradle file to use Spacelift 17 and Gradle 2.5 > ------------------------------------------------------------ > > Key: ARQ-2063 > URL: https://issues.jboss.org/browse/ARQ-2063 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (ARQ-2062) Upgrade jboss-parent to latest version (21)

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2062?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2062: -------------------------------- Fix Version/s: (was: drone_3.0.0.Alpha1) > Upgrade jboss-parent to latest version (21) > ------------------------------------------- > > Key: ARQ-2062 > URL: https://issues.jboss.org/browse/ARQ-2062 > Project: Arquillian > Issue Type: Component Upgrade > Components: Extension - Drone > Affects Versions: drone_2.0.1.Final > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2016