forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-1055) forrest.echo propery is always true if not commented out
Date Fri, 14 Nov 2008 00:32:44 GMT

    [ https://issues.apache.org/jira/browse/FOR-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647483#action_12647483
] 

David Crossley commented on FOR-1055:
-------------------------------------

Are you sure Gavin? There are other properties (e.g. forrest.validate) that can be set to
either true or false. Our Ant build files handle this. Perhaps this forrest.echo property
is not being handled consistently like the other properties.

> forrest.echo propery is always true if not commented out
> --------------------------------------------------------
>
>                 Key: FOR-1055
>                 URL: https://issues.apache.org/jira/browse/FOR-1055
>             Project: Forrest
>          Issue Type: Bug
>          Components: Other
>            Reporter: Michael Parker
>            Assignee: Gavin
>            Priority: Trivial
>
> The propertty forrest.echo  causes an echo of the settings only by its existence not
by the value.
> Example
> # Prints out a summary of Forrest settings for this project
> forrest.echo=false
> will lead to a print out.

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


Mime
View raw message