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 144609 - Misleading deploy-on-change feedback when changing non-java files
Summary: Misleading deploy-on-change feedback when changing non-java files
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker with 2 votes (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-20 16:53 UTC by malfunction84
Modified: 2016-07-07 08:54 UTC (History)
1 user (show)

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 malfunction84 2008-08-20 16:53:25 UTC 
This situation was encountered using a Tomcat 5.5 Web Project in NB 6.5 beta.

If "Deploy on Change" is enabled, NB will deploy the project even when only a JSP file changes.  There is no reason to
redeploy when a JSP file changes.  The JSP compiler (e.g. Jasper) takes care of that by detecting changes and
recompiling the JSP as necessary.  (This is how this feature worked in previous versions of NetBeans like 6.1.)  These
unnecessary redeploys slow down development.

Redeploying when a JSP changes is only really necessary if antiResourceLocking="true" in the project's context.xml file.
Comment 1 _ ludo 2008-08-20 17:09:27 UTC 
same for GlassFish: Only changes in *.java files should trigger a real compile an project deploy.
For html, jsp, images, script files (js, json,...) the behavior of 6.1 (copy file on save both on project source and
build area) is enough.
Currently, for JSP/html users, it seems a regression from 6.1 to do a real redeploy on file save, as opposed to a mere
file copy in the build area.
Comment 2 malfunction84 2008-09-12 20:26:02 UTC 
Changed summary.  Previously: "NB should not redeploy when a JSP file changes"

The in-place deployment may be more complicated than we think it is, but the only time a redeployment should occur is
when a file is copied to build/web/WEB-INF/classes/
Comment 3 Petr Hejl 2008-09-15 12:08:23 UTC 
I tested with tomcat 5.5 and beta and web app is not redeployed when JSP is changed. It provides UI feedback that
"server & IDE is handling it" but this does not necessarily mean real redeployment.

This bug was found GFv2 plugin and has been fixed already. Issue 144756.

Do yo report that real app redeployment is made for JSP?
Comment 4 Petr Hejl 2008-10-02 12:58:54 UTC 
No response from reporter. Closing as WORKSFORME.
Comment 5 malfunction84 2008-10-02 23:02:17 UTC 
Sorry, I actually can't test it anymore.  Thanks to issue 141921, I can't even deploy my project.

I'll try updating to one of the nightly builds.  If it still occurs, I'll reopen.
Comment 6 malfunction84 2009-01-08 20:00:41 UTC 
You're right.  An actual redeployment is not happening in 6.5 (Build 200811100001).

Still, feedback is provided as if a deployment is happening.  Could this misleading feedback be suppressed?  Updating a
JSP is instantaneous, yet sometimes the "deploying..." progress bar stays up for 10-20 seconds after the JSP file has
been saved.  The changes have already been made and are even visible when you access the page, but this progress bar
indicates that the IDE is still performing some deployment-related work when it clearly isn't.

Changed summary (was "Unnecessary deploy-on-change when changing non-java files") and priority (was P3).
Comment 7 Martin Balin 2016-07-07 08:54:15 UTC 
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss