Fixed #474- Improve doc on how to pass parameter to MavenOption when …

…using MavenCLIOptions (#475)

* Describe how to pass parameter to MavenOption annotation
* Add entry to release notes

itf-documentation/src/main/asciidoc/release-notes/_release-notes-0.14.0.adoc

@@ -40,6 +40,7 @@
 :issue-468: https://github.com/khmarbaise/maven-it-extension/issues/468[Fixed #468]
 :pr-460: https://github.com/khmarbaise/maven-it-extension/pull/460[Pull request #460]
 :pr-462: https://github.com/khmarbaise/maven-it-extension/pull/462[Pull request #462]
+:issue-474: https://github.com/khmarbaise/maven-it-extension/issues/474[Fixed #474]
 
 :release_0_14_0: https://github.com/khmarbaise/maven-it-extension/milestone/14
 

itf-documentation/src/main/asciidoc/usersguide/usersguide.adoc

@@ -783,7 +783,7 @@ void first( MavenExecutionResult result )
 ----
 
 [[structuring.default.goals.options]]
-=== Default Goals,Options
+=== Default Goals, Options
 
 [[structuring.goals]]
 ==== Goals
@@ -970,6 +970,18 @@ class BasicIT {
   }
 }
 ----
+If you want to pass a parameter to a `@MavenOption` you have to name the parameters explicit like this:
+[source,java]
+----
+@MavenJupiterExtension
+class BasicIT {
+
+  @MavenTest
+  @MavenOption(value = MavenCLIOptions.FILE, parameter = 'path/to/pom.xml')
+  void first(MavenExecutionResult result) {
+  }
+}
+----
 Now let us summarize the information for options. As long as no explicit `@MavenOption` is defined the
 default will be used which are the following: