|
|
Re: Buckminster build does not provide sufficient information to identify missing dependencies [message #754522 is a reply to message #754465] |
Wed, 02 November 2011 22:01 |
|
Output that ends up in that log is normally related to a misconfiguration. Output from the build should go to the
console and to the ${workspace_root}/.metadata/.log
Missing required plug-ins should be detected (and printed) by the PDE compiler in the build step. Not sure why that gets
cloaked in your case. Perhaps it's due to something in your ant script?
- thomas
On 2011-11-02 16:52, Matthew Webber wrote:
> Further investigation shows that there is some of the diagnostic information I need in
> ~/.eclipse/626335158/configuration/1320234741097.log, which is not an obvious place to look, but anyhow ...
>
> Normally I guess that log would be in the directory containing my Buckminster install. However, that directory is
> network shared, read-only, so that multiple users can use it simultaneously. Hence the log redirects to ~/.eclipse
> instead, as described in the Eclipse documentation on multi-user installs.
>
> Matthew
>
|
|
|
Powered by
FUDForum. Page generated in 0.03196 seconds