Tamas Cservenak opened MNG-8263 and commented

At early beginning of ingesting Takari Wrapper, several ideas were tried until wrapper arrived to it's final place.
Still, there are some remnants in master that complicates our lives and also results in strange side effects:

• lifecycle - this makes Maven4 be fixed regarding used Wrapper (unless explicitly set in POM, but wrapper is not a lifecycle plugin, so should not be set in POM)
• mvn/mvn.cmd scripts - they were split to make them reusable for wrapper, but today there is no need for this. Still, split scripts are hard to manage/edit/validate with tools.

Issue Links:

• MNG-7900 wrapper lifecycle in multi module project should be executed only in root module

• MWRAPPER-14 Make maven wrapper functional

• MNG-6917 Introduce wrapper lifecycle
  ("supercedes")

• MNG-6914 Align mvn and mvnw scripts
  ("supercedes")

Remote Links:

• GitHub Pull Request #1736
  

Backported to: 4.0.0-beta-5