Ant Task for Jelastic Cloud Platform

Apache Ant is an open source software tool for automating software build processes. It is best suited to building Java projects. Ant supplies a number of built-in tasks allowing to compile, assemble, test and run Java applications. It is extremely flexible and does not impose coding conventions or directory layouts to the Java projects which adopt it as a build tool.
Ant uses XML to describe the build process and its dependencies. By default the XML file is named build.xml.
Use this configuration for Ant.
You have to define the tasks you use in your build file:
<ivy-module version="2.0">
    <info organisation="com.jelastic" module="jelastic-ant-task"/>
        <dependency org="org.codehaus.jackson" name="jackson-mapper-asl" rev="1.8.1"/>
        <dependency org="org.apache.httpcomponents" name="httpcore" rev="4.1.1"/>
        <dependency org="org.apache.httpcomponents" name="httpclient" rev="4.1.1"/>
        <dependency org="org.apache.httpcomponents" name="httpmime" rev="4.1.1"/>
        <dependency org="commons-codec" name="commons-codec" rev="1.4"/>
        <dependency org="commons-logging" name="commons-logging" rev="1.1.1"/>

Configure the build file:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns:ivy="antlib:org.apache.ivy.ant" name="Jelastic Test Task Deploy" basedir="." default="deploy">

    <property name="lib.dir" value="lib"/>
    <property name="ivy.default.ivy.user.dir" value="${basedir}/lib"/>
    <property name="ant.lib.task" value="${basedir}/lib-task/jelastic-ant-task-1.0.jar"/>

    <path id="">
        <fileset dir="${lib.dir}"/>
        <fileset dir="${ant.lib.task}"/>

    <target name="deploy" description="Use the Task">
        <ivy:retrieve pattern="${lib.dir}/[artifact].[ext]" type="jar" />

        <taskdef name="jelastic" classname="com.jelastic.Jelastic" classpathref=""/>
        <jelastic email="<!-- ... -->"
                  password="<!-- ... -->"
                  dir="<!-- ... -->"
                  filename="<!-- ... -->"
                  context="<!-- ... -->"
                  environment="<!-- ... -->"

What's next?