Add support for externally provided 'lifecycle-mapping-metadata.xml' …

…file

Signed-off-by: Snjezana Peco <snjezana.peco@redhat.com>

README.md

@@ -193,6 +193,7 @@ The following settings are supported:
 * `java.templates.typeComment`: Specifies the type comment for new Java type. Supports configuring multi-line comments with an array of strings, and using ${variable} to reference the [predefined variables](https://github.com/redhat-developer/vscode-java/wiki/Predefined-Variables-for-Java-Template-Snippets).
 * `java.references.includeAccessors`: Include getter, setter and builder/constructor when finding references. Default to true.
 * `java.configuration.maven.globalSettings` : Path to Maven's global settings.xml.
+* `java.configuration.maven.lifecycleMappings` : Path to Maven's lifecycle mappings xml.
 * `java.eclipse.downloadSources` : Enable/disable download of Maven source artifacts for Eclipse projects.
 * `java.references.includeDecompiledSources` : Include the decompiled sources when finding references. Default to true.
 * `java.project.sourcePaths`: Relative paths to the workspace where stores the source files. `Only` effective in the `WORKSPACE` scope. The setting will `NOT` affect Maven or Gradle project.

package.json

@@ -619,6 +619,13 @@
           "description": "Specifies default mojo execution action when no associated metadata can be detected.",
           "scope": "window",
           "order": 90
+        },
+        "java.configuration.maven.lifecycleMappings": {
+          "type": "string",
+          "default": null,
+          "description": "Path to Maven's lifecycle mappings xml",
+          "scope": "window",
+          "order": 100
         }
       }
     },