June 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1735) Release Droidium 1.0.0.Alpha5

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1735?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic closed ARQ-1735. ---------------------------------- > Release Droidium 1.0.0.Alpha5 > ----------------------------- > > Key: ARQ-1735 > URL: https://issues.jboss.org/browse/ARQ-1735 > Project: Arquillian > Issue Type: Release > Security Level: Public(Everyone can see) > Components: Extension - Droidium > Affects Versions: droidium_1.0.0.Alpha4 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: droidium_1.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-454) NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created ARQGRA-454: ----------------------------------------- Summary: NPE in WebElementEnricher.enrich() with Arquillian 1.1.5.Final Key: ARQGRA-454 URL: https://issues.jboss.org/browse/ARQGRA-454 Project: Arquillian Graphene Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 2.0.3.Final Reporter: Juergen Zimmermann I'm getting a GrapheneTestEnricherException caused by a NPE (see stacktrace below) after upgrading Arquillian to 1.1.5.Final. The issue doesn't exist with Arquillian 1.1.4.Final. The stacktrace: {code} org.jboss.arquillian.graphene.enricher.exception.GrapheneTestEnricherException: Error while initializing: class de.shop.util.IndexPage at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:78) at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:125) at org.jboss.arquillian.graphene.DefaultGrapheneRuntime.goTo(DefaultGrapheneRuntime.java:120) at org.jboss.arquillian.graphene.Graphene.goTo(Graphene.java:291) at de.shop.util.AbstractWebTest.before(AbstractWebTest.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:267) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:193) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:345) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:49) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:207) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:155) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: java.lang.NullPointerException at org.jboss.arquillian.graphene.enricher.WebElementEnricher.enrich(WebElementEnricher.java:68) at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.enrichRecursively(AbstractSearchContextEnricher.java:73) at org.jboss.arquillian.graphene.enricher.PageObjectEnricher.setupPage(PageObjectEnricher.java:97) at org.jboss.arquillian.graphene.location.LocationEnricher.goTo(LocationEnricher.java:76) ... 34 more {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic resolved ARQ-1740. ------------------------------------ Resolution: Done > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic reopened ARQ-1740: ------------------------------------ > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1740: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: recorder_1.0.0.Alpha4 Resolution: Done > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > Fix For: recorder_1.0.0.Alpha4 > > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Alex Soto reassigned ARQ-1740: ------------------------------ Assignee: Stefan Miklosovic (was: Alex Soto) Done!!! And sorry I haven't seen that there was a checkstyle to be run in Maven. PR here https://github.com/lordofthejars/arquillian-recorder/compare/arquillian:m... > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1740: ----------------------------------- Assignee: Alex Soto (was: Stefan Miklosovic) > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Stefan Miklosovic (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic updated ARQ-1740: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-recorder/pull/4 > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Alex Soto reassigned ARQ-1740: ------------------------------ Assignee: Stefan Miklosovic (was: Alex Soto) I assign to you the issue so if you think that pull request is good you can close it. Of course if I have to close it, reassign again to me and I close it. > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Stefan Miklosovic > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1740) Allow Asciidoctor reporter to generate standard AsciiDoc

by Alex Soto (JIRA)

[ https://issues.jboss.org/browse/ARQ-1740?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1740 started by Alex Soto. > Allow Asciidoctor reporter to generate standard AsciiDoc > -------------------------------------------------------- > > Key: ARQ-1740 > URL: https://issues.jboss.org/browse/ARQ-1740 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Recorder > Affects Versions: recorder_1.0.0.Alpha2 > Reporter: Alex Soto > Assignee: Alex Soto > Priority: Minor > > Allow Asciidoctor reporter to generate standard AsciiDoc. Currently Asciidoctor reporter generates AsciiDoc files that can only be converted by Asciidoctor. > If user tries to convert AsciiDoc file using python implementation an exception will be thrown. Although probably most users will use Asciidoctor, it will be interesting to add an option so if user are still using python implementation the reporter generates an AsciiDoc report fully compatible with python implementation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2014