Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Definition

Excerpt

Configures your container in a specific directory

Explanation

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 delete :

  • Delete the configuration directory

...

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.

Support Matrix

Java

Ant

Maven2

IntelliJ IDEA

Netbeans

(tick)

(tick)

(tick)

(question)

(question)

Java API

There are different ways of using a standalone configuration:

...

Wiki Markup
{snippet:lang=java|id=configuration-untyped-resin3x|url=http://svn.codehaus.org/cargo/core/trunk/documentation/src/main/java/org/codehaus/cargo/documentation/Snippets.java}

Ant Task

Code Block
xml
xml

<cargo containerId="resin3x" [...]>
  <configuration type="standalone" home="target/resin3x"/>
  [...]
</cargo>

Maven2 Plugin

Code Block
xml
xml

[...]
<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 2 plugin so specifying only the following would also work:

Code Block
xml
xml

[...]
<container>
  <containerId>resin3x</containerId>
  [...]
</container>
[...]