[maven-compiler-plugin] branch master updated: add a reference to older projects with module-info

[hboutemy]

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-compiler-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new ccf790e  add a reference to older projects with module-info
ccf790e is described below

commit ccf790e2b4f4b7ef6b1dd96fd88e570e36e8e549
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Sat May 2 12:46:51 2020 +0200

    add a reference to older projects with module-info
---
 src/site/apt/multirelease.apt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/apt/multirelease.apt b/src/site/apt/multirelease.apt
index 3c6c5bc..42aa53d 100644
--- a/src/site/apt/multirelease.apt
+++ b/src/site/apt/multirelease.apt
@@ -98,7 +98,7 @@ META-INF/MANIFEST.MF { Multi-Release: true }
 
   There are a couple of important facts one should know when creating Multi 
Release jars.
   
-  * The Java compiler must be called for every different version. The 
solutions solve this either by having multiple Maven Projects/Modules or by 
adding extra execution-blocks to the pom. 
+  * The Java compiler must be called for every different version. The 
solutions solve this either by having multiple Maven Projects/Modules or by 
adding extra compiler execution-blocks to the POM (like 
{{{./examples/module-info.html}older projects with module-info}}). 
   
   * The <<<Multi-Release: true>>> attribute is only recognized when the 
classes are in a jar. In other words, you cannot test the classes put in 
<<<target/classes/META-INF/versions/$\{release}/>>>.