Le 27/04/2018 à 10:27, Robert Scholte a écrit : > IMO this will overcomplicate things and I don't see the real benefits > of it. > Indeed it would complicates plugins, but conversely doing nothing complicates the use of standard Java tools. For example Maven can not yet generate aggregate javadoc on modularized projects, and the default Maven directory structure is blocking us from using the command-line as a fallback (unless I missed a workaround). So I'm looking for a way to get the best of both worlds.
> You've summed up only a small number of plugins, but in the end almost > every plugins needs to become aware of this new structure > Yes, I realize that. > The options to compile multiple modules all at once is a direct result > of the modularization of the JDK itself, and the need to build it all > at once without third party tool. Maven already supports this since > the early days, but with its own structure. > Indeed, but Maven own structure provides different advantages and inconvenient. In addition of above-cited javadoc issue, running annotation processor on multi-modules at once would be easier with a jigsaw-friendly project (I sometime need to do that, when the processing result is some kind of global report). I suspect that there would also be other advantages with other Java tools that I did not yet explored. > You can give it a try to patch the plugins, but I'm afraid you'll jump > from one failing plugin to the next. > Possibly, but before to spend time on that I would prefer to know if there is support for the principle. A wiki page? Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
