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.
Environment: Maven 3, Tomcat 7, Netbeans Dev 201309270002, jdk 1.7_40 Reproduce: Create new Maven web project, point it to tomcat instance. Add javascript file with simple console.log call Deploy Open project properties, go to 'Run' and uncheck deploy on save. Edit index.jsp, reload page in browser (update works as expected) change message in javascript file, save (reload page, JS message NOT updated) Have encountered this for both older existing projects and new projects as well. Let me know if you need anything else for details.
Thanks for the report. I think this might be related to the enhancement I have implemented recently (Copy on Save for static resources). I'll take a look at it and let you know if I need something else.
Fixed by change-set: web-main #a6191e1a0101 Also "css" extension were added as static resource.
Integrated into 'main-silver', will be available in build *201310010002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/a6191e1a0101 User: Martin Janicek <mjanicek@netbeans.org> Log: #236485 - JS files not copied on save in maven web projects
I have the same problem for .cfm files, which I registered a text/html file I see from http://hg.netbeans.org/main-silver/rev/a6191e1a0101 that you consider a file as a "static resource" using the file extension I propose these enhancements: - consider files as "static resources" using MIME type mapping (every thing that is text/html, text/css, text/javascript....) - consider files as "static resources" which is not to be "compiled", so for example everything which is not .java - add a flag "Consider this file type as a static resource" on file extension options
Thanks for proposals. Changing to enhancement for now, setting TM = Next
Is it possible to known where "NM" fill be released ? My team cannot upgrade NetBeans to 8.0 (so we are stuck to 7.4) because for each change to static files we have to perform a full Run/deploy of the webapplication
sorry for typo....I meant "when next milestone will be released?"
Already fixed (change-set: web-main #de73823c63e8) within an issue 218345 *** This bug has been marked as a duplicate of bug 218345 ***