Hi,
I am trying to deploy a deployable on 2 instances of an InstalledLocalContainer using different configurations.
To achieve this I use a maven configuration similar to this one:
http://old.nabble.com/Multiple-Tomcat-Containers-and-Not-Automatically-deploying-Maven-2-project-artifact-ts7631458.html#a7631458.
My configuration defines 2 executions (different ids) calling cargo goal 'start' with different parameters for underlying StandaloneLocalConfiguration.
It looks like from my tests that the configuration of second execution is ignored (non-existent class for implementation node doesn't generate errors).
As the InstalledLocalContainer I am using is a custom implementation (no plugin available for this container) I am wondering if this kind of scenario is supported or if the implementation is wrong.
Could someone confirm if this use case is supported by cargo?
Thanks,
Julien
