Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/227
@anujgandharv, the first place to look is at the actual
`jena-integration-tests` module. You will see there that the tests follow the
same form as in other Jena modules (explicitly linked together in suites and
run by `maven-surefire`). I would myself have preferred to use more usual
practices such as those to which I suppose you to be referring (tests selected
by name, `maven-failsafe` for integration tests) but at least this way is
consistent across the Jena code base.
So in order to put your tests into that module as it stands you would have
to use the Maven plugin to start an ES node before the `test` phase and stop it
afterwards. There aren't any such phases that seem particularly suitable to me,
but you could use `process-test-classes` and `prepare-package`, I suppose.
On the other hand, it might be better (I think it would be better) to put
your tests into that module and execute them with `maven-failsafe`. Then you
can use the `pre-` and `post-integration-test` phases to start and stop the ES
node, which is (to my understanding) the right and normal timing for that kind
of operation.
A last alternative would be to break that integration test module down into
submodules, one for each module being tested. That's a little more hierarchy
and structure than Jena usually uses with maven, but this might be a good place
for it.
@afs, what do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
