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.
Summary: | Poor performance of JavaDataNode.checkUpToDate | ||
---|---|---|---|
Product: | java | Reporter: | _ tboudreau <tboudreau> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | tzezula |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Naive patch to use the fast up-to-date check if a system property is set |
Description
_ tboudreau
2004-01-28 12:04:49 UTC
Created attachment 13113 [details]
Naive patch to use the fast up-to-date check if a system property is set
Makes sense. Even though it is not cheap to find out all compilers and ask them for the output dir. Cc Tomas to take this into account for stavbicka > Even though it is not cheap to find out all compilers and
> ask them for the output dir.
Shouldn't it be possible to do that check once per run of NetBeans unless something
actually changes?
Sure, it should. But I looked at current apis and I am not aware of any that allows to find out destination folder of the compiler type. So it is possible just for java compiler types. In case of eg ant script compiler it will not work. Well, stavbicka is a great opportunity to improve the APIs. Any case where separation of concerns results in information resolution loss (which is what this is) is probably something that should be revisited. This issue is no longer relevant since the code was completely rewritten. |