March 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1302) Support Weld 2.x

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1302?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1302: ------------------------------- Fix Version/s: weld_1.0.0.CR6 (was: weld_1.0.0.Final) > Support Weld 2.x > ---------------- > > Key: ARQ-1302 > URL: https://issues.jboss.org/browse/ARQ-1302 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: weld_1.0.0.CR6 > > > ARQ-1168 Added a tight dependency on the BeansXml API from Weld Bootstrap SPI. This SPI has changed in the Weld 2.x branch which cause the Container to fail runtime. > The reason for the tight dependency is to support merging duplicate entries in beans.xml when using a FlatDeployment structure. > Weld 2.x Bootstrap has added support for this feature via the new parse(beans.xml, merge) method. > Update the weld containers to support the old and new way of merging the beans.xml. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-841) Should not scan for classes in Archive if it contains no beans.xml

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-841?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-841: ------------------------------ Fix Version/s: weld_1.0.0.CR6 (was: weld_1.0.0.Final) > Should not scan for classes in Archive if it contains no beans.xml > ------------------------------------------------------------------ > > Key: ARQ-841 > URL: https://issues.jboss.org/browse/ARQ-841 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Aslak Knutsen > Assignee: Matt Benson > Labels: starter > Fix For: weld_1.0.0.CR6 > > Attachments: pom.xml > > > A deployment with no beans.xml should not result in Beans being registered in the Weld Container. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1348) Prepare Weld CR6

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1348: ---------------------------------- Summary: Prepare Weld CR6 Key: ARQ-1348 URL: https://issues.jboss.org/browse/ARQ-1348 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: Weld Containers Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: weld_1.0.0.CR6 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1347) Not possible to run a spock test w/o arquillian

by Fabian Schwarzer (JIRA)

Fabian Schwarzer created ARQ-1347: ------------------------------------- Summary: Not possible to run a spock test w/o arquillian Key: ARQ-1347 URL: https://issues.jboss.org/browse/ARQ-1347 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Spock TestRunner Reporter: Fabian Schwarzer Assignee: Bartosz Majsak If I use spock to implement my unit tests and my arquillian tests, it is not possible to run spock (unit) tests w/o Arquillian any more. Afaik this is possible if JUnit is used. Annotate them with @Arquillian -> running as Arquillian test; Don't annotate them -> running as "normal" unit tests. I would like to have this behaviour with spock as well. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1346) cannot run ejb 3.x integrate test using arquillian-glassfish-managed-3.1

by Tang Yong (JIRA)

[ https://issues.jboss.org/browse/ARQ-1346?page=com.atlassian.jira.plugin.s... ] Tang Yong updated ARQ-1346: --------------------------- Attachment: javaeewithgf.zip server.log > cannot run ejb 3.x integrate test using arquillian-glassfish-managed-3.1 > ------------------------------------------------------------------------ > > Key: ARQ-1346 > URL: https://issues.jboss.org/browse/ARQ-1346 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: GlassFish Containers > Affects Versions: 1.0.0.CR1 > Environment: 1 Windows XP > 2 Glassfish 3.1.2.2 or current v4 snapshot > Reporter: Tang Yong > Priority: Critical > Attachments: javaeewithgf.zip, server.log > > > Today, I trigger a problem[1] about arquillian glassfish integrated test > again on Glassfish 3.1.2.2 or current Glassfish 4.0-SNAPSHOT. > [1]: > http://stackoverflow.com/questions/8677780/cannot-deploy-jar-file-with-ej... > The attachment(javaeewithgf.zip) is my modified sample based on > "Enterprise JavaBeans 3.1, 6th Edition " using > arquillian-glassfish-managed-3.1. > And the attachment(server.log) is the result of running on current > Glassfish 4.0-SNAPSHOT. > The issue is very critical because test scene is very simple. > I will upload the attachments. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1346) cannot run ejb 3.x integrate test using arquillian-glassfish-managed-3.1

by Tang Yong (JIRA)

Tang Yong created ARQ-1346: ------------------------------ Summary: cannot run ejb 3.x integrate test using arquillian-glassfish-managed-3.1 Key: ARQ-1346 URL: https://issues.jboss.org/browse/ARQ-1346 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.CR1 Environment: 1 Windows XP 2 Glassfish 3.1.2.2 or current v4 snapshot Reporter: Tang Yong Priority: Critical Today, I trigger a problem[1] about arquillian glassfish integrated test again on Glassfish 3.1.2.2 or current Glassfish 4.0-SNAPSHOT. [1]: http://stackoverflow.com/questions/8677780/cannot-deploy-jar-file-with-ej... The attachment(javaeewithgf.zip) is my modified sample based on "Enterprise JavaBeans 3.1, 6th Edition " using arquillian-glassfish-managed-3.1. And the attachment(server.log) is the result of running on current Glassfish 4.0-SNAPSHOT. The issue is very critical because test scene is very simple. I will upload the attachments. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1340) Drone webdriver is not created during @BeforeClass

by Alex Okrushko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1340?page=com.atlassian.jira.plugin.s... ] Alex Okrushko commented on ARQ-1340: ------------------------------------ Perfect, thanks! > Drone webdriver is not created during @BeforeClass > -------------------------------------------------- > > Key: ARQ-1340 > URL: https://issues.jboss.org/browse/ARQ-1340 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.1.1.Final > Environment: Arquillian JUnit Container 1.0.3.Final > Arquillian Graphene Webdriver 2.0.0.Alpha3 > Arquillian Drone dependencies and Selenium dependencies 1.1.1.Final > Arquillian Core dependencies 1.0.3.Final > junit 4.8.1 > jdk 1.6 > Reporter: Alex Okrushko > Assignee: Karel Piwko > > Drone webdriver is not created during @BeforeClass, however *is created during @Before or if called by GrapheneContext.getProxy()* > The following does NOT work: > {code:java} > @RunWith(Arquillian.class) > public class TestDroneLogin { > @Drone > private static WebDriver driver; > > @BeforeClass > public static void setup(){ > //GrapheneContext.getProxy().navigate().to("http://google.com"); > driver.navigate().to("http://google.com"); > } > > @Test > public void testInput(){ > driver.findElement(By.cssSelector("input#gbqfq")); > } > } > {code} > However, if I use {{GrapheneContext.getProxy()}} instead of {{driver}}, everything works as expected: > {code:java} > @BeforeClass > public static void setup(){ > GrapheneContext.getProxy().navigate().to("http://google.com"); > } > {code} > ALSO, if {{@Before}} is used then Drone webdriver is created as expected, so this problem is specific to {{@BeforeClass}} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1340) Drone webdriver is not created during @BeforeClass

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1340?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1340: --------------------------------- Alex, I think you would appreciate an idea of Drone / Thucydides integration: http://thucydides.info/overview http://arquillian.org/blog/tags/thucydides/ > Drone webdriver is not created during @BeforeClass > -------------------------------------------------- > > Key: ARQ-1340 > URL: https://issues.jboss.org/browse/ARQ-1340 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Drone > Affects Versions: drone_1.1.1.Final > Environment: Arquillian JUnit Container 1.0.3.Final > Arquillian Graphene Webdriver 2.0.0.Alpha3 > Arquillian Drone dependencies and Selenium dependencies 1.1.1.Final > Arquillian Core dependencies 1.0.3.Final > junit 4.8.1 > jdk 1.6 > Reporter: Alex Okrushko > Assignee: Karel Piwko > > Drone webdriver is not created during @BeforeClass, however *is created during @Before or if called by GrapheneContext.getProxy()* > The following does NOT work: > {code:java} > @RunWith(Arquillian.class) > public class TestDroneLogin { > @Drone > private static WebDriver driver; > > @BeforeClass > public static void setup(){ > //GrapheneContext.getProxy().navigate().to("http://google.com"); > driver.navigate().to("http://google.com"); > } > > @Test > public void testInput(){ > driver.findElement(By.cssSelector("input#gbqfq")); > } > } > {code} > However, if I use {{GrapheneContext.getProxy()}} instead of {{driver}}, everything works as expected: > {code:java} > @BeforeClass > public static void setup(){ > GrapheneContext.getProxy().navigate().to("http://google.com"); > } > {code} > ALSO, if {{@Before}} is used then Drone webdriver is created as expected, so this problem is specific to {{@BeforeClass}} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1087) Wrong dump directory path

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1087?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1087. ------------------------------ > Wrong dump directory path > ------------------------- > > Key: ARQ-1087 > URL: https://issues.jboss.org/browse/ARQ-1087 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha5 > Environment: Windows 7 64bit > Reporter: Nicolas-Xavier Vanderlinden > Assignee: Bartosz Majsak > Priority: Minor > Fix For: persistence_1.0.0.Alpha6 > > > Dump directory path seems to be wrong under Windows 7: > org.jboss.arquillian.persistence.core.exception.DatabaseDumpException: Unable to dump database state to C:UsersNicoAppDataLocalTemparquillian.extension.persistence.default.sql.script.location=script/[1346601018658] -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1094) @ShouldMatchDataSet Not Properly Comparing Datasets

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1094?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1094. ------------------------------ > @ShouldMatchDataSet Not Properly Comparing Datasets > --------------------------------------------------- > > Key: ARQ-1094 > URL: https://issues.jboss.org/browse/ARQ-1094 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Environment: RHEL 6.2, JBoss AS 7.1.1, EAP 6.0, H2 In-Memory Database, Arquillian 1.0.1.Final, APE Alpha5 > Reporter: Bryan Saunders > Assignee: Bartosz Majsak > Labels: persistence > Fix For: persistence_1.0.0.Alpha6 > > > APE's @ShouldMatchDataSet annotation is not properly matching datasets. See full discussion here: https://community.jboss.org/message/758418 -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2013