Sure, but you asked for an API, there's none so far. I'm not sure what kind of API we could offer, as this depends on what you want to build. If you build an OSGi plugin, you may want to restrict the visibility to exported packages, kinda like with JPMS. Takari lifecycle does this sort of thing too. So the API depends on the packaging / type of artifact you're building imho.
Imho, but Tamas has thought about it more afaik, JPMS modules should have their own packaging / lifecycle, not reusing plain JAR, as the rules are different. The compiler plugin maybe should be a different plugin too, that would make things less complicated maybe. Guillaume Le mar. 19 déc. 2023 à 13:55, Martin Desruisseaux < [email protected]> a écrit : > Le 2023-12-19 à 13 h 32, Guillaume Nodet a écrit : > > > result.getPaths().stream().map(Path::toString).collect(Collectors.joining(":")) > > This is more complicated than that. From a set of dependencies, we need > to dispatch them between class-path, module-path and --patch-module > option (the latter may be seen as a class-path specific to each module). > This is done by an analysis of dependencies properties. Which is why I > think we need one more piece of API dedicated to this task. > > Martin > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ------------------------ Guillaume Nodet
