Frequently Asked Questions

General

  1. What does the Virtualization Maven Plugin do?
  2. What virtualization platforms are supported by the Virtualization Maven Plugin?
  3. I have written an implementation of the vcc-api for my virtualization platform, how can I use this with the Virtualization Maven Plugin?

General

What does the Virtualization Maven Plugin do?

The Virtualization Maven Plugin provides a means to control virtual computers running on a virtualization platform from within a Maven project

[top]
What virtualization platforms are supported by the Virtualization Maven Plugin?

The Virtualization Maven Plugin uses the Virtual Computer Control project's API to control virtualization platforms, so if your virtualization platform is supported by Virtual Computer Control, then it is supported by the Virtualization Maven Plugin.

[top]
I have written an implementation of the vcc-api for my virtualization platform, how can I use this with the Virtualization Maven Plugin?

Firstly, would you be interested in having your implementation hosted by the Virtual Computer Control. Please email the VCC Developer Mailing List to see about getting your implementation hosted.

Secondly, it is not necessary to have your implementation hosted by the Virtual Computer Control project. Assuming you have your implementation installed in either your local repository, or a remote repository which you have configured in either your pom.xml or in your settings.xml, all you need to do is add your implementation as a dependency of the Virtualiazation Maven Plugin, e.g. 

<project>
  <build>
    <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>virtualization-maven-plugin</artifactId>
        <version>0.0.1-alpha-1-SNAPSHOT</version>
        ...
        <dependencies>
          <dependency>
            <groupId>your impl's groupId</groupId>
            <artifactId>your impl's artifactId</artifactId>
            <version>your impl's version</version>
          </dependency>
        </dependencies>
        ...
      </plugin>
    </plugins>
  </build>
</project>
[top]