[hibernate-dev] Enabling all modules by default in a build

[Sanne Grinovero]

In Hibernate Search there is a Maven module responsible for running
performance tests, which takes several minutes to run.

Since it's quite annoying for day to day development, and especially
during a release process as the process runs the tests multiple times,
the module is only enabled when explicitly selecting an ad-hoc Maven
profile.

I now just realized that by doing so, the Maven release process does
not correctly update the version of the module after a release: the
non-master CI jobs I just created fail to build as it refers to a
mismatched snapshot version (it happens to work on master by chance).

I'll fix the specific situation with an ad-hoc commit, but what's the
long term fix? Should we deprecate this kind of selection of built
modules?

This problem didn't affect the docs module as this is explicitly
enabled by the release process, but I really don't want to add an
additional half an our for the release process to run performance
tests.

I'm planning to have the module always run, so that at least it gets
compiled, and use the profile to set some environment options for
long/short duration. Good idea?

The fix to include documentation would probably need to wait migration
to asciidoc.

Cheers,
Sanne