On 23 March 2013 17:53, prasanna <t...@apache.org> wrote: > On 23 March 2013 01:49, Chip Childers <chip.child...@sungard.com> wrote: >> >> OK - Next errors: >> >> mvn -Pdeveloper,marvin -Dmarvin.config=setup/dev/advanced.cfg -pl >> :cloud-marvin integration-test >> [INFO] Scanning for projects... >> [INFO] >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] >> [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin --- >> [INFO] >> [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ >> cloud-marvin --- >> [INFO] >> [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ >> cloud-marvin --- >> [INFO] >> [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ >> cloud-marvin --- >> [INFO] >> [INFO] --- exec-maven-plugin:1.2.1:exec (integration-test) @ cloud-marvin --- >> Usage: nosetests [options] >> >> nosetests: error: no such option: --with-marvin >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE > > Awesome! Thanks for trying Chip. I think you may have forgotten to > register the marvin-nose plugin with nose > > $ cd tools/marvin/marvin > $ pip install . > > I'll combine the two pip install steps so it's only one Marvin installation.
This is done. You don't have to register marvin with nose anymore. It's done as part of marvin install now. I've corrected the wiki(s) with this information. Also a good time to enhance marvin to use ApiDiscovery like cloudmonkey does so that new APIs included can be tested along with this mvn+marvin integration.
