summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCedric Beust <cedric@beust.com>2017-02-16 06:28:19 -0800
committerGitHub <noreply@github.com>2017-02-16 06:28:19 -0800
commit47d25b9f975ba1b71c05c0bed2e128548a40b15b (patch)
treecbfc2acbdf75d7debd76c4f2b36167f95eed22f6
parent05fefa91406dc9514fc3583b88b9fd7ea8619947 (diff)
downloadjcommander-47d25b9f975ba1b71c05c0bed2e128548a40b15b.tar.gz
Update index.adoc
-rw-r--r--doc/index.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/index.adoc b/doc/index.adoc
index c3d996b..1dca5fb 100644
--- a/doc/index.adoc
+++ b/doc/index.adoc
@@ -485,7 +485,7 @@ Attempting to pass a negative integer to this option will cause a ParameterExcep
=== Global parameter validation
-After parsing your parameters with JCommander, you might want to perform additional validation across these parameters, such as making sure that two mutually exclusive parameters are not both specified. Because of all the potential combinations involved in such validation, JCommander does not provide any annotation-based solution to perform this validation because such an approach would necessarily be very limited by the very nature of Java annotations. Instead, you should simple perform this validation in Java on all the arguments that JCommander just parsed.
+After parsing your parameters with JCommander, you might want to perform additional validation across these parameters, such as making sure that two mutually exclusive parameters are not both specified. Because of all the potential combinations involved in such validation, JCommander does not provide any annotation-based solution to perform this validation because such an approach would necessarily be very limited by the very nature of Java annotations. Instead, you should simply perform this validation in Java on all the arguments that JCommander just parsed.
== Main parameter