[arquillian-issues] [JBoss JIRA] (ARQGRA-468) Cannot use relative @Location when using "standalone" JUnit integration

[Lukáš Fryč (JIRA)]

     [ https://issues.jboss.org/browse/ARQGRA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukáš Fryč updated ARQGRA-468:
------------------------------
    Fix Version/s: 2.1.0.Alpha3
                       (was: 2.1-Tracking)


> Cannot use relative @Location when using "standalone" JUnit integration
> -----------------------------------------------------------------------
>
>                 Key: ARQGRA-468
>                 URL: https://issues.jboss.org/browse/ARQGRA-468
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: configuration
>    Affects Versions: 2.1.0.Alpha2
>            Reporter: Christoffer Bromberg
>            Assignee: Christoffer Bromberg
>            Priority: Minor
>             Fix For: 2.1.0.Alpha3
>
>
> As per https://issues.jboss.org/browse/ARQGRA-374 one can use the arquillian.xml to specify a "contextRoot" for page objects that use a relative URL.
> This feature does not work if you use the "Standalone Mode" as described here: https://docs.jboss.org/author/display/ARQGRA2/Framework+Integration+Options
> After I switched to the "container" dependency it works as expected.
> I don't use the deployment and container management feature of Arquillian and still the "container" dependency works without any hassle. So either the 
> {code}
> <!-- Arquillian JUnit Standalone -->
> <dependency>
>     <groupId>org.jboss.arquillian.junit</groupId>
>     <artifactId>arquillian-junit-standalone</artifactId>
>     <scope>test</scope>
> </dependency>
> {code}
> dependency should also include the correct classes (e.g. URLResourceProvider)  or maybe the "Standalone" integration option is not (or no longer) needed.
> So the workaround for me was to use the arquillian-junit-container dependency.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)