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 227269 - the IDE does not tell you when jsp files contain packages that no longer exist in the project
Summary: the IDE does not tell you when jsp files contain packages that no longer exis...
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 7.2
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-11 05:49 UTC by kingpoop
Modified: 2013-08-21 10:28 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (80.69 KB, text/plain)
2013-03-11 05:49 UTC, kingpoop
Details
clean and build should not be allowed when packages have been removed. (62.76 KB, image/jpeg)
2013-03-11 05:53 UTC, kingpoop
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kingpoop 2013-03-11 05:49:43 UTC
Product Version = NetBeans IDE 7.2 (Build 201207171143)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.6.0_37
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.12-b01
Comment 1 kingpoop 2013-03-11 05:49:49 UTC
Created attachment 132442 [details]
IDE log
Comment 2 kingpoop 2013-03-11 05:53:51 UTC
I think the IDE needs alot more work to make working with jsp files easier.  The IDE does not check jsp files very well.  see the pic.
this file was deployed to production and it took some time to figure things out.  this bug made it past tests, etc.
Comment 3 kingpoop 2013-03-11 05:53:54 UTC
Created attachment 132443 [details]
clean and build should not be allowed when packages have been removed.
Comment 4 Marek Fukala 2013-08-21 10:19:35 UTC
The main sore point is that the JSP files don't support refactoring of the java code. So if you remove/rename/move a class or package then JSP file won't be updated and  you won't see usages in the refactoring window.

There's also a subsidiary problem that the JSP file is not marked w/ an error badge if there's an error found by the JSP parser. The badging works for example for expression language expressions.
Comment 5 Marek Fukala 2013-08-21 10:28:28 UTC
I've file new bug for the second problem:

Bug 234704 - No error badge JSP file errors by the JSP parser 

The first problem is covered by following enhancement:

Bug 205599 - Rename refactoring in JSP is not supported!! 

Closing this isssue then.