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 bui
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
