Le dim. 29 oct. 2023 à 21:32, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit :
> Le 2023-10-29 à 21 h 25, Romain Manni-Bucau a écrit : > > > Then you are back to the dependency set solution which is not the type > > solution and in this option the type is fully useless. > > > Maybe we would need a wiki page explaining how the DependencySet > approach would apply to JPMS. At this time, the relationship to the > --add-exports option is obscure to me. > Was referencing the options using module names, if you drop the dep or reference a package not supported by the module we should be able to fail. But you are right it belongs to the shared part of maven handling jvm options (likely the same handling the dependency resolution for the parameters from the dependency set reference I spoke about for ex). > > > >> Why would we need to declare all transitive dependencies? The > >> <type>module</type> element in the pom.xml of each dependency would > >> apply. > >> > > Cause your transitive deps are then jars, not modules (that said the > > opposite is wrong too for most libs) > > > When Maven downloads a JAR file, it also downloads its POM file. In my > understanding this is how Maven get information about transitive > dependencies. It seems to me that Maven gets type information of > transitive dependencies that way too, isn't it? > It downloads pom in version 4.0.0 without the guarantee of the handing of this meta, we can make it downloading more recent pom with the new meta but no guarantee in the future so you kind of lock your maven version with the pom (from experience it is not good for dev to restrict it too much even if I know some people like to lock it). > > Martin > >
