Re: [platform-releng-dev] 4.6.0 N-Build: N20150908-2000 -BUILDFAILED

["David M Williams" <david_williams@xxxxxxxxxx>]

> From: Daniel Megert <daniel_megert@xxxxxxxxxx>
> To: "Eclipse platform release engineering
list." <platform-releng-
> dev@xxxxxxxxxxx>, 
> Date: 09/09/2015 02:54 AM
> Subject: Re: [platform-releng-dev] 4.6.0 N-Build:
N20150908-2000 - 
> BUILD FAILED
> Sent by: platform-releng-dev-bounces@xxxxxxxxxxx
> 
> > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-
> plugin:0.23.1:compile (default-compile) on project 
> org.eclipse.core.tests.resources: Compilation failure: Compilation
failure: 
> 
> Why does the entire build fail because of a compile error in a test
> bundle? I thought we publish those builds that have no errors. 

In short, we continue "as much as we reasonably
can". If Tycho had it's (default) way, 
it would stop at the first compile error ... we at
least continue compiling in case there's 
additional ones to know about. 

I believe the PDE build could "continue further"
since it's builds were feature based ... 
easy to distinguish runtime code from test code. Plus,
I, as I recall, I think PDE would still 
"assemble" the bundle, even if it had compile
errors, whereas Tycho will not. 

Since Tycho is Git repository based, there is no easy
way to tell if test or runtime code caused the failure. 
And, even if we could do some "custom coding"
to get around that, I am not sure how far we 
could get with it before Tycho would fail again due
to it's own ideas of what 
it should build, and what it should not. (For example,
it would at least fail at creating 
p2 repositories, because something would be missing.)

Hope that helps. If anyone knows something I don't,
let me know.