March 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-793) Arquillian config-impl-base is not a part of junit|testng-standalone

by Karel Piwko (JIRA)

Karel Piwko created ARQ-793: ------------------------------- Summary: Arquillian config-impl-base is not a part of junit|testng-standalone Key: ARQ-793 URL: https://issues.jboss.org/browse/ARQ-793 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR7 Reporter: Karel Piwko Priority: Critical When configuration was split, the arquillian-config-impl-base was made a dependency of container only {code} ./container/spi/pom.xml: <artifactId>arquillian-config-impl-base</artifactId>  ./container/impl-base/pom.xml: <artifactId>arquillian-config-impl-base</artifactId>  ./bom/pom.xml: <artifactId>arquillian-config-impl-base</artifactId> ./config/impl-base/pom.xml: <artifactId>arquillian-config-impl-base</artifactId> {code} This means that when no container is on classpath, e.g. standalone mode of junit/testng, ArquillianDescriptor is not created at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] (ARQ-625) EnterpriseArchive deployment with EJB-JAR without descriptor will fail on WAS V8.0

by Gerhard Poul (Created) (JIRA)

EnterpriseArchive deployment with EJB-JAR without descriptor will fail on WAS V8.0 ---------------------------------------------------------------------------------- Key: ARQ-625 URL: https://issues.jboss.org/browse/ARQ-625 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: WebSphere Containers Environment: WAS V8.0.0.1 Reporter: Gerhard Poul Assignee: Gerhard Poul Priority: Minor A deployment of an EnterpriseArchive that contains an EJB-JAR without a descriptor will fail on WAS V8.0. The errors being logged are from WTP and have message codes of IWAE0006E and IWAE0023E. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (ARQ-337) Create a Context/Scope activation/deactivation abstraction for CDI

by Aslak Knutsen (JIRA)

Create a Context/Scope activation/deactivation abstraction for CDI ------------------------------------------------------------------- Key: ARQ-337 URL: https://jira.jboss.org/browse/ARQ-337 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen We need to have a stable and reliable api exposed by arquillian over the different container types and CDI impls to control the activation and deactivation of different scopes -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
7
0 / 0

[JBoss JIRA] (ARQAJO-101) Using of JQuery 1.5 causes that JQuery selectors are not escaped properly

by Juraj Huska (Created) (JIRA)

Using of JQuery 1.5 causes that JQuery selectors are not escaped properly ------------------------------------------------------------------------- Key: ARQAJO-101 URL: https://issues.jboss.org/browse/ARQAJO-101 Project: Arquillian Ajocado Issue Type: Bug Components: core Affects Versions: 1.0.0.CR2 Environment: Ajocado 1.0.0-SNAPSHOT Reporter: Juraj Huska Assignee: Lukáš Fryč When I want to use JQuery selectors in my tests, I can not just type: {code} jq("input[id$=attributes:handleClassInput]"); {code} since it will not be properly escaped, and thus will fail to create this JQuery Locator. I can avoid it by escaping it manually, but it will too much work for my big test suite, which already worked with RichFaces Selenium properly. The reason why *it works in RichFaces Selenium is that it uses JQuery v1.4.4 and Ajocado is using 1.5.* With 1.4.4 it works fine also in Ajocado. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
14
0 / 0

[JBoss JIRA] (ARQAJO-111) Support Thread-Local Context with Selenium 2

by Lukáš Fryč (Created) (JIRA)

Support Thread-Local Context with Selenium 2 -------------------------------------------- Key: ARQAJO-111 URL: https://issues.jboss.org/browse/ARQAJO-111 Project: Arquillian Ajocado Issue Type: Feature Request Components: core Reporter: Lukáš Fryč Fix For: 2.0-Tracking -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-520) ResolutionException for artifact org.jboss.arquillian.osgi:arquillian-osgi-bundle:jar

by Thomas Diesler (JIRA)

ResolutionException for artifact org.jboss.arquillian.osgi:arquillian-osgi-bundle:jar ------------------------------------------------------------------------------------- Key: ARQ-520 URL: https://issues.jboss.org/browse/ARQ-520 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Affects Versions: osgi_1.0.0.CR2 Reporter: Thomas Diesler Assignee: Thomas Diesler When the JBoss Nexus repo is not defined in ~/.m2/settings.xml we get org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to resolve an artifact at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:324) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:70) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl$MavenArtifactBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:471) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl$MavenArtifactBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:405) at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.installBundle(EmbeddedDeployableContainer.java:182) at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.start(EmbeddedDeployableContainer.java:108) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (ARQ-338) All test case to specify a list of support bundles

by Thomas Diesler (JIRA)

All test case to specify a list of support bundles -------------------------------------------------- Key: ARQ-338 URL: https://jira.jboss.org/browse/ARQ-338 Project: Arquillian Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler ARQ OSGi tests may have the need to install the arquillian-osgi-bundle before they can run -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-301) Create a Spring framework integration (for non-standalone containers)

by Dan Allen (JIRA)

Create a Spring framework integration (for non-standalone containers) --------------------------------------------------------------------- Key: ARQ-301 URL: https://jira.jboss.org/browse/ARQ-301 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Implement a Spring framework integration. We want to be able to execute Spring tests in non-standalone containers (e.g., Java EE, Servlet). These containers don't have the Spring framework programming model out of the box. So we need to ship it to the server along with the test. That's the purpose of an Arquillian framework integration, so it's an ideal solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
12
0 / 0

[JBoss JIRA] Created: (ARQ-454) Console log output in Arquillian and JBoss Container Managed 6

by Ove Ranheim (JIRA)

Console log output in Arquillian and JBoss Container Managed 6 -------------------------------------------------------------- Key: ARQ-454 URL: https://issues.jboss.org/browse/ARQ-454 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: JBoss Containers Affects Versions: 1.0.0.Alpha5 Reporter: Ove Ranheim It should be possible to configure console log output in in arquillian.xml, so the logger would redirected server.log to console output. This would require a change in ServiceController: http://anonsvn.jboss.org/repos/jbossas/projects/server-manager/tags/1.0.4... For Bamboo users; Bamboo Jobs are sniffing on the console log output and is sensitive about that, so to get proper integration tests running, this is a requirement. This issue should probably be raised with Ryan Campbell. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-583) When missing a vital part of an ARQ test a meaningful exception should be thrown

by Jason Porter (JIRA)

When missing a vital part of an ARQ test a meaningful exception should be thrown -------------------------------------------------------------------------------- Key: ARQ-583 URL: https://issues.jboss.org/browse/ARQ-583 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR4 Reporter: Jason Porter For example if you're missing a @Deployment, an error stating as much should be thrown. There may be some others, but this one comes to the top. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2012