why activate with properties, better to just activate the profile you want, e.g.
mvn -Pdev clean install also, you will need to put all the modules you don't want run with that profile into a separate profile (probably one that is activeByDefault) that way when you specify -Pdev (which will deactivate all profiles and activate the one you specify) only the module(s) you want will be active in your project model 2009/11/4 chicagopooldude <[email protected]>: > > Stephen, > Thanks for your reply I have tried profile with no success here is what I > am doing and this is located in parent pom. > <profile> > <id>dev</id> > <activation> > <property> > > <name>env</name> > <value>dev</value> > </property> > > </activation> > <modules> > <module>client</module> > </modules> > </profile> > >> mvn -Denv=dev clean install > This is how I am evoking this profile but nothing is happening and all the > sub modules are getting cleaned up. When we specifiy a name value pair in > activation element how to envoke it from command line, I also dont want to > put some thing specific in settings.xml. > > Any help is appreciated. > > Regards > Seshu Pitcha (CME Group Chicago IL) > > > -- > View this message in context: > http://old.nabble.com/Specifying-a-different-POM-file-tp26160205p26197443.html > Sent from the Maven - Users 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]
