Re: [platform-releng-dev] 4.3.0 I-Build: I20130429-2000 - BUILD FAILED

[David M Williams <david_williams@xxxxxxxxxx>]

At least we are building, and signing,
again. This build failure is due to something else. I'm not exactly sure
exactly what, but I have seen before: 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465

I think basically a combination of the
way the "comparator" pulls old bundles, if qualifiers match,
and the way that JDT does some "custom combination" of classes
... from different bundles, I believe? If so, I'm not sure this can be
cured by a tool fix (at least, in any quick/easy way) and the JDT Team
may have to get in the habit that if they change one of those bundles involved
in custom "callback", then they will have to touch the  other
one too, so that they are both seen as "new" and unsigned and
unpacked at the right time? 

But ... I really do not understand to
core problem very well ... am hoping it make more sense to someone from
JDT? 

Thanks, 





From:      
 e4Builder@xxxxxxxxxxx
To:      
 platform-releng-dev@xxxxxxxxxxx,

Date:      
 04/29/2013 09:50 PM
Subject:    
   [platform-releng-dev]
4.3.0 I-Build: I20130429-2000 - BUILD FAILED
Sent by:    
   platform-releng-dev-bounces@xxxxxxxxxxx

---

Eclipse downloads: http://download.eclipse.org/eclipse/downloads/drops4/I20130429-2000/_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev