Allow overriding runAlways plugins on project level

[Mobe91]

New feature, improvement proposal

Problem Statement

My use case is a multi-module project containing multiple modules with WAR packaging. I would like to make sure that the main WAR that includes other WARs is repackaged even if the cache kicks in because it needs to include updated versioning information in the final WAR artifact (using spring-boot-maven-plugin:build-info).
So, the maven-war-plugin should run always for the main WAR, but not for the other WARs.

Solution Proposal

Would it be possible to allow overriding the global runAlways plugins on project level by adding another project level property as described here?

[Mobe91]

I am closing this since I found that I can achieve what I want by configuring a non-default execution of the WAR plugin for the Maven module in question, and then specify this particular execution inside runAlways. Therefore, no project level configuration is required.