Guess a prerequisite would be a finer graines ordering of plugins otherwise the split in profiles will have side effects and make it a nightmare to maintain so even assuming it is not a bad idea it can nees v5 and rethink the build graph deeply.
Current workaround is a property injexted in the build deduced from maven version, guess it is sufficient. Le jeu. 23 mars 2023 à 23:04, Matt Nelson <[email protected]> a écrit : > I would like to ask if profile activation[1] on the maven version can be > (re)considered for inclusion into 4.0.0 > > I have a common base pom at work and was taking 4.0.0 for a spin and ran > into some issues where I needed to start flexing some config based on the > maven version. I think part of this is the nature of it being an alpha and > some other plugins(all 3rd party) not being ready for 4.0.0 yet. Based on > some of the other discussions[2] on this board, it looks like more plugins > may need to start flexing. If that is the case, then there would be even > more reason to introduce a new first class profile activator. > > [1] https://issues.apache.org/jira/browse/MNG-4760 > [2] https://www.mail-archive.com/[email protected]/msg129413.html >
