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.
Hello, If you have a webapp with (2000) correct and a few (5) JSPs with residual errors, which do not allow an error free compilation, it is not possible to debug or test the webapp. In large projects a real killer to using Netbeans (Eclipse allows it). Please provide a warning but allow the build/run process to continue. I know one can remove the JPSs from the project or fiddle with the Ant build script, but they are in such cases fairly impenetrable to understand and this (continuation) should be the default. Web aps are large and mosts parts are independant of the others and can be tested independantly (not like a single desktop gui app). Thanks, John Muir
In case the reply is to modify the build script: The web app scripts are very complex and I know of no simple way to tell ant to ignore the result (success/failure) of a single prerequisite task. Anyway... continuation ought to be the NB default as the different parts of a web app (e.g. an complex ERP system) are fairly independent of each other and during development always have residual errors due to their size, fluidity and the number of developers working on them concurrently.
Reassigning to web for evaluation. I think this is _MUST_TO_IMPLEMENT_ to be competitive with eclipse.
Hi John, thanks for the report. However, as far as I know, NetBeans does not compile JSPs by default. There is a checkbox "Test compile all JSPs during builds" in the Web Project properties dialog (under "Compiling"), but this is off by default. What is the setting for your project? Also, can you please attach the error output from the build script? Is this error produced by Ant, or by the server on deployment? (And if it is the server, which server do you use?) Thanks, Petr Jiricka
Hi Petr, I guess I was not aware of the consequences of that checkbox, so I suppose it's not a defect. However, as it kept me from changing completely over to Netbeans from Eclipse for many months (and as your colleague prehak also seemed to be unsure) please consider the following suggestions (just for Webapp projects) to make the consequences more transparent.. At least either add a dependant checkbox similar to "JSP errors stop the build/run/debug" to the "Test compile all JSPs during builds" checkbox. (At the very least add a message to the build failed explaining how to work around this problem or pop up a "Confirm build abort due to JSP errors" alert.) Better still would be to continue the build but add all error messages & links to the source to a new rider "Errors" or "Issues" in the bottom window (beside 'Output'). This is the default behaviour in Eclipse and IMHO should also be the default for Netbeans. I'm pretty sure all J2EE developers working on large projects would agree on that. In spite of this one gripe, thanks to all for a really stunning IDE! John Muir
So I change this to enhancements. It's good idea.
Will this enhancement be included in version 6?
Probably, it depends on the time. I would like to do it.
moving opened issues from TM <= 6.1 to TM=Dev
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