GitLab

that suits the docker version, as it is different from the distrib one.
For now, the version is copied, and any modification in the file must
be copied to the docker version.
With the proposed change, the docker version is generated from the
distrib version, with minor changes

to test docker image

(+ include tests in docker image build on CI) => commented out for now,
as GOSS tool is missing on the CI slave image

Closes [BR-530](https://bonitasoft.atlassian.net/browse/BR-530)

Now it builds BOS & SP images on PR and master/dev builds and pushes it to quay.io (BOS + SP)

Closes [BR-530](https://bonitasoft.atlassian.net/browse/BR-530)

instead of a separate Github repo, use distrib repo to build docker images.

`build.sh` can be run with the local build snapshot build when the version is `SNAPSHOT` see `infrastructure/build_and_publish_docker_image.groovy`

that index.jsp was added to replace root application and to redirect to
/bonita

Because of a refactor on how distrib is organized, that index.jsp was
not copied anymore in `/server/webapps/ROOT`

Move it in the right folder and change the order of copy to have it
where it belongs.

Closes [BR-478](https://bonitasoft.atlassian.net/browse/BR-478)

Without `level` at the end of the property, it doesn't work

Closes [BR-430](https://bonitasoft.atlassian.net/browse/BR-430)

Also remove all reference to the need to add Oracle drivers

covers [BPO-540](https://bonitasoft.atlassian.net/browse/BPO-540)

* avoid generating empty log files

'host-manager' and 'manager' webapps are not packaged within the bundle so
remove associated handlers that previously generated empty log files.
In addition, remove the 'localhost' handlers as no logger is associated to it.

* all logs in a single bonita.log file

This ensures that all logs of 3rd party libs are in bonita.log and simplify
logging configuration.

In the past, we have been forced to declare for most of 3rd party lib loggers
the right handler to ensure logs are generated in the bonita.log file. Most of
the time, this was done only after receiving external feedback on bug
investigations (information were lost or hidden in catalina log file).

Part of the work to hide Tomcat internals to the external world.

* comment AJP connector by default (follow tomcat changes)

this fixes CVEs, see
https://tomcat.apache.org/security-8.html

Closes [BR-408](https://bonitasoft.atlassian.net/browse/BR-408)

When using oracle and XA, there is an issue between Arjuna and Oracle that causes XAResource enlisting issue.
In order to avoid this issue when there is multiple XAResource registered, override XADataSource in commons-dbcp2 to make XAResource#isSameRM always return false in the case of Oracle database.

Add also integration tests on BDM

Relates to [BR-370](https://bonitasoft.atlassian.net/browse/BR-370)
Closes to [BS-19464](https://bonitasoft.atlassian.net/browse/BS-19464)

if activated

Closes [BR-353](https://bonitasoft.atlassian.net/browse/BR-353)

stax was duplicated, ignore the oldest version

for activation, remove it from lib/bonita, it was no used by the
transaction manager
ignore activation-api from transitive dependencies, its bundled by
jakarta.activation (api+implementation)

Relates to [BR-332](https://bonitasoft.atlassian.net/browse/BR-332)

* use bonita-web-sp dependencies for the sp war
* bonita-war-sp: add console-server-sp extra dependencies
* remove libs already in lib/bonita
* ignore overlay when building bonita-war-sp

the overlay comes from console-server-sp.war that have
console-server.war as overlay. It was making lib present in community but not in SP to be copied in the SP war (forms-*.jar)
Co-authored-by: Baptiste Mesta <baptiste.mesta@gmail.com>