Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Tue, 21 May 2013 21:38:20 +0000 (UTC)
From: "Tim Enderling (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: <JIRA.12648679.1369158261571.358.1369172300002@arcas>
In-Reply-To: <JIRA.12648679.1369158261571@arcas>
References: <JIRA.12648679.1369158261571@arcas>
Subject: [jira] [Updated] (EASYANT-55) The attribute onMissingExtensionPoint
 of the bindtargets task is ignored
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tim Enderling updated EASYANT-55:
---------------------------------

    Attachment: EASYANT-55-EasyAnt-respects-the-onMissingExtensionPo.patch

The attached patch is based on the current trunk (SVN revision 1480665).

It addresses the issue by the following changes:
* {{ProjectUtils}} will actually read the third field in the extension infos (if given) instead of using {{OnMissingExtensionPoint.FAIL}} as behavior for all bindings to missing extension points.

I know that extension points are originating from EasyAnt and the EasyAnt's {{bindtarget}} task doesn't have this attribute, but it's odd that the code in EasyAnt's {{ProjectUtils}} knows of {{OnMissingExtensionPoint}}, but does not know that it can be specified in the third array field. Also I was wondering, why those extension infos are presented as arrays. Is there a good reason for this or just convenience that prevented the developer from properly using the type system? ;-)

Like for my patch for EASYANT-54, I could provide a simple test case here to prevent re-breaking.
                
> The attribute onMissingExtensionPoint of the bindtargets task is ignored
> ------------------------------------------------------------------------
>
>                 Key: EASYANT-55
>                 URL: https://issues.apache.org/jira/browse/EASYANT-55
>             Project: EasyAnt
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.9
>            Reporter: Tim Enderling
>         Attachments: EASYANT-55-EasyAnt-respects-the-onMissingExtensionPo.patch
>
>
> When using the {{bindtargets}} task that is now part of Ant with a non-existing extension point, EasyAnt will complain about the missing extension point and fail, no matter which value was specified for the {{onMissingExtensionPoint}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira