All,I have a parent pom, where I'm activating a profile based on the existence of the directory 'src/main/java'. I then have a multi module build where the children depend on the aforementioned parent pom.
When I build the modules using an aggregator pom, the profile isn't activated correctly. When building the modules one-by-one, the profiles are activated as expected. Is this the expected behavior? I would figure that even if built via an aggregator pom, the profiles should be activated when the modules are built because the path is relative to the individual module.
I've attached an example project to reflect what I'm talking about.
example.tar.gz
Description: application/gzip
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
