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.
Skip deployment of war during development-phase. Usually during development you don't need the war file at all - you usually just change one or two files and immediately want to test what you changed by hitting 'run' - which should just copy the changed files to it's deployment directory and start up the server - DONE! ... Our project is quite large - so a typical war file will be around 70MB (megabytes), which takes around 1,5min to build each time i run the project and redeploy. This needs to be _WAY_ faster - incremental deployment should be at most around 5-10seconds. There should be a property to allow some 'fast' deployment, which should at least disable building the warfile until it is _really_ needed at the end of the development process, when it is actually deployed to the testserver or the productionserver. It should definately _not_ be deployed each time I change on or two jsp's or config-files. The waiting time for that is tiresome. Please supply some ui two disable war-deployment
Which server are you using? If appserver, did you try to switch incremental deployment on (Tools | Options -> IDE Configuration | Server and External... | J2EE Servers | Sun Java System... -> Directory Based Deployment Possible)? Is this what are you looking for?
I use Tomcat 5.0 (which I added to the Server Registry). With nb 3.6, there was no need to deploy the whole project somewhere else, it just used the directory structure, which you developed on. Therefore you if you only changed a jsp page or a html file, you only needed to reloaded the page in the browser and there you are... Although if you changed a jar or a class file you needed to redeploy by hand. Now the whole project is redeployed automatically every time, which 1.) Copies all changed pages to the dist directory (which is ok, seperate implementation and deployment) 2.) packages the whole thing -> war 3.) deployes it to the server 4.) and starts the server from scratch which will take 4min at least for our platform, since at least 1500 files are packaged including a 50MB database file and a lot preconfigurations need to be done on every startup... How can I mimic the behaviour of nb3.6 again, where I only needed to reload the changed page? Maybe some sort of quickdeploy should be implemented, which just copies changed files to the deploymentdirectory of the server without any restart of the server. If sources or jar's have been changed the user could be asked if a complete deployment should be made.
I agree with you - see duplicate issue 49542. Feel free to add comments/votes there. My comments: We use directory based deployment on Tomcat and it should work: 1) JSP on save is automatically "deployed" 2) Changed Java class after Build and Redeploy is deployed (you can additionally turn on some hot-deployment Tomcat switch in Tomcat's settings) 3) Workaround "How to turn it off" is: modify your build.xml - add these lines: <target name="-do-dist-with-manifest" if="has.custom.manifest" depends="init,compile,compile-jsps,-pre-dist"> </target> *** This issue has been marked as a duplicate of 49542 ***