Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Message-ID: <20952746.210161275883918285.JavaMail.jira@thor>
Date: Mon, 7 Jun 2010 00:11:58 -0400 (EDT)
From: "David Crossley (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Updated: (FOR-535) Create a plugins task for ANT
In-Reply-To: <1975057906.1118392366158.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FOR-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-535:
-------------------------------

    Affects Version/s: 0.8
                       0.9-dev

> Create a plugins task for ANT
> -----------------------------
>
>                 Key: FOR-535
>                 URL: https://issues.apache.org/jira/browse/FOR-535
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Plugins (general issues)
>    Affects Versions: 0.7, 0.8, 0.9-dev
>            Reporter: Ross Gardler
>
> The ant file for loading and mounting plugins is horribly complex now that we are using versioned plugins. I've used lots of if elements and mutable properties from the ant-contrib package. In my view when you overuse these tasks it generally means you should have a specialised ANT task to handle the logic. ANT is not supposed to be a programming language.
> We need to create an ANT task for the handling the installation of plugns so that we have more control over what is going on (for example, we can remove the need to have an unversioned plugin to fall back on).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.