Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 0.3
-
Fix Version/s: None
-
Component/s: Ant
-
Labels:None
-
Number of attachments :
Description
I would like to propose to move the ZipURLInstaller out of the <cargo-*> tasks. Indeed, the installer is something that should be used before calling the cargo tasks (same as when using the Java API).
Thus I propose to create a special task for the installer:
<cargo-installer installURL="..." installDir="..." homeDirProperty="..."/>
where homeDirProperty points to a property that will hold the location of the installed container home.
Activity
Vincent Massol
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Component/s | Ant [ 11432 ] |
Vincent Massol
made changes -
| Workflow | jira [ 29122 ] | Cargo [ 54971 ] |
We can create a task like this :
<installer type="zipUrlInstaller" installUrl=".../...zip" installDir="..." id="AAA">
<proxy host="..." port="..." user="..." password="..." excludeHosts="..."/>
</installer>
And in the container we define either a homeDir attribute, an installerRefId attribute or an inner installer element ?