[platform-releng-dev] I-build scheduled for 4 PM (1600) Eastern

[David M Williams <david_williams@xxxxxxxxxx>]

The SWT changes have been reverted, for
now, so we'll see how a new I-build goes. If it goes well, it should be
finished about 7 PM (Eastern) ... test results by midnight or so. 

Thanks 




From:      
 David M Williams/Raleigh/IBM@IBMUS
To:      
 "Eclipse platform
release engineering list." <platform-releng-dev@xxxxxxxxxxx>,

Date:      
 07/16/2013 05:09 PM
Subject:    
   Re: [platform-releng-dev]
4.4.0 N-Build:        N20130715-2000  
     -        BUILD
       FAILED
Sent by:    
   platform-releng-dev-bounces@xxxxxxxxxxx

---

There has been quite a few of us looking
at this issue today, but nothing obvious has been found. I have opened
following bug to track. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=413116

On the surface, it appears the "root cause" may be that swt change
to pre-req 1.5, whereas jface.databinding and jface.text still only require
Foundation classes. 

This may be a limitation we "just have to live with" with new
Tycho/Maven build? That is, an "easy fix" would appear to be
that jface.databinding and jface.text also move up to 1.5. Is this objectionable?
Or does SWT need to move "back down" to Foundation classes? 

Comments/suggestions in bug 413116 would be most welcome. 

Thanks, 




From:        David
M Williams/Raleigh/IBM@IBMUS 
To:        "Eclipse
platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>,
Date:        07/16/2013
01:10 PM 
Subject:        Re:
[platform-releng-dev] 4.4.0 N-Build: N20130715-2000      
 -        BUILD        FAILED
Sent by:        platform-releng-dev-bounces@xxxxxxxxxxx

---

I have noticed, in my PDE Workbench, that even there, in the fragment (say
for org.eclipse.swt.gtk.linux.x86_64, which is the architecture I'm running
on) PDE says "exports not found" for that fragment. Is that normal?
Or could binary have been "built wrong"?  (I normally have
those fragments "closed", but "opened" this one just
to take a look). 

Anyway, while others are trying to narrow down the cause of the failure,
I'm going to try a test M build .... just to make sure the issue is with
Luna stream only. 

Thanks, 




From:        Thomas
Watson/Austin/IBM@IBMUS 
To:        "Eclipse
platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>,
Date:        07/16/2013
09:05 AM 
Subject:        Re:
[platform-releng-dev] 4.4.0 N-Build: N20130715-2000 -      
 BUILD        FAILED 
Sent by:        platform-releng-dev-bounces@xxxxxxxxxxx

---

Perhaps it is related to the recent upgrade to Java 5 for SWT since that
happened since the last successful N-Build.  But I don't really see
anything wrong with the related commits:

http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=5fba4321d581bbd674b16968240b2ba2ff039c2c
http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=eb4a566fe3bbefedab594865c6cfba14ed29c7d7

If it turns out to be related to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=411672
then it appears CBI nay not be paying attention to the Eclipse-ExtensibleAPI:
true header like the PDE build used to.  This header was a kind of
hack that told PDE to allow fragments to be placed on the classpath of
bundles that import/require the host so they can provide additional API
which is not declared by the host.

Tom

David
M Williams---07/15/2013 08:36:55 PM---I think the "root" of this
build failure are changes made for  https://bugs.eclipse.org/bugs/show_bu

From: David M Williams/Raleigh/IBM@IBMUS
To: "Eclipse platform release
engineering list." <platform-releng-dev@xxxxxxxxxxx>, 
Date: 07/15/2013 08:36 PM
Subject: Re: [platform-releng-dev]
4.4.0 N-Build: N20130715-2000 - BUILD FAILED
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

---

I think the "root" of this build failure are changes made for

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

Not sure why they haven't shown up earlier ... perhaps something related
to "comparator"? 

But, on the surface, there's the appearance that SWT no longer "exports"
its API .... though it does in its 
fragments. Perhaps needs to do in both, to get the build to work? 

Other suggestions/analysis welcome. 




From:        e4Builder@xxxxxxxxxxx
To:        platform-releng-dev@xxxxxxxxxxx,
Date:        07/15/2013
09:30 PM 
Subject:        [platform-releng-dev]
4.4.0 N-Build: N20130715-2000 - BUILD FAILED 
Sent by:        platform-releng-dev-bounces@xxxxxxxxxxx

---

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