This is an automated email from the ASF dual-hosted git repository. elharo pushed a commit to branch elharo-patch-5 in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 5f0a16223a8f13919d13ed3e92b1c9c20e091d08 Author: Elliotte Rusty Harold <[email protected]> AuthorDate: Mon Jan 6 06:54:28 2020 -0500 Update Java versions for 2019 @michael-o --- content/apt/pom.apt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/apt/pom.apt b/content/apt/pom.apt index d408598..69cc2db 100644 --- a/content/apt/pom.apt +++ b/content/apt/pom.apt @@ -369,9 +369,9 @@ mvn install:install-file -Dfile=non-maven-proj.jar -DgroupId=some.group -Dartifa The classifier distinguishes artifacts that were built from the same POM but differ in content. It is some optional and arbitrary string that - if present - is appended to the artifact name just after the version number. - As a motivation for this element, consider for example a project that offers an artifact targeting JRE 1.5 but at the - same time also an artifact that still supports JRE 1.4. The first artifact could be equipped with the classifier - <<<jdk15>>> and the second one with <<<jdk14>>> such that clients can choose which one to use. + As a motivation for this element, consider for example a project that offers an artifact targeting Java 11 but at the + same time also an artifact that still supports Java 1.8. The first artifact could be equipped with the classifier + <<<jdk11>>> and the second one with <<<jdk8>>> such that clients can choose which one to use. Another common use case for classifiers is to attach secondary artifacts to the project's main artifact. If you browse the Maven central repository, you will notice that the classifiers <<<sources>>> and <<<javadoc>>> are used
