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 9304 - JSP compilation is never considered up-to-date
Summary: JSP compilation is never considered up-to-date
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 minor (vote)
Assignee: Petr Jiricka
URL:
Keywords:
Depends on:
Blocks: 8997
  Show dependency tree
 
Reported: 2001-01-30 19:38 UTC by Jesse Glick
Modified: 2004-02-04 20:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2001-01-30 19:38:16 UTC 
[dev jan 30]

When I have a Java source, and F9 to compile, then F9 again, it says it is up to
date and no need to recompile. This is because the Compiler impl correctly
implements isUpToDate(). For JSPs, though, it is never considered up to date; F9
always recompiles the JSP, even though nothing has changed in the interim.
Mildly annoying.
Comment 1 Jan Chalupa 2001-03-12 12:23:31 UTC 
Version: 'Dev' -> 3.2
Comment 2 Jan Chalupa 2001-05-06 15:48:14 UTC 
Target milestone -> 3.3
Comment 3 Petr Jiricka 2001-06-18 08:59:15 UTC 
This was partially fixed - when the page is up to date, the compiler does 
nothing. However, it still looks like it compiles smething. It should write 
the "nothing was compiled, everything is up to date" message.
Comment 4 Jan Chalupa 2001-11-27 17:37:14 UTC 
Target milestone -> 3.3.1.
Comment 5 Marek Grummich 2002-07-22 12:14:45 UTC 
Set target milestone to TBD
Comment 6 Marek Grummich 2002-07-22 12:25:41 UTC 
Set target milestone to TBD
Comment 7 Petr Jiricka 2004-02-04 20:19:42 UTC 
Fixed by replacing JSP compilation by JSP validation.
Comment 8 Petr Jiricka 2004-02-04 20:34:17 UTC 
Forgot to change the state to FIXED.