Plugin classpaths

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Plugin classpaths

Elliotte Rusty Harold
When executing a Maven build are the various plugins--compiler plugin,
release plugin, shade plugin, etc.--separated from each other in any
way? That is,

1. Do they execute in separate processes?
2. Do they use separate class loaders?

or do they all run together in the same process with the same classpath?

--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Plugin classpaths

Hervé BOUTEMY
there is also a documentation for that
https://maven.apache.org/guides/mini/guide-maven-classloading.html

Regards,

Hervé

Le samedi 11 avril 2020, 14:49:06 CEST Robert Scholte a écrit :

> It is a classpath per plugin. The class you're looking for is
> the DefaultBuildPluginManager[1]
>
> Robert
>
>
> [1] https://github.com/apache/maven/blob/master/maven-core/src/main/java/org
> /apache/maven/plugin/DefaultBuildPluginManager.java On 11-4-2020 13:09:53,
> Elliotte Rusty Harold <[hidden email]> wrote: When executing a Maven
> build are the various plugins--compiler plugin, release plugin, shade
> plugin, etc.--separated from each other in any way? That is,
>
> 1. Do they execute in separate processes?
> 2. Do they use separate class loaders?
>
> or do they all run together in the same process with the same classpath?
>
> --
> Elliotte Rusty Harold
> [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]





---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]