You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Jean-Louis Boudart (JIRA)" <ji...@apache.org> on 2013/05/22 11:32:20 UTC
[jira] [Resolved] (EASYANT-54) Exceptions in initialization phase
of project are swallowed
[ https://issues.apache.org/jira/browse/EASYANT-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Louis Boudart resolved EASYANT-54.
---------------------------------------
Resolution: Fixed
Fix Version/s: 0.10
Patch applied on trunk.
Thanks for the contribution.
As you pointed out we're currently missing lot of test. So if you have one (even a regression one) it would be a great start :).
> Exceptions in initialization phase of project are swallowed
> -----------------------------------------------------------
>
> Key: EASYANT-54
> URL: https://issues.apache.org/jira/browse/EASYANT-54
> Project: EasyAnt
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.9
> Reporter: Tim Enderling
> Fix For: 0.10
>
> Attachments: EASYANT-54-EasyAnt-no-longer-swallows-exceptions-dur.patch
>
>
> BuildExceptions that are thrown when loading plugins during project initialization are not printed out. EasyAnt will just stop without a clue.
> An example of this can be found when using the {{parameter}} task directly inside the project element of a plugin, like in clean-std (which is not a good style anyway, but one of the places that I stumbled into):
> {code}
> <project name="org.apache.easyant.plugins#clean-std" xmlns:ea="antlib:org.apache.easyant">
> <ea:core-version requiredrevision="[0.9,+]" />
> <ea:parameter property="target" required="true" description="the target directory to clean" />
> <target name="clean-std:clean" description="clean project">
> <echo message="Cleaning ${target}..." />
> <delete dir="${target}" />
> </target>
> </project>
> {code}
> If {{target}} is not set, the usual message from the {{parameter}} task will not be printed.
--
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