Le dim. 29 oct. 2023 à 20:49, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit :
> Le 2023-10-29 à 16 h 10, Tamás Cservenák a écrit : > > > The current draft of types we want to introduce (and packaging): > > https://gist.github.com/cstamas/4e9bcbef25ce912a90ad1e127b0c5db8 > > > Thanks! I fully support this proposal, as I believe it can resolve the > most blocking issue in using JPMS with Maven. > > This is not the only issue, we would also need some support for > --add-reads, --add-exports and --add-opens options. But maybe we can > discuss that on a separated wiki page. The most important issue is > control on class-path versus module-path, and above proposal seems to > address it well. Thanks again! > Is it really different since part of options are related so either we align on the jvm making using maven location mapping easier or we fully integrate but means we must detect errors in options which is for me a hard task (= gain will be low). So don't think it is a different thread, it is the same for me. side note: please think about transitivity, here with the proposal you must define *all* your transitive deps in your consumer pom. Completely changes the maven philosophy. > > Martin > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
