(Apologises for top posting ) This thread is about a bunch of requested features (cache and parallel executions of mojos) that we have been discussing on dev@ mailing list. As said in this thread the first show stopper for Maven is that we do not have a clear definition of input and outputs for each plugin. There are proposals but actually no one is spending actively engineering time on these topics.
Any help is very appreciated, please join us on dev@ Best regards Enrico Il Dom 2 Feb 2020, 18:57 Thomas Broyer <t.bro...@gmail.com> ha scritto: > Le dim. 2 févr. 2020 à 17:48, Anton Vodonosov <avodono...@yandex.ru> a > écrit : > > > Hello. > > > > In order to speed up the build of a multi-module project, I'd like to > > reuse artifacts of modules that haven't changed. > > Manual versioning is tedious and error-prone. > > > > Is it possible to automatically assign versions to modules computed as a > > hash-of( hash-of(module sources) + hashes of all dependencies)? > > > > Please define modules sources? > Hint: you can't, at least not without knowing how all plugins work. Gradle > Enterprise tries to have such knowledge fwiw to solve this exact issue. > > Also, you'll probably want to include system properties (or at least Maven > properties) and some environment information (e.g. which JDK) in the hash. > > In this approach, every change in code will modify such hash-based version > > of all dependent modules automatically. > > > > This would be similar to Nix package manager. > > > > How to do that in maven? > > > > As said above, you could try Gradle Enterprise. Takari had something in the > works too a few years ago. > …or if that's really problematic for you, then migrate to another build > tool, such as Gradle or Bazel. > > > > Best regards, > > - Anton > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
