Le 2024-01-03 à 16 h 45, Romain Manni-Bucau a écrit :
maven4 introduces the notion of "services" (...snip...) So guess all
is there to do it and core can stay as this for backward compat
(maven4 must support maven3) but nothing more.
Current services are class-path aware, with DependencyProperties and
isAddedToClasspath() methods. My argument is that where class-path is
handled, module-path should be handled too, because it is a replacement
for class-path.
Maybe I misread your PR but I didn't see where dependencies were added
in dep resolver using the meta
I do not touch to this part of Maven.
use javadoc:javadoc then, intent is to run it with --module-path
target/classes but compile with --classpath
No, if the project is compiled with --module-path, it should be run with
the same --module-path (except for JAR added/removed because of scopes),
and javadoc should be run with the same --module-path as well. I do not
understand why you insist for inconsistent options? Can you please
provide a test case showing your point? We are keep arguing again and
again in circles. Please prove me your point with an "hello world"
compilable, executable and documentable on the command line with
inconsistent options, and showing that those inconsistencies are
required for producing the desired result.
Martin
