Sean Busbey wrote:
I can think of some hacky ways to use the profile yetus tries to
activate[1] to have the integration tests run during the test-phase.
But that's a bad idea, since you'll essentially have to duplicate any
work configured to happen in the pre-integration-test and
post-integration-test phases.
Probably easiest will be to define a new test plugin that calls the
verify goal (with the needed params to avoid e.g. unit tests, javadoc,
etc). The checkstyle and findbugs test plugins both include having
maven run with goals:
https://github.com/apache/yetus/blob/master/precommit/test-patch.d/checkstyle.sh#L164
https://github.com/apache/yetus/blob/master/precommit/test-patch.d/findbugs.sh#L100
This is exactly what I had in mind. Thanks for the pointer.
They take different approaches, with findbugs using
maven_modules_worker. It looks much simpler to base your test on the
findbugs plugin, IMHO.
We'd love a "make a Yetus test plugin" tutorial based on "run a maven
plugin," if you wouldn't mind writing down the process you end up
going through. ;)
I will keep this in mind :D
[1]:
http://yetus.apache.org/documentation/0.1.0/precommit-buildtools/#test-profile
