March 2016 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-2021) Allow extending ArquillianConfig service

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/ARQ-2021?page=com.atlassian.jira.plugin.s... ] Arcadiy Ivanov commented on ARQ-2021: ------------------------------------- Also please cut a release if the change is approved. > Allow extending ArquillianConfig service > ---------------------------------------- > > Key: ARQ-2021 > URL: https://issues.jboss.org/browse/ARQ-2021 > Project: Arquillian > Issue Type: Feature Request > Components: JBoss AS Containers > Reporter: Arcadiy Ivanov > Priority: Minor > > Need to be able to add dependencies to ArquillianConfig MSC service and inject values from other services. > Need to allow adding dependencies to Arquillian Service archive. > Fix a broken switch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2021) Allow extending ArquillianConfig service

by Arcadiy Ivanov (JIRA)

[ https://issues.jboss.org/browse/ARQ-2021?page=com.atlassian.jira.plugin.s... ] Arcadiy Ivanov updated ARQ-2021: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/wildfly/wildfly-arquillian/pull/68 > Allow extending ArquillianConfig service > ---------------------------------------- > > Key: ARQ-2021 > URL: https://issues.jboss.org/browse/ARQ-2021 > Project: Arquillian > Issue Type: Feature Request > Components: JBoss AS Containers > Reporter: Arcadiy Ivanov > Priority: Minor > > Need to be able to add dependencies to ArquillianConfig MSC service and inject values from other services. > Need to allow adding dependencies to Arquillian Service archive. > Fix a broken switch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2021) Allow extending ArquillianConfig service

by Arcadiy Ivanov (JIRA)

Arcadiy Ivanov created ARQ-2021: ----------------------------------- Summary: Allow extending ArquillianConfig service Key: ARQ-2021 URL: https://issues.jboss.org/browse/ARQ-2021 Project: Arquillian Issue Type: Feature Request Components: JBoss AS Containers Reporter: Arcadiy Ivanov Priority: Minor Need to be able to add dependencies to ArquillianConfig MSC service and inject values from other services. Need to allow adding dependencies to Arquillian Service archive. Fix a broken switch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2018) Upgrade Karaf to latest release for arquillian-container-karaf-managed

by Steve Storck (JIRA)

[ https://issues.jboss.org/browse/ARQ-2018?page=com.atlassian.jira.plugin.s... ] Steve Storck edited comment on ARQ-2018 at 3/7/16 4:15 PM: ----------------------------------------------------------- [~thomas.diesler]: I missed that file on the original commit. Updated the pull request, so it should be good now. was (Author: stevestorck): I missed that file on the original commit. Updated the pull request, so it should be good now. > Upgrade Karaf to latest release for arquillian-container-karaf-managed > ---------------------------------------------------------------------- > > Key: ARQ-2018 > URL: https://issues.jboss.org/browse/ARQ-2018 > Project: Arquillian > Issue Type: Enhancement > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Reporter: Steve Storck > > The current version of the managed Karaf container is 2.3.3. This was released in 2013, so it is quite outdated. The latest release is 4.0.4, which was released in early 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2016) arquillian-osgi-bundle includes dependencies but does not export them

by Steve Storck (JIRA)

[ https://issues.jboss.org/browse/ARQ-2016?page=com.atlassian.jira.plugin.s... ] Steve Storck commented on ARQ-2016: ----------------------------------- [~thomas.diesler]: I cannot change the assignee at all, so I'll just comment here and link you when I need that to be done, if that's all right with you. By the way, I need some information with regard to how auxiliary archives are deployed to a container (particularly to an OSGi container) and if they are available in the same way that all bundles are available, with their exports available to the tests. The spock extension that I want to use deploys an auxiliary archive, and the exports seem to be unavailable in the container when my tests are deployed. I have searched with Google quite a bit, and I have looked into the code, but I am not finding anything definitive. > arquillian-osgi-bundle includes dependencies but does not export them > --------------------------------------------------------------------- > > Key: ARQ-2016 > URL: https://issues.jboss.org/browse/ARQ-2016 > Project: Arquillian > Issue Type: Feature Request > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Environment: Under Linux, and inside Karaf 4.x > Reporter: Steve Storck > > When the arquillian-container-osgi extension is deployed, it also deploys the arquillian-osgi-bundle. This bundle exposes a few APIs, but it contains (and does not expose) some of the implementation and SPI packages. This effectively results in only being able to use the provided JUnitBundleTestRunner extension. I want to use the arquillian-testrunner-spock extension, but it always fails because I have to deploy the test SPI bundle with my test jar, and it conflicts with those packages that the arquillian-osgi-bundle uses internally. This causes an exception to be thrown that complains that the EventTestRunnerAdaptor implementation is not an instance of the TestRunnerAdaptor interface. The chain of events that results in the exception is as follows: > {code:java|title=ArquillianSputnik.java (arquillian-testrunner-spock)|borderStyle=solid} > package org.jboss.arquillian.spock; > public class ArquillianSputnik extends Sputnik { > import org.jboss.arquillian.test.spi.TestRunnerAdaptor; > import org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder; > // Methods and fields omitted for brevity, but you can see that the > // proper packages are imported > public void run(RunNotifier notifier) { > // Code omitted for brevity > final TestRunnerAdaptor adaptor = TestRunnerAdaptorBuilder.build(); > // More code omitted for brevity > } > } > {code} > {code:java|title=EventTestRunnerAdaptorBuilder.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > public class TestRunnerAdaptorBuilder { > private static final String DEFAULT_EXTENSION_CLASS = > "org.jboss.arquillian.core.impl.loadable.LoadableExtensionLoader"; > private static final String TEST_RUNNER_IMPL_CLASS = > "org.jboss.arquillian.test.impl.EventTestRunnerAdaptor"; > public static TestRunnerAdaptor build() { > // omitted lines for brevity > ManagerBuilder builder = ManagerBuilder.from() > .extension(SecurityActions.loadClass(DEFAULT_EXTENSION_CLASS)); > return SecurityActions.newInstance( > TEST_RUNNER_IMPL_CLASS, > new Class<?>[] {ManagerBuilder.class}, > new Object[] {builder}, > TestRunnerAdaptor.class); > } > } > {code} > {code:java|title=SecurityActions.java (arquillian-core test/spi)|borderStyle=solid} > package org.jboss.arquillian.test.spi; > final class SecurityActions { > static <T> T newInstance(final String className, > final Class<?>[] argumentTypes, > final Object[] arguments, > final Class<T> expectedType) { > @SuppressWarnings("unchecked") > Class<T> implClass = (Class<T>) loadClass(className); > if (!expectedType.isAssignableFrom(implClass)) { > throw new RuntimeException("Loaded class " + > className + > " is not of expected type " + > expectedType); > } > return newInstance(implClass, argumentTypes, arguments); > } > } > {code} > I think that the best solution would be to completely decouple the JUnitTestRunner from the container modules, or at the very least, it would be good to change the <_exportcontents> to export most (or all) of the embedded dependency packages so that users can make use of other extensions, or build their own. > Edit: After some more thought, it would be really nice to make test extensions loadable (with a default if it is unspecified, of course). I don't know enough about the code base (yet) to say if it would be best to do this via an annotation, or if pluggability would be better leveraged somewhere else in the framework. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2018) Upgrade Karaf to latest release for arquillian-container-karaf-managed

by Steve Storck (JIRA)

[ https://issues.jboss.org/browse/ARQ-2018?page=com.atlassian.jira.plugin.s... ] Steve Storck commented on ARQ-2018: ----------------------------------- I missed that file on the original commit. Updated the pull request, so it should be good now. > Upgrade Karaf to latest release for arquillian-container-karaf-managed > ---------------------------------------------------------------------- > > Key: ARQ-2018 > URL: https://issues.jboss.org/browse/ARQ-2018 > Project: Arquillian > Issue Type: Enhancement > Components: OSGi Containers > Affects Versions: osgi_2.1.0.Final > Reporter: Steve Storck > > The current version of the managed Karaf container is 2.3.3. This was released in 2013, so it is quite outdated. The latest release is 4.0.4, which was released in early 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.s... ] Gerhard Poul closed ARQ-1961. ----------------------------- Resolution: Cannot Reproduce > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > Attachments: DaveWesterman_arquillian-enhanced-trace.zip > > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2020) wlp-remote arquillian support for wlp server assembly

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2020?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-2020: ------------------------------ Description: Websphere liberty Maven plugin allows you to package a liberty server assembly and deploy it to repo Manager like Nexus: https://github.com/WASdev/ci.maven#liberty-assembly It would be good if the Liberty Arquillian container could be configured to download and use this liberty assembly. This mean each environment the tests run on would'nt need to be pre-installed with a Liberty server. was: Websphere liberty Maven plugin allows you to package a liberty server assembly and deploy it to repo Manager like Nexus: https://github.com/WASdev/ci.maven#liberty-assembly It would be good if the Liberty Arquillian container could be configured to download and use this liberty assembly. https://github.com/arquillian/arquillian-container-was/tree/master/wlp-ma... This mean each environment the tests run on would'nt need to be pre-installed with a Liberty server. > wlp-remote arquillian support for wlp server assembly > ----------------------------------------------------- > > Key: ARQ-2020 > URL: https://issues.jboss.org/browse/ARQ-2020 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: D K > Assignee: Gerhard Poul > > Websphere liberty Maven plugin allows you to package a liberty server assembly and deploy it to repo Manager like Nexus: > https://github.com/WASdev/ci.maven#liberty-assembly > It would be good if the Liberty Arquillian container could be configured to download and use this liberty assembly. > This mean each environment the tests run on would'nt need to be pre-installed with a Liberty server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2020) wlp-remote arquillian support for wlp server assembly

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2020?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-2020: ------------------------------ Reporter: Gerhard Poul (was: D K) > wlp-remote arquillian support for wlp server assembly > ----------------------------------------------------- > > Key: ARQ-2020 > URL: https://issues.jboss.org/browse/ARQ-2020 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Gerhard Poul > Assignee: Gerhard Poul > > Websphere liberty Maven plugin allows you to package a liberty server assembly and deploy it to repo Manager like Nexus: > https://github.com/WASdev/ci.maven#liberty-assembly > It would be good if the Liberty Arquillian container could be configured to download and use this liberty assembly. > This mean each environment the tests run on would'nt need to be pre-installed with a Liberty server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2020) wlp-remote arquillian support for wlp server assembly

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2020?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-2020: ------------------------------ Fix Version/s: (was: was_1.0.0.next) > wlp-remote arquillian support for wlp server assembly > ----------------------------------------------------- > > Key: ARQ-2020 > URL: https://issues.jboss.org/browse/ARQ-2020 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: D K > Assignee: Gerhard Poul > > Websphere liberty Maven plugin allows you to package a liberty server assembly and deploy it to repo Manager like Nexus: > https://github.com/WASdev/ci.maven#liberty-assembly > It would be good if the Liberty Arquillian container could be configured to download and use this liberty assembly. > This mean each environment the tests run on would'nt need to be pre-installed with a Liberty server. -- 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 March 2016