March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1712) Support for process identification

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1712?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1712: ----------------------------- Summary: Support for process identification (was: Support for process identification/timespamp) Fix Version/s: spacelift_1.0.0.Alpha2 Description: Spacelift currently always outputs process identification (based on first argument). It should be possible to: * make this string configurable * disable this altogether This will help make logs more readable. was: Spacelift currently always outputs process identification (based on first argument). It should be possible to: * make this string configurable * disable this altogether * add timestamp to the output There should be both API and system property approach - for disabling and timespamps. This will help make logs more readable. Assignee: Karel Piwko > Support for process identification > ---------------------------------- > > Key: ARQ-1712 > URL: https://issues.jboss.org/browse/ARQ-1712 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha1 > Reporter: Karel Piwko > Assignee: Karel Piwko > Fix For: spacelift_1.0.0.Alpha2 > > > Spacelift currently always outputs process identification (based on first argument). > It should be possible to: > * make this string configurable > * disable this altogether > This will help make logs more readable. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1654. ------------------------------ > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit$\*$ methods should probably be enough. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1071. ------------------------------ > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final, 1.1.3.Final > Reporter: Rick-Rainer Ludwig > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1012) org.junit.Assume API not working

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1012?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1012. ------------------------------ > org.junit.Assume API not working > -------------------------------- > > Key: ARQ-1012 > URL: https://issues.jboss.org/browse/ARQ-1012 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Integration Test Suite > Affects Versions: 1.0.0.Final > Environment: Windows 7, Java 1.7 > Reporter: Karsten Ohme > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Hi, > my test classes are annotated with @RunWith(Arquillian.class) > I try to use the newer JUnit org.junit.Assume API. > The problem ist, that the outcome of the test seems to be ignored, e.g. org.junit.Assume.assertNonNull does not fail and throws an exception. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1641) Tests with failed assumptions do not show up as skipped

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1641?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1641. ------------------------------ > Tests with failed assumptions do not show up as skipped > ------------------------------------------------------- > > Key: ARQ-1641 > URL: https://issues.jboss.org/browse/ARQ-1641 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.2.Final > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > A test like this reports success instead of skipped. > Occurs with managed wildfly, tomcat, karaf > {code} > @Test > public void foo() throws Exception { > Assume.assumeTrue(false); > > // test code that should only run when the above is true > } > {code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1733) Update to latest ShrinkWrap|Resolver

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1733?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1733. ------------------------------ > Update to latest ShrinkWrap|Resolver > ------------------------------------ > > Key: ARQ-1733 > URL: https://issues.jboss.org/browse/ARQ-1733 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1733) Update to latest ShrinkWrap|Resolver

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1733?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1733. -------------------------------- Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/392e24422d40c8df573c... > Update to latest ShrinkWrap|Resolver > ------------------------------------ > > Key: ARQ-1733 > URL: https://issues.jboss.org/browse/ARQ-1733 > Project: Arquillian > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1733) Update to latest ShrinkWrap|Resolver

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1733: ---------------------------------- Summary: Update to latest ShrinkWrap|Resolver Key: ARQ-1733 URL: https://issues.jboss.org/browse/ARQ-1733 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.3.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.1.4.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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1732) Support the use of Future from ExecutorService in InstanceProducer

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1732: ---------------------------------- Summary: Support the use of Future from ExecutorService in InstanceProducer Key: ARQ-1732 URL: https://issues.jboss.org/browse/ARQ-1732 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.1.4.Final Reporter: Aslak Knutsen Fix For: 2.0.0.Beta1 Open InstanceProducer with a option to set(Future<T>). @Inject Instance<T> inst; inst.get() would call future.get(); Would allow for background creation of any exposed contextual object. {code} @Inject @TestScoped private InstanceProducer<T> producer; @Inject private Instance<ExecutorService> executor; producer.set(executor.submit(Callable<T>)) {code} Questions: When is fire(T) called, when set(Future<T>) as now, or when Future is resovled? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1654. -------------------------------- Fix Version/s: 1.1.4.Final (was: 2.0.0.Beta1) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-core/commit/f8ec8e37bc8d1a195e84... > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit$\*$ methods should probably be enough. -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2014