Le 28/08/2023 à 13:30, Elliotte Rusty Harold a écrit :
> On Mon, Aug 28, 2023 at 8:49 AM Martin Desruisseaux wrote:
>> * Long term solution would be to change the POM model by expanding the
>> <dependency> section for controlling on an individual basis how to
>> handle each dependency.
>
> How would this work with transitive dependencies?
I propose to make it non-transitive: an explicit request to put a
dependency on the class-path or module-path would apply only to that
direct dependency. The transitive dependencies would continue to be
handled as declared in the pom.xml file of the direct dependency.
Rational: a direct dependency may be known to be compatible with both
the class-path and module-path (e.g. it may duplicate "module-info" into
"META-INF/services/"), but maybe some transitive dependencies are not.
However developers could override the behavior of a transitive
dependency by declaring that dependency explicitly in the project
pom.xml. It would be similar to overriding the version of a transitive
dependency.
> Meta-point: it's easier to keep long term track of discussions like
> this if they're in the issue tracker instead of the mailing list.
We have https://issues.apache.org/jira/browse/MNG-7855. Should it be a
wiki or a GitHub discussion page instead? (whatever is more convenient
for developers involved in those parts of Maven).
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
