> I do not understand what you are trying to explain here. Sorry I was not clear at all ! I was trying to say that in a multimodule build, if you have a module shaded with the shade plugin, my rule of thumb is to NEVER have another module listing this shaded module in its dependencies. Said otherwise, in the same reactor, the shaded module must be a dependency of no other module. This is because Maven computes the dependency graph at startup, when it has no idea of "shading".
*- - - - -François Marot* Le dim. 10 juil. 2022 à 11:56, Niels Basjes <ni...@basjes.nl> a écrit : > Hi, > > On Fri, Jul 8, 2022 at 5:43 PM Francois Marot <francois.ma...@gmail.com> > wrote: > > > I believe you used the shade maven plugin or equivalent. > > > Yes > > > > I faced this > > problem multiple times and to my knowledge, there is no "good" solution. > > > > I was afraid of that. > > > > The problem is that Maven computes the dependency graph for all modules > of > > the reactor right at the start. But when the shade plugin integrates > ANTLR > > inside your library, this library should not depend onto ANTLR anymore. > But > > because the dependency graph was computed at the start, > > other modules of the reactor depending onto your library still depend > onto > > ANTLR even if there is already a shaded version of ANTLR inside your > > library. > > > > Yes, I was hoping there is a simple way to detach a directory from the main > build reactor and still have it built. > > So in the end, in the same reactor execution, module MUST NOT depend onto a > > shaded module. They must be considered as 'final' modules. > > > > I do not understand what you are trying to explain here. > > Niels >
