Hi,
we maybe abused file activation a bit and turned on specific packaging plugins using marker file to activate profiles defined in our company pom. Executions and configurations are already defined in the company pom's pluginManagement section as well. So e.g. switching on 3 plugins we use to create DEB files from JARs could be activated for single modules in a reactor project by touching a file `module1/.companypom-profiles/create-deb`. However with Maven 4 RC3 we found that this does not work anymore. `mvn help:active-profiles` does not show the profiles with Maven 4 either while Maven 3.9.9 does, so basically it must be the core which changed behavior. I understand that using such an approach is at least unusual. I mostly want to know whether this is on purpose or a bug. Best Regards Mirko Friedenhagen -- Sent with my mobile --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
