Can we have the documentation module of the core project in a profile so it can be disabled if needed? It still has issues building as well depends on native tools not universally present. It will be an issue for a CI system to ensure these tools present on all build hosts as well in some other cases.
Attaching a patch file. Since docs are not buildable now I verified to get the same error with and without the patch.
you cam apply by "patch -p0 < docs.patch"
Moved documentation module definition in main pom to 2 separate profiles:
1) the 'release' profile used by the release plugin
2) profile named 'docs' intended to be able to activate inclusion of documentation
So essentially documentation is now not activated by default. Instead, for non-release processes one must activate that profile explicitly. My only real concern with that is how that will play with IDE integrations. By I am pretty sure for IntelliJ at least this will be fine; really no clue about Eclipse. We can revisit if that becomes an issue.
Thanks! CI is now running fine. There is some issue with publishing and notification but that will be resolved soon.
Database builds are my next task.