In [1] it is stated: "All profiles that are active by default are automatically deactivated when a profile in the POM is activated on the command line or through its activation config."
So, it's not a bug but the expected behavior. /Anders [1] https://maven.apache.org/guides/introduction/introduction-to-profiles.html On Mon, Jun 8, 2015 at 2:10 PM, Alexander Kriegisch < [email protected]> wrote: > Hi Jenkins experts. > > When I do something like > > mvn help:active-profiles > > for a module defining a profile inside its pom.xml with activeByDefault > set to true, the corresponding profile is indeed active in addition to any > profiles defined in settings.xml. > > Now when I do > > mvn help:active-profiles -P Foo > > I see that Foo is active, the profiles from settings.xml are, too, but the > profile from pom.xml is inactive. I would expect it to remain active > because I have not specified anything like -P !MyPomProfile. > > I have tested with Maven 3.2.5, 3.3.1, 3.3.3, same behaviour in each > version. > > Is my expectation wrong (the manual does not contradict it, at least) or > is this a bug? > > Regards > -- > Alexander Kriegisch > http://scrum-master.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
