gnodet commented on PR #13494:
URL: https://github.com/apache/maven/pull/13494#issuecomment-6840426640

   @rmannibucau Good point — the current PR doesn't expose a per-dependency 
"classpath vs module path" toggle at the plugin author level. 
   
   For **modular plugins** (those with `<modular>true</modular>`): all declared 
dependencies land on the module path and must be named modules. There's no 
opt-out per dependency — if a dep can't be a named module (auto-module with no 
stable name, split package), the whole plugin load fails with 
`ModuleLayerCreationException`.
   
   For **classpath plugins** (the common case today): everything stays on the 
classpath as before. The `META-INF/maven/module-access` descriptor is for 
punching holes in strong encapsulation from boot-layer modules — it doesn't 
move deps to the module path.
   
   The hybrid model you describe (some deps on classpath, some on module path, 
within the same plugin load) is out of scope for this PR. That would likely 
require the Maven plugin POM model to gain a `<scope>module-path</scope>` or 
similar, and the resolver to handle split loading — a future design concern 
once the foundation here is in place.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to