This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new c9f7599d Update guide-maven-classloading.apt
c9f7599d is described below
commit c9f7599d87961cdcabcd33970b110d013a39b1e9
Author: Konrad Windszus <[email protected]>
AuthorDate: Sat Jun 10 20:45:33 2023 +0200
Update guide-maven-classloading.apt
Fix links, some clarifications
---
content/apt/guides/mini/guide-maven-classloading.apt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/apt/guides/mini/guide-maven-classloading.apt
b/content/apt/guides/mini/guide-maven-classloading.apt
index 2f700f76..9a5cf871 100644
--- a/content/apt/guides/mini/guide-maven-classloading.apt
+++ b/content/apt/guides/mini/guide-maven-classloading.apt
@@ -68,9 +68,9 @@ Guide to Maven Classloading
<<<{{{/ref/current/apidocs/org/apache/maven/project/MavenProject.html}MavenProject}}>>>
belong to this classloader.
- You can add elements to this classloader by
{{{/ref/current/maven-model/maven.html#class_extension}extensions}}.
+ You can add elements to this classloader by the means outlined in
{{{./guide-using-extensions.html}Core Extension}}.
These are loaded through the same classloader as <<<$\{maven.home\}/lib>>>
and hence are available
- to the Maven core and all plugins for the current project (through the API
Classloader: see next paragraph).
+ to the Maven core and all plugins for the current project (through the API
Classloader, see next paragraph).
More information is available in {{{./guide-using-extensions.html}Core
Extension}}.
* {API Classloader}
@@ -84,10 +84,10 @@ Guide to Maven Classloading
[../../buildExtensionClassRealm.svg] Build Extension Class Realm
- For every plugin which is marked with <<<\<extensions\>true\</extensions\>>>>
or a build extension listed in the according section of the POM, there is
+ For every plugin which is marked with <<<\<extensions\>true\</extensions\>>>>
and every {{{/ref/current/maven-model/maven.html#class_extension}build
extension}} listed in the according section of the POM, there is
a dedicated classloader. Those are isolated. That is, one build extension
does not have access to other build extensions.
It imports everything from the API classloader.
- All JSR 330 or Plexus components declared in the underlying JAR are
registered as components in the global Plexus container
+ All JSR 330 or Plexus components declared in the underlying JAR are
registered in the global Plexus container
while creating the classloader.
In addition all component references in the plugin descriptor are properly
wired from the underlying Plexus container.
Build extensions have limited effect as they are loaded late.
