Determine if LTE requires custom handling of the Maven wrapper with multi-module Maven projects.

PROBLEM

Multi-mod Maven case doesn't allow launch from "child" directory using mvnw wrapper from parent.
Say I have a multi-mod Maven structure like:

parent
 + pom.xml
 + mvnw
 + war
      + pom.xml
      + src/main/liberty/config/server.xml
      ....
 + jar
      pom.xml
      ...

In Liberty Tools Eclipse, I can run from the parent project and use the default parms (which is an empty list) and get mvnw liberty:dev, i.e. it'll use the mvnw wrapper in the root.

However, if I try to run from the 'war' level, I'll get default parms of ( ... -f ../pom.xml -pl war). However there's no way to pick up mvnw.

IDEA

• Can we try to look for 'mvnw' in the parent/containing folder?
• Should we only do such a check if we see a relative path like ../pom.xml as the -f parm value?
• Does this steer us towards the need of a display of the full generated command? : https://github.com/OpenLiberty/liberty-tools-eclipse/issues/210

Start with the child-project command described in the issue: a war module using -f ../pom.xml -pl war while the mvnw wrapper is in the parent directory. Review the discussion in issue 210 about displaying the full generated command, then define and test the expected wrapper lookup behavior for multi-module projects.