April 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-826) arquillian-protocol.war's web.xml is not build correctly if test-runner entries are already existent (mutiple entries possible)

by Patrick T (JIRA)

Patrick T created ARQ-826: ----------------------------- Summary: arquillian-protocol.war's web.xml is not build correctly if test-runner entries are already existent (mutiple entries possible) Key: ARQ-826 URL: https://issues.jboss.org/browse/ARQ-826 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Packaging Enricher SPI, Runtime Enricher SPI Affects Versions: 1.0.0.CR7 Environment: Jboss 4.3 EAP/4.2.1, Java 1.5 Reporter: Patrick T web.xml of arquillian-protocol.war, thats added during test-deployment, is not checked for content. Therefore multiple testrunner-entries may occur, resulting in an exception, if an enriched file is tried to get deployed again. -- 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

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] (ARQAJO-129) Blog about renaming to Graphene

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQAJO-129: --------------------------------- Summary: Blog about renaming to Graphene Key: ARQAJO-129 URL: https://issues.jboss.org/browse/ARQAJO-129 Project: Arquillian Ajocado Issue Type: Sub-task Reporter: Lukáš Fryč Fix For: 1.0.0.CR3 -- 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

12 years, 9 months

1
3
0 / 0

[JBoss JIRA] (ARQ-688) Arquillian can't start EAP 5.1

by Tomáš Schlosser (Created) (JIRA)

Arquillian can't start EAP 5.1 ------------------------------ Key: ARQ-688 URL: https://issues.jboss.org/browse/ARQ-688 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Environment: Arquillian 1.0.0.CR6 JBoss EAP 5.1.1 Reporter: Tomáš Schlosser When using JBoss container in manual mode and try to start it, the command throw exception because JBoss EAP does not start within 30 seconds. No command response within timeout of 30000 ms. org.jboss.arquillian.protocol.servlet.runner.ServletCommandService.execute(ServletCommandService.java:60) at org.jboss.arquillian.container.test.impl.client.container.ContainerContainerController.start(ContainerContainerController.java:45) at org.jboss.qa.brms.bre.container.TransactionsTest.foo(TransactionsTest.java:16) 98 lines not shown -- 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

12 years, 9 months

4
3
0 / 0

[JBoss JIRA] (ARQ-855) Create a Drone logo

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/ARQ-855?page=com.atlassian.jira.plugin.sy... ] Dan Allen deleted ARQ-855: -------------------------- > Create a Drone logo > ------------------- > > Key: ARQ-855 > URL: https://issues.jboss.org/browse/ARQ-855 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Dan Allen > Assignee: Karel Piwko > Priority: Optional > Labels: design > > Create a logo for Arquillian Drone. The logo will be used on the website, in blogs and press releases and in presentations. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-855) Create a Drone logo

by Dan Allen (JIRA)

Dan Allen created ARQ-855: ----------------------------- Summary: Create a Drone logo Key: ARQ-855 URL: https://issues.jboss.org/browse/ARQ-855 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Drone Reporter: Dan Allen Assignee: Karel Piwko Priority: Optional Create a logo for Arquillian Drone. The logo will be used on the website, in blogs and press releases and in presentations. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-748) Update Arquillian test dependencies to be able to do a clean build against Maven Central

by Karel Piwko (JIRA)

Karel Piwko created ARQ-748: ------------------------------- Summary: Update Arquillian test dependencies to be able to do a clean build against Maven Central Key: ARQ-748 URL: https://issues.jboss.org/browse/ARQ-748 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Infrastructure Affects Versions: 1.0.0.CR7 Reporter: Karel Piwko Assignee: Karel Piwko * CDI TestEnricher Current version 1.1.0.Final is not available in Maven Central. Note that the change would require an update to related slf4j bindings to 1.6.1. * Servlet Protocol jboss.web:servlet-api:jar:3.0.0.alpha-25 in not available in Maven Central to be replaced with {code:xml} <dependency> <groupId>org.jboss.spec.javax.servlet</groupId> <artifactId>jboss-servlet-api_3.0_spec</artifactId> <version>1.0.0.Final</version> </dependency> {code} * Arquillian Example Domain/JUnit/TestNG same as protocol and org.jboss.ejb3:jboss-ejb3-api:jar:3.1.0 replaced with {code:xml} <dependency> <groupId>org.jboss.spec.javax.ejb</groupId> <artifactId>jboss-ejb-api_3.1_spec</artifactId> <version>1.0.1.Final</version> </dependency> {code} and javax.jms:jms with {code:xml} <dependency> <groupId>org.jboss.spec.javax.jms</groupId> <artifactId>jboss-jms-api_1.1_spec</artifactId> <version>1.0.0.Final</version> </dependency> {code} -- 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

12 years, 9 months

2
6
0 / 0

[JBoss JIRA] (ARQ-850) Should support custom container mode

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-850: --------------------------------- Summary: Should support custom container mode Key: ARQ-850 URL: https://issues.jboss.org/browse/ARQ-850 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR7 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Final A 4. container mode 'custom' should be added where Arquillian only attempts to 'setup' the Container. All other operations are left up to the user/extension. -- 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

12 years, 9 months

1
3
0 / 0

[JBoss JIRA] (ARQ-715) Add a getter for ProtocolMetaData.contexts

by Alexis Hassler (Created) (JIRA)

Add a getter for ProtocolMetaData.contexts ------------------------------------------ Key: ARQ-715 URL: https://issues.jboss.org/browse/ARQ-715 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Base Implementation Reporter: Alexis Hassler Having a ProtocolMetaData.getContexts() method would help to safely clone (and rewrite) metadata in extensions. Without that method, we could forget some contexts. -- 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

12 years, 9 months

4
5
0 / 0

[JBoss JIRA] (ARQ-792) Honor system property for debugging Arquillian internals

by Karel Piwko (JIRA)

Karel Piwko created ARQ-792: ------------------------------- Summary: Honor system property for debugging Arquillian internals Key: ARQ-792 URL: https://issues.jboss.org/browse/ARQ-792 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR7 Reporter: Karel Piwko Often an extension developer wants to know what's going in Arquillian. There is a way how to enable a debug mode, however it requires a complete build of Arquillian from source: It should honor a property instead: {code} mvn test -Darquillian.debug=true {code} -- 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

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] (ARQ-670) Arquillian Servlet's context root should be "test", not "test.war", in EAR

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-670?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-670. ----------------------------- > Arquillian Servlet's context root should be "test", not "test.war", in EAR > -------------------------------------------------------------------------- > > Key: ARQ-670 > URL: https://issues.jboss.org/browse/ARQ-670 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Protocol SPIs and Implementation > Affects Versions: 1.0.0.CR6 > Reporter: Alexandre Gattiker > Assignee: Aslak Knutsen > Fix For: 1.0.0.CR8 > > > As the Arquillian JMX protocol doesn't currently work for EARs in AS7 (AS7-1696), I tried using the Servlet 3.0 protocol. However the test runner fails to contact the servlet: > java.lang.IllegalStateException: Error launching request at http://127.0.0.1:8080/test/ArquillianServletRunner?outputMode=serializedO.... No result returned > at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.executeWithRetry(ServletMethodExecutor.java:158) > at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:118) > ... 75 more > The servlet is actually deployed at: > http://127.0.0.1:8080/test.war/ArquillianServletRunner > Because Arquillian has added the following to my EAR's application.xml: > <module> > <web> > <web-uri>test.war</web-uri> > <context-root>test.war</context-root> > </web> > </module> > This can be traced to org.jboss.arquillian.protocol.servlet.v_3.ServletProtocolDeploymentPackager: > > applicationXml.webModule(wrappedWar.getName(), wrappedWar.getName()); -- 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

12 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 April 2012