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.
Finding Participant deployed an application and got the following error in build output. He didn't read the full error and didn't understand how to fix it. <a lot of text here> Trying to create reference for application in target server failed; The context root [...] in application [...] <continues off the screen> <hyperlink>...build-impl.xml:227: Deployment error:</hyperlink> <red>The module has not been deployed.</red> <red>See the server log for details.</red> <red>BUILD FAILED</red> See screenshot in URL Severity 1 participant didn't know how to proceed. Recommendation Improve formatting of the error output Do not send the user to the server log. Show only important messages in output window. Improve the error message text.
This is annoyoing especially when you are developing on a remote application server and cannot see the server.log as an output tab. (NB5.5dev 200605120200 + Glassfish)
Jano, I do not think that not showing the "See the server log for details." message is a good idea. In some cases looking in the server log is the best way how to find out why deployment failed. The long message "Trying to create reference for..." comes from the appserver plug-in (maybe directly from the server) and thus another issue should be probably filed against the plug-in. Couldn't be this solved by turing "Wrap text" option on by default?
This is a complicated problem and I don't think there's a simple solution for it like turning the text wrap on. Also sending the user to the current server log doesn't really help because the server log contains hundreds of lines and sometimes too many exceptions that's very hard to understand. There's a separate issue file for the server log. I see the following things would fix the problem: 1. In the output window show only problem description. Hide everything else like the regular ant build output. The problem description has to be well formatted (word wrap on, etc.). 2. The problem description has to be comprehensive and offering possible ways to fix it. The description cannot be hidden in the server log but show directly in the process output. This can only be achieved by looking at all possible problems that we can catch and report. Probably together with the app server team. 3. The output shouldn't show the link to build script (build-impl.xml). In general users don't test their build scripts. This should be optional, not shown by default. I'm sorry I cannot help here. I would recommend to make this a priority for the next release and plan for it. Then we can take a look at this issue, prepare UI spec, etc. I bet users would be very happy if we design better problem reporting.
If you insist on fixing #1 and #3, please file an issue against the whole IDE. Reassigning to sunappserv plug-in for evaluation whether #2 can be fixed, since it cannot be done from the j2eeserver.
Cannot change existing errors in AS 9.0 FCS. 9.1 will do much better, as this is a key focus. Noe the output tab of the IDE could wrap long lines, as a mimimum. The error message was at least there, assuming the user scrolls on the right side.
There is a popup on output tab to "Wrap Text". The user can activate it. Now the IDE does not provide a programatic API to turn this on, so the plugin cannot set it up. Open a different bug on openide APIs is you want the wrapping to be done by default, or if we need an API so that the plugin can turn it on.