This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 25785 - The default value of usefile attribute in <formatter> element is true
Summary: The default value of usefile attribute in <formatter> element is true
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
: 30768 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-07-18 16:26 UTC by Milan Kuchtiak
Modified: 2004-01-28 18:41 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kuchtiak 2002-07-18 16:26:47 UTC
Look at the usefile atribute in <formatter> element 
(subelement of <junit>).
It is defaultly defined as true, but if you look at 
the "usefile" property on the formatter node - there 
is "False".
Comment 1 Jesse Glick 2002-07-19 15:37:27 UTC
Ant provides no metadata from tasks re. what the default values of
attrs are, nor re. which attrs are optional and which required. The
property in the property sheet has to show something in case there is
no value set in the XML.
Comment 2 Milan Kuchtiak 2002-07-19 15:49:14 UTC
However its strange when usefile attribute(in property 
sheet)  has value False and inspite of this output file is 
created to some external file.

I know that the syntax is missing (there are no default 
values in Ant) but logically its an issue.
Comment 3 Jesse Glick 2002-07-19 16:46:23 UTC
I suppose so. Ideally the property sheet could show True, False, and
<Undefined>. However this would require a custom property editor, I
think. Not sure what the situation is re. properties of other types -
requires investigation as to use of getValue()==null for various
property editors (it is not supported for Sun's default boolean editor
at least).
Comment 4 David Konecny 2003-02-06 15:47:01 UTC
*** Issue 30768 has been marked as a duplicate of this issue. ***
Comment 5 Jesse Glick 2003-12-19 15:39:33 UTC
getValue -> null should work these days.
Comment 6 Jesse Glick 2004-01-28 18:41:31 UTC
Fixed in same commit as issue #33055.