Subject: Exported From Confluence
Content-Type: text/html; charset=UTF-8
Discussion on the design of the Ant tasks.
Here are the main discussions we had about the Ant tasks for Cargo:
- Remove cargo-XXX tasks : Actually there's one task =
for each container Id. It's not really evolutionary and works only with the=
containers referenced in the default Containers factory. We prefer to remo=
ve these aliases (CARGO-132) and to keep the generi=
c one using either a container id as referenced in the default containers f=
actory or the name of the container class.
- Create a separate task for ZipUrlInstaller : The zi=
pUrlInstaller is actually a sub-element of the cargo task. We propose (CARGO-75) to extract it in a real task to be able to reu=
- Create a separate task for deployers : We can't reu=
se deployables between several servers and we can't have actually a remote =
deployer. We did a proposal (Thread) seve=
ral months ago to solve this.
- Extract configuration in an external (XML) file : W=
e discussed several times (Thread, CARGO-135) about to store the confi=
guration in a file instead of in the build script.