Thanks. I was hoping that it would evaluate the file-based activation per project. I was treating it as a separate issue than the multiple conditions. But I think what you're saying is that the profile activation happens once for the whole reactor, and not per project within the reactor. I gather that you're saying if the keystore file doesn't exist when I first run maven, then the keystore profile will be activated for all projects in the reactor. Is that correct? I'm still seeing the keystore profile activate from the property alone even if the keystore file already exists before I run the mvn command. So that still suggests that it's doing an or of the conditions rather than an and. Running 'mvn -N -X help:active-profiles -Djarsigner.keystore.scm.url' isn't giving any debug info on the profile activation unfortunately.
My goal here is to have as much of the build process as possible self-contained in the POM files and executed from a single mvn command. > -----Original Message----- > From: Jörg Schaible [mailto:joerg.schai...@gmx.de] > Sent: Tuesday, November 10, 2015 4:26 PM > To: users@maven.apache.org > Subject: [EXTERNAL] RE: profile activation with multiple conditions > > Justin Georgeson wrote: > > > So here's a minimal parent pom.xml, which lists 2 child modules that I > > created with 'mvn archetype:generate' choosing the > > 'maven-archetype-quickstart' archetype. My goal was that if I > > > > mvn package > > > > Then the compile/test/package occurs with no attempt to sign. But then > > by changing the command to > > > > mvn package -Djarsigner.keystore.scm.url=... > > -Djarsigner.keystore.scm.user=... -Djarsigner.keystore.scm.password=... \ > > -Djarsigner.storepass=... > > > > Then it checks out a single copy of the keystore during the package > > phase of the parent project, and the jarsigner profile automatically > > activates during each of the modules due to the presence of the keystore > > file. > > > > Instead it's deleting the keystore and checking out the keystore file > > during every project (or instead of and of profile activation > > conditions), and the jarsigner profile is not automatically activated. > > Profile activation is quite the first thing Maven does. So, the file has to be > already there when Maven starts. > > Form your description I got the impression that you "create" somehow the file > during the build and expects then that Maven takes it into consideration for > profile activation. That will never happen. And this has nothing to do with > multiple profile conditions. > > Cheers, > Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org
