You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/11/30 20:51:06 UTC

[GitHub] [maven-site] kwin commented on a diff in pull request #346: [MNGSITE-501] Clarify profile jdk activation

kwin commented on code in PR #346:
URL: https://github.com/apache/maven-site/pull/346#discussion_r1036430310


##########
content/apt/guides/introduction/introduction-to-profiles.apt:
##########
@@ -127,11 +129,12 @@ mvn groupId:artifactId:goal -P profile-1,profile-2,?profile-3
   Profiles can be automatically triggered based on the detected state of
   the build environment. These triggers are specified via an <<<\<activation\>>>>
   section in the profile itself. Currently, this detection is limited to
-  prefix-matching of the JDK version, the presence of a system property or
-  the value of a system property. Here are some examples.

Review Comment:
   well prefix matching is just one possibility as version ranges are supported as well



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org