JSR-352: Test starting/stopping the job using WildFly tooling (e.g. CLI)

Description

https://github.com/mincong-h/gsoc-hsearch/issues/150

WARNING: we need Wildfly 11 in order to even try to test this, because in Wildfly 10 only batch jobs defined in the deployed module are accessible from the command line. And in our case, the batch job is defined in a dependency of the deployed module. See https://issues.jboss.org/browse/WFLY-7000

Environment

None

Activity

Show:
Yoann Rodière
July 13, 2017, 8:06 AM

Maybe we could test this on Wildfly 11.0.0.Alpha1? We'd have to change the wildfly version in our pom, launch the main Wildfly integration tests, and if that works, we could start adding a test using the CLI as described in the original issue on GitHub.

Sanne Grinovero
July 13, 2017, 9:49 AM
Edited

We'd have to change the wildfly version in our pom, launch the main Wildfly integration tests

Just to share a trick: remember that to run quick experiment you can override any build property from the commandline. This is one of the reasons we define versions in properties.

Yoann Rodière
August 7, 2017, 7:40 AM

Current status: testing with Wildfly 11 seems to result in linking errors:

See the branch: https://github.com/mincong-h/hibernate-search/commits/HSEARCH-2614-test-WildFly-CLI
... and the Travis build: https://travis-ci.org/mincong-h/hibernate-search/builds/261250399?utm_source=github_status&utm_medium=notification

I will look into it later.

Fixed

Assignee

Yoann Rodière

Reporter

Yoann Rodière

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Fix versions

Priority

Minor
Configure