Configures your container in a specific directory |
The standalone configuration allows configuring your container so that it is setup to start in a directory you choose (see the configuration page for more general explanations).
Whenever you configure or start a container which uses a standalone configuration, Cargo will:
The reason for this behavior is reproducibility which is for example very useful for automated testing. If you wanted to keep a generated configuration you could ask Cargo to generate a standalone configuration once and then consider it an existing configuration.
There are different ways of using a standalone configuration:
{snippet:lang=java|id=configuration-typed-resin3x|url=https://raw.githubusercontent.com/codehaus-cargo/cargo/master/core/documentation/src/main/java/org/codehaus/cargo/documentation/Snippets.java} |
DefaultConfigurationFactory
which automatically maps the right implementation for the container you're using. For example:{snippet:lang=java|id=configuration-untyped-resin3x|url=https://raw.githubusercontent.com/codehaus-cargo/cargo/master/core/documentation/src/main/java/org/codehaus/cargo/documentation/Snippets.java} |
<cargo containerId="resin3x" [...]> <configuration type="standalone" home="target/resin3x"/> [...] </cargo> |
[...] <container> <containerId>resin3x</containerId> [...] </container> <configuration> <type>standalone</type> <home>target/resin3x</home> </configuration> [...] |
Note that the standalone configuration is the default for the Maven plugin so specifying only the following would also work:
[...] <container> <containerId>resin3x</containerId> [...] </container> [...] |