Community
Participate
Working Groups
Build ID: Version: 3.4.0 Build id: I20080523-0100 Steps To Reproduce: 1.Create an update site project based on a feature based on a plugin 2. Have an error in the plugin 3. Build All on the update site The result is an error message in logs.zip in the update site directory. More information: Errors in Eclipse belong in Errors Log or Problem View. However I understand that these are difficult to implement. An acceptable alternative would be to put the errors in a console view. I can help you get started with that solution, let me know. An acceptable but inferior implementation is a log file. If this is the only possible path, please at least link the log file in the popup error message. The current solution of zipping the log file is unacceptable. This pointless extra step forces users to open the log file with an external program and navigate to read their errors.
This is true. If you have a way to capture the ant log and embellish them to present them to the user, we would really be interested.
Log files and stdout are the only ways PDE/Build has to report errors, PDE/Build is first and foremost headless. Any improved error reporting must be done by UI.
(In reply to comment #1) > This is true. If you have a way to capture the ant log and embellish them to > present them to the user, we would really be interested. > Do you know where in the source the ant process is created? I assume it is triggered by Build All button and that the headless build just calls ant directly? (Meaning that new UI code to jam the ant log into a UI will not interfere with headless use case). Also precise details on what source would be the correct starting point would be a big help.
(In reply to comment #3) > Also precise details on what source would be the correct starting point would > be a big help. > The build/export is done by a set of operations. For update sites this is SiteBuildOperation, but the majority of the code is higher up in the hierarchy, specifically FeatureExportOperation. We have a build listener, ExportBuildListener, that tries to detect that an error occurred during the headless operation. Note that if this is fixed, it should be done in a way that it can apply to all of the export operations (features, plug-ins, products and update sites). They all use the same headless logging, though for the other operations we pop up a dialog containing the link to the zip (as the zip is not in the workspace).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
