[
https://issues.apache.org/jira/browse/OLINGO-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989526#comment-13989526
]
Francesco Chicchiriccò commented on OLINGO-271:
-----------------------------------------------
I have applied your patch without deploying {{ref}} as said and everything went
fine, so I have committed the changed to master:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=22eb2ed75832461adbbda160866b859ef5e24ea5
To me this issue can be resolved.
> Introduce a cargo context path for integration tests
> ----------------------------------------------------
>
> Key: OLINGO-271
> URL: https://issues.apache.org/jira/browse/OLINGO-271
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-client
> Reporter: Stephan Klevenz
> Attachments: cargo-run-failures.txt, fit-proposal.patch
>
>
> Currently the client side integration tests are executed on context root
> (cargo deployment):
> <deployables>
> <deployable>
> <properties>
> <context>/</context>
> </properties>
> </deployable>
> </deployables>
> </configuration>
> I would like to introduce a context path because of we plan to deploy a
> server side OData service (another WAR) in parallel.
> I have that done already and can provide a patch (attached).
> The context paths are named
> /stub (client integration test with a server stub)
> /ref (client integration test with reference server)
> /ref dose exists currently in feature branch only [olingo-266]. Feel free to
> find better names for instead of stub and ref.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
