Thomas Bouffard authored Jan 15, 2020 and Baptiste Mesta committed Jan 15, 2020

Stop having bonita-web as parent
  - this added gwt dependencies to all modules
  - use bom for dependencies management instead

remove declaration of uid version as it is not used (confirmed by the version
which relates to bonita 7.6)

upgrade plugins versions to latest available
remove unused plugins
  - checksum-maven-plugin
  - jacoco-maven-plugin

update maven-compiler plugin configuration

Introduce bonita-war to replace all-in-one and war-server
  - the main change is to declare all dependencies in war-server to let maven
  resolve dependencies
  - only on community for now
  - previously, as we copied the lib from the web war and add the one for
  bonita-server, the dependencies resolution could not be properly done by maven
  So, now, just copy web resources first to create the initial war, then add all
  the lib to the war via full maven resolution

Simplify the bundle preparation
  - previously, it was done in several steps because we had the deploy and the
  wildfly bundles.
  - now, we create a 'tomcat distribution for bonita', used for both Community
  and Enterprise to remove duplication

Other changes
  - remove license files
  They are only packaged in the deploy bundle but not in the final tomcat one,
  so remove them
  - remove spnego jar from repository and get it as maven dependency
  - package: avoid warning on windows (outputDirectory)

Thomas Bouffard authored Jan 14, 2020 and Baptiste Mesta committed Jan 14, 2020

Simplify access to bonita by redirecting tomcat root to the bonita webapps.
This implies replacing the default tomcat ROOT webapps by a custom one in charge
of the redirect.

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

Deploying extra webapp in the bonita bundle is not supported. However, if this
is needed, do it by dropping it in the webapps tomcat folder
Part of the work to hide Tomcat internals to the external world.

Simplify processing
  - remove version in tomcat directories used in various modules
  - deploy module: put bonita lib directory in the final tomcat server/lib/bonita
  folder for simplification
  - remove extra copies of jars and files

In addition, use maven pom packaging for the 'deploy-distrib-sp'module as
this module doesn't need to produce a jar artifact

* feat(wildfly removal): remove WildFly bundle from distrib

* Also remove CAS config module for WildFly

* Simplify structure, now that there is only Tomcat

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

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

* fix deploy plugin configuration for theme archetype

+ add logging config for the Arjuna Listener

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

Previous implementation used a dedicated download mechanism: retrieve
them from download sites (but without checksum checks), cache them locally
and detect if they were available locally.

New implementation relies on the Maven dependency resolution. This
  - makes the pom simpler (no antrun task, nor dedicated caching), in particular
  remove dependency on ant-contrib
  - cache, checksum checks are deferred to Maven --> safer builds

In addition, fix community tomcat assembly (remove leading /) that were
useless and generated warning when building on windows

Plus some minor fixes:
  - fix warning generated by parent not in the root folder (set no relative
     path)
  - set encoding to UTF-8 for reproducible builds
  - wildfly bundle community: remove the deploy plugin configuration as
     it is managed at top level globally in the parent of the project and
     configured using a property set to not deploy the module
  - git ignore: correctly ignore node resources


Covers [BS-19060](https://bonitasoft.atlassian.net/browse/BS-19060)