[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [e4-dev] 0.11 Integration Build: I20110217-2100
|
On Fri, Feb 18, 2011 at 7:18 AM, Branekov, Danail
<danail.branekov@xxxxxxx> wrote:
Paul, is there “know-how” on reading the build log file? I inspected the log (which is larger than 16M) and found a couple of error entries regarding org.eclipse.e4.tools.ui.designer: lines 139869, 140079, 148902, etc
Here is an example (line 148902)
[javac] ----------
[javac] 1517. ERROR in /opt/public/eclipse/e4/build/e4/downloads/drops/4.0.0/I20110217-2100/plugins/org.eclipse.e4.tools.ui.designer/src/org/eclipse/e4/tools/ui/designer/wizards/E4NewProjectWizard.java (at line 364)
[javac] application.getBindingContexts().add("org.eclipse.ui.contexts.dialogAndWindow");
[javac] ^^^
[javac] The method add(MBindingContext) in the type List<MBindingContext> is not applicable for the arguments (String)
[javac] ----------
How did you know that the issue is because of tagging?
They're using an old version of the model. The first time it failed last night with the swt.renderers.cocoa fragment I concluded I didn't tag it (since I don't have it open on linux). In this case I assumed a tagging mistake, but this is actually XWT code that hasn't been updated to the new model contribution.
AFAIK there isn't really a "know-how". Our build is actually composed of 2 PDE builds. The first one builds Eclipse SDK 4.1 and the second builds e4 0.11. Each PDE build is composed of 4 parts: the fetch, the resolve of bundles, the compile, and then producing something useful (our zips and tars).
This kind of compile error can indicate that the incorrect version of that plugin is being built ... or in this case, hasn't even been fixed yet.
There might be more heuristics, but my coffee hasn't kicked in yet :-)
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
