[midPoint-git] [Evolveum/midpoint] dda866: MID-6475: Windows service is back, so is running w...

[virgo47]

  Branch: refs/heads/support-4.3
  Home:   https://github.com/Evolveum/midpoint
  Commit: dda8660397b2f7641c3d191b2abba3cad61b6e2c
      https://github.com/Evolveum/midpoint/commit/dda8660397b2f7641c3d191b2abba3cad61b6e2c
  Author: Richard Richter <richard.richter at evolveum.com>
  Date:   2021-06-16 (Wed, 16 Jun 2021)

  Changed paths:
    M dist/src/main/bin/midpoint.bat
    M dist/src/main/bin/midpoint.sh
    M dist/src/main/bin/service.bat
    M gui/admin-gui/pom.xml
    A tools/midpoint-boot-layout/pom.xml
    A tools/midpoint-boot-layout/src/main/java/com/evolveum/midpoint/tools/layout/MidPointWarLauncher.java
    A tools/midpoint-boot-layout/src/main/java/com/evolveum/midpoint/tools/layout/MidPointWarLayout.java
    A tools/midpoint-boot-layout/src/main/java/com/evolveum/midpoint/tools/layout/MidPointWarLayoutFactory.java
    M tools/pom.xml

  Log Message:
  -----------
  MID-6475: Windows service is back, so is running with -jar midpoint.war

The MidPointWarLauncher was reinstated in a simplified form as a first
step before PropertiesLauncher is run.
It contains needed "stop" method for Windows service.
This allowed to initialize loader.path here, which is much cleaner from
the outside perspective, JARs in ${midpoint.home}/lib just work again
even when run as -jar midpoint.war.