I am wondering if the OP is hitting the "must have a named profile in the aggregation root" that I have observed, but not determined whether it is a bug or a feature.
If I have a multi-module project and one module 'web' has a profile called "run". mvn -Prun clean install -f web/pom.xml will activate the "run" profile mvn -Prun clean install does not seem to activate the "run" profile unless I put an empty profile called "run" in the root of aggregation Now of course I'm doing some seriously fancy sh1t and the above is simplified, so it might not be that clear-cut... but none the less, I am wondering if the OP is seeing something like that On 26 August 2011 08:16, Wayne Fay <wayne...@gmail.com> wrote: >> The mysql-test profile is to test the dao layer, layer that is found in the >> "core" module. >> >> So, this mysql-test profile should sit in the "core" pom file. >> >> Otherwise, some of this profile properties would not be found in another >> "view" module. > > So remind us again, what is the problem you are trying to solve, what > have you done so far, and why did that not work? I'm lost. You should > be able to just copy profiles and properties around and make things > work trivially. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
