Hi all, Reviewing and trying to follow Martin's thread about JPMS I thought about the old issue that our build pipelines (plugins chain) is very hard to customize. Guillaume added the priority case but the clean solution proposed originally was to define custom lifecycles (to add frontend, docker builds for ex) - more or less a custom AbstractLifecycleMappingProvider.
I wonder if we shouldn't extend .mvn/extensions.xml (or root pom <extensions> block) to support to define custom lifecycle mappings there and potentially explicit new "types" too which would be great for Martin's work since it would allow to avoid undefined types and implicit jar mapping in a "strict" mode (to detect typos for ex since it must become open). So proposal is to extend extension to get more configuration - and coded extensions can indeed plug themselves there. The main challenge seems to be to re-evaluate the mappings but looks doable. High level it is more or less "let the pom/.mvn inject maven components without coding/by declaration". Hope it makes sense, let me know if it is worth investigating more or if the idea is too particular to my old needs. Best, Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance>
