Yes, please enter this an an issue in JIRA. Thanks for discovering this issue and taking the time to find a fix as well as the root cause. Makes my job a lot easier! ;-)
Matt On Thu, Jan 8, 2009 at 6:38 PM, songsp <[email protected]> wrote: > > I did a little more research on maven profile inheritance. Found this thread: > http://www.nabble.com/Profile-inheritance-td8259757.html > > "Profiles are not inherited, period." > > So it looks like in an AppFuse modular application, the "prod" profile > defined in the parent pom cannot be invoked using -Pprod in the core module. > This profile should probably be moved to the core pom in a modular > application. Seems like a defect to me, is it a good idea to report this in > jira? > > > > songsp wrote: >> >> Hi, >> >> I was trying to populate my production database with default data (instead >> of the sample-data.xml file in the test resources). I searched the wiki >> and mailing list and it looked like I should use this command: >> >> mvn -Pprod dbunit:operation >> >> I run the command in the core directory and found my database was still >> initialized with test data (with negative primary keys). Then I noticed >> that the prod profile was in the parent pom while I was running the >> command in the core directory - maven does not seem to inherit profiles >> from parent POM. >> >> Moving the prod profile from the parent POM to core/pom.xml solved my >> problem - now my database is populated with records from default-data.xml. >> My question is, should AppFuse move the prod profile to core/pom.xml in a >> modular application by default so that it works out of the box? Or did I >> miss anything? >> >> Thanks! >> > > -- > View this message in context: > http://www.nabble.com/The-prod-profile-in-the-POM-in-a-modular-application-tp21357730s2369p21364739.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
