Don't have the logs any more, but I suspect that tools/marvin/pom.xml uses the same property to activate both profiles, so marvin.setup gets run whenever -Dmarvin.config is specified.
On 4/9/13 6:07 PM, "Prasanna Santhanam" <prasanna.santha...@citrix.com> wrote: >Hi Chiradeep, marvin.test doesn't create the zone. I'll look at it again. >Do you have the logs of your run so I can see what might be wrong? > > >-- >Prasanna., > >----- Original Message ----- >From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >Sent: Wednesday, April 10, 2013 05:58 AM >To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> >Subject: Re: [MERGE] bvt branch to master > > > >On 4/9/13 12:57 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> >wrote: > >>Doesn't work for me >>A. -Dmarvin.config=setup/dev/advanced.cfg needs absolute path for some >>reason >>B. [INFO] --- exec-maven-plugin:1.2.1:exec (integration-test) @ >>cloud-marvin --- >>Usage: nosetests [options] >> >>nosetests: error: no such option: --with-marvin >> > >OK, 'B' got resolved by re-installing Marvin. > >New problem: >mvn -Pdeveloper,marvin.test complains that the zone is already created. >It seems to be creating the same zone created by marvin.setup > >
