July 2017 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.s... ] Gerhard Poul commented on ARQ-2130: ----------------------------------- [~vramik] If I understand your issue correctly it is about the arquillian-was-remote-8.5 not being available from the official maven repository? FYI: This is mentioned in the documentation at https://docs.jboss.org/author/display/ARQ/WAS+V8.5+-+Remote which is why I categorized this as an enhancement instead of a bug > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > Priority: Critical > > I'm not able to get > {noformat} > <groupId>org.jboss.arquillian.container</groupId> > <artifactId>arquillian-was-remote-8.5</artifactId> > <version>1.0.0.Beta2</version> > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xm... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-2130: ------------------------------ Issue Type: Enhancement (was: Bug) > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > > I'm not able to get > {noformat} > <groupId>org.jboss.arquillian.container</groupId> > <artifactId>arquillian-was-remote-8.5</artifactId> > <version>1.0.0.Beta2</version> > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xm... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-2130: ------------------------------ Priority: Critical (was: Major) > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Enhancement > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > Priority: Critical > > I'm not able to get > {noformat} > <groupId>org.jboss.arquillian.container</groupId> > <artifactId>arquillian-was-remote-8.5</artifactId> > <version>1.0.0.Beta2</version> > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xm... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2130?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2130: -------------------------------- Affects Version/s: was_1.0.0.Beta2 > Unaccessible arquillian-was-remote-8.5 > -------------------------------------- > > Key: ARQ-2130 > URL: https://issues.jboss.org/browse/ARQ-2130 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Affects Versions: was_1.0.0.Beta2 > Reporter: Vlastislav Ramik > Assignee: Gerhard Poul > > I'm not able to get > {noformat} > <groupId>org.jboss.arquillian.container</groupId> > <artifactId>arquillian-was-remote-8.5</artifactId> > <version>1.0.0.Beta2</version> > {noformat} > It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xm... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2130) Unaccessible arquillian-was-remote-8.5

by Vlastislav Ramik (JIRA)

Vlastislav Ramik created ARQ-2130: ------------------------------------- Summary: Unaccessible arquillian-was-remote-8.5 Key: ARQ-2130 URL: https://issues.jboss.org/browse/ARQ-2130 Project: Arquillian Issue Type: Bug Components: WebSphere Containers Reporter: Vlastislav Ramik Assignee: Gerhard Poul I'm not able to get {noformat} <groupId>org.jboss.arquillian.container</groupId> <artifactId>arquillian-was-remote-8.5</artifactId> <version>1.0.0.Beta2</version> {noformat} It seems that the module is not released: https://github.com/arquillian/arquillian-container-was/blob/master/pom.xm... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-567) Supporting Test Suites (@ArquillianSuite)

by Daniel G (JIRA)

[ https://issues.jboss.org/browse/ARQ-567?page=com.atlassian.jira.plugin.sy... ] Daniel G commented on ARQ-567: ------------------------------ Is the work on this task continued? For us this is a blocker to even think about Arquillian. We have huge EARs where deployments take at least a minute. With hundreds of test classes, this is just impossible to handle with a per test class deployment. > Supporting Test Suites (@ArquillianSuite) > ----------------------------------------- > > Key: ARQ-567 > URL: https://issues.jboss.org/browse/ARQ-567 > Project: Arquillian > Issue Type: Feature Request > Reporter: Mousavi Jahan Abadi S. M. > Assignee: Aslak Knutsen > Fix For: 1.2.0.Alpha1 > > > Currently, it is supported that JUnit test cases being run by Arquillian. This feature request is request for supporting test suites too to be run by Arquillian too. Idea is like: > @RunWith(ArquillianSuite.class) > @Suite.SuiteClasses( { TestCase1.class, TestCase2.class, .... } ) > public class AllTests{ > @Deployment > public static JavaArchive createTestArchive(){ > return ShrinkWrap.create(JavaArchive.class,"test.jar"); > } > } > The advantages of above approach for users of Arquillian framework are: > - Test cases don't needed to be modified to have: "@RunWith(Arquillian.class)" annotation. In other words, test cases will be pure JUnit code, and no Arquillian code (results in less coding for end users). > - It is not necessary to include the static "@Deployment" methods in all test cases any more, and only Test Suite need to define the archieving/deployment related setting/definitions. > The advantage of above approach for framework itself is: > - From performance point-of-view, it becomes possible for Arquillian to deploy all test cases in the Test Suite into J2EE container in one action (one deploy/undeploy for one test suite, instead of mulitple deploy/undeploy for each test case). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2129) Operations Binary download/extraction/marking as executable are not thread-safe

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2129?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2129: -------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-extension-drone/pull/104 > Operations Binary download/extraction/marking as executable are not thread-safe > ------------------------------------------------------------------------------- > > Key: ARQ-2129 > URL: https://issues.jboss.org/browse/ARQ-2129 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.3.1 > Reporter: Matous Jobanek > Assignee: Matous Jobanek > Fix For: drone_2.3.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2129) Operations Binary download/extraction/marking as executable are not thread-safe

by Matous Jobanek (JIRA)

Matous Jobanek created ARQ-2129: ----------------------------------- Summary: Operations Binary download/extraction/marking as executable are not thread-safe Key: ARQ-2129 URL: https://issues.jboss.org/browse/ARQ-2129 Project: Arquillian Issue Type: Bug Components: Extension - Drone Affects Versions: drone_2.3.1 Reporter: Matous Jobanek Assignee: Matous Jobanek Fix For: drone_2.3.2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2109) EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2109?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2109: -------------------------------- Affects Version/s: 1.1.13.Final > EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case > ------------------------------------------------------------------------------------------ > > Key: ARQ-2109 > URL: https://issues.jboss.org/browse/ARQ-2109 > Project: Arquillian > Issue Type: Bug > Components: Runtime Enricher SPI > Affects Versions: 1.1.13.Final > Reporter: Ladislav Thon > > The {{EJBInjectionEnricher}} supports injecting the test instance fields annotated with {{javax.ejb.EJB}}. However, looking at the {{EJBInjectionEnricher.getJndiNamesForAnonymousEJB}} method, it makes too strong assumptions about the JNDI name. Specifically, it assumes the {{test.ear}} and {{test}} names. That doesn't necessarily have to be correct (e.g. WildFly Swarm Arquillian adapter doesn't use these names). There's an easy way to improve this for some situations: also consider the {{java:module}} portable namespace. It can't fix all situations, but it does fix some of them. (For Swarm, it's completely enough, since Swarm doesn't support EARs.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2109) EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2109?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-2109: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > EJBInjectionEnricher makes too strong assumptions about JNDI names in the "anonymous" case > ------------------------------------------------------------------------------------------ > > Key: ARQ-2109 > URL: https://issues.jboss.org/browse/ARQ-2109 > Project: Arquillian > Issue Type: Bug > Components: Runtime Enricher SPI > Affects Versions: 1.1.13.Final > Reporter: Ladislav Thon > > The {{EJBInjectionEnricher}} supports injecting the test instance fields annotated with {{javax.ejb.EJB}}. However, looking at the {{EJBInjectionEnricher.getJndiNamesForAnonymousEJB}} method, it makes too strong assumptions about the JNDI name. Specifically, it assumes the {{test.ear}} and {{test}} names. That doesn't necessarily have to be correct (e.g. WildFly Swarm Arquillian adapter doesn't use these names). There's an easy way to improve this for some situations: also consider the {{java:module}} portable namespace. It can't fix all situations, but it does fix some of them. (For Swarm, it's completely enough, since Swarm doesn't support EARs.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues July 2017