November 2013 - arquillian-issues

[JBoss JIRA] (ARQ-986) Add more advanced exception matching logic in @ShouldThrowException

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-986?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-986: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Add more advanced exception matching logic in @ShouldThrowException > ------------------------------------------------------------------- > > Key: ARQ-986 > URL: https://issues.jboss.org/browse/ARQ-986 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployable Containers SPI > Reporter: Dan Allen > Assignee: Ivan St. Ivanov > Priority: Minor > Fix For: 1.1.2.Final > > > The @ShouldThrowException assertion for a deployment should support more intelligent exception matching similar to what was implemented for Seam Catch. A single exception class compared to the outer most exception often isn't sufficient. If nothing else, we should unwrap the exception and try the match for each exception in the stack. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1471) Provide documentation for @Observes annotation

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1471?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1471. ------------------------------ Resolution: Done > Provide documentation for @Observes annotation > ---------------------------------------------- > > Key: ARQ-1471 > URL: https://issues.jboss.org/browse/ARQ-1471 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.1.Final > Reporter: Karel Piwko > Fix For: 1.1.2.Final > > > @Observes annotation should contain a documentation. > The most annoying fact is that precedence does not explain its value, that is that bigger value means being executed first. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1573) Prepare 1.1.2.Final release

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1573?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1573. ------------------------------ Assignee: Aslak Knutsen Resolution: Done pushed to nexus > Prepare 1.1.2.Final release > --------------------------- > > Key: ARQ-1573 > URL: https://issues.jboss.org/browse/ARQ-1573 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Base Implementation > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 1.1.2.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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1573) Prepare 1.1.2.Final release

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1573: ---------------------------------- Summary: Prepare 1.1.2.Final release Key: ARQ-1573 URL: https://issues.jboss.org/browse/ARQ-1573 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: Base Implementation Reporter: Aslak Knutsen Fix For: 1.1.2.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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1471) Provide documentation for @Observes annotation

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1471?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1471: ------------------------------- Fix Version/s: 1.1.2.Final (was: 2.0.0.Beta1) > Provide documentation for @Observes annotation > ---------------------------------------------- > > Key: ARQ-1471 > URL: https://issues.jboss.org/browse/ARQ-1471 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.1.Final > Reporter: Karel Piwko > Fix For: 1.1.2.Final > > > @Observes annotation should contain a documentation. > The most annoying fact is that precedence does not explain its value, that is that bigger value means being executed first. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-986) Add more advanced exception matching logic in @ShouldThrowException

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-986?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-986: ------------------------------ Fix Version/s: 1.1.2.Final (was: 2.0.0.Beta1) > Add more advanced exception matching logic in @ShouldThrowException > ------------------------------------------------------------------- > > Key: ARQ-986 > URL: https://issues.jboss.org/browse/ARQ-986 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployable Containers SPI > Reporter: Dan Allen > Assignee: Ivan St. Ivanov > Priority: Minor > Fix For: 1.1.2.Final > > > The @ShouldThrowException assertion for a deployment should support more intelligent exception matching similar to what was implemented for Seam Catch. A single exception class compared to the outer most exception often isn't sufficient. If nothing else, we should unwrap the exception and try the match for each exception in the stack. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1572) Marry Persistence and JRebel extensions

by Bernard Labno (JIRA)

Bernard Labno created ARQ-1572: ---------------------------------- Summary: Marry Persistence and JRebel extensions Key: ARQ-1572 URL: https://issues.jboss.org/browse/ARQ-1572 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha6 Reporter: Bernard Labno Assignee: Bartosz Majsak JRebel extension currently does not pick up changes in datasets. Here is how it works: If there is no target/jrebel-temp/.../*.meta file for given deployment then it assumes user wants full redeploy. If such file is present then deployment is blocked and tests are run at once. JRebel extension also checks if there is a rebel.xml file in the archive. If not then it generates such file based on exact content of the archive and explodes archive into target/jrebel-temp/*. Now the problem is that if resource is not in the archive then it will not be included in generated rebel.xml and thus won't be picked up by JRebel. Datasets are now automatically packed inside WEB-INF/lib/randomUUID.jar. JRebel will not substitute resources or classes from bundled libs. We could generate additional rebel.xml for that but I'd have to know what is the name of such archive and we would tightly couple both extensions. It would be easiest if Persistence ext would pack datasets directly into WE-INF/classes. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1571) Remove API 10 from default platform

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1571?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1571. ------------------------------------ Resolution: Done > Remove API 10 from default platform > ----------------------------------- > > Key: ARQ-1571 > URL: https://issues.jboss.org/browse/ARQ-1571 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > Related to fix ARQ-1568, it is no longer necessary to check for API 10 presence. Default behavior could simply be to find out newest (highest) API level if no level is specified to create the AVD. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1077) Persistence Plugin does not work with Drone/Graphene

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/ARQ-1077?page=com.atlassian.jira.plugin.s... ] Bernard Labno commented on ARQ-1077: ------------------------------------ Oh Mighty Bartosz, please show us your mercy and prioritize on this task. This is so much needed for Arquillian REST extension. > Persistence Plugin does not work with Drone/Graphene > ---------------------------------------------------- > > Key: ARQ-1077 > URL: https://issues.jboss.org/browse/ARQ-1077 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Drone, Extension - Persistence > Environment: JBoss AS 7 Container > Reporter: Bryan Saunders > Assignee: Bartosz Majsak > Labels: drone, persistence > > Persistence Extension does not execute when being used with the Drone/Graphene extensions. When you run the tests in Client Mode the @UsingDataSet annotations do not trigger and populate the database. @ApplyScriptBefore also does not work. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1571) Remove API 10 from default platform

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1571?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reassigned ARQ-1571: -------------------------------------- Assignee: Stefan Miklosovic > Remove API 10 from default platform > ----------------------------------- > > Key: ARQ-1571 > URL: https://issues.jboss.org/browse/ARQ-1571 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha2 > Reporter: Karel Piwko > Assignee: Stefan Miklosovic > > Related to fix ARQ-1568, it is no longer necessary to check for API 10 presence. Default behavior could simply be to find out newest (highest) API level if no level is specified to create the AVD. -- 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

11 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2013