This might get complicated. (Or else it is something simple over my head). 


You get this for your own builds? Or aggregation builds? 

We did add a sparcv9 filesystem fragment in the platform but as I tried to 
look into this saw some mysterious things and not sure if I did things 
wrong, or if aggregator needs a change ... or, what. Hence, let's move the 
conversation to bug 396653 and we'll pull in all the experts needed. 
(Buckminster, Aggregator, Equinox/OSGi). 

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

Thanks, 





From:   "Wenz, Michael" <[email protected]>
To:     Cross project issues <[email protected]>, 
Date:   12/14/2012 04:20 PM
Subject:        Re: [cross-project-issues-dev] Notice that the Eclipse 
Platform Project will be a little late with our official M4 build for 
Kepler
Sent by:        [email protected]



Hi,
 
Not sure if that is a platform issue, but I’m currently stuck on this…
 
I’m trying to get an early M4 version of Graphiti and updated our GEF and 
EMF Transaction dependencies to their latest integration builds to get 
their correct ICU4J usages. But I get this strange build error when I also 
update to the M4 platform integration update site ([1]) for the build 
David referred to below:
 
ERROR   [0053] : No suitable provider for component 
org.eclipse.core.filesystem.solaris.sparcv9:osgi.bundle(&(target.arch=sparcv9)(target.os=solaris))
 
was found in resourceMap 
file:/opt/users/hudsonbuild/.hudson/jobs/gmp-graphiti-nightly/workspace/org.eclipse.gmp/org.eclipse.gmp.graphiti/releng/org.eclipse.graphiti.releng/build.rmap
  ERROR   [0053] : No suitable provider for component 
org.eclipse.core.filesystem.solaris.sparcv9:osgi.bundle(&(target.arch=sparcv9)(target.os=solaris))
 
was found in searchPath binaries.platform
    ERROR   [0053] : Rejecting provider 
p2({0}/eclipse/updates/4.3-I-builds[file:/home/data/httpd/download.eclipse.org/eclipse/updates/4.3-I-builds]):
 
No component match was found
 
Full build log at [1]
 
I have no clue where the dependency to that sparcv9 plugin is coming from. 
With an the milestones update site [3] I get a green build.
 
Does anyone have a clue how to fix this? Do I miss anything?
 
Michael
 
[1] http://download.eclipse.org/eclipse/updates/4.3-I-builds (Which is a 
composite containing an I20121214-0730 repo)
[2] 
https://hudson.eclipse.org/hudson/me/my-views/view/Graphiti/job/gmp-graphiti-nightly/1223/console
[3] http://download.eclipse.org/eclipse/updates/4.3milestones
 
 
From: [email protected] [
mailto:[email protected]] On Behalf Of David M 
Williams
Sent: Freitag, 14. Dezember 2012 20:13
To: Cross project issues
Subject: [cross-project-issues-dev] Notice that the Eclipse Platform 
Project will be a little late with our official M4 build for Kepler
 
It is very likely our M4 build will be 
http://download.eclipse.org/eclipse/downloads/drops4/I20121214-0730/ 

But ... we've had to go through several respins to get things right ... 
mostly "repo correctness" issues (not that much of substance has changed 
in past few days). 

So, our unit tests won't be complete until late tonight, hence we won't 
declare an official M4 until those are done and confirmed ok. That will 
either be late tonight or Saturday, depending on exactly when they get 
done and teams finish their sign-offs (bug 396469). 

I will go ahead and update our b3aggrcon file with our "presumed M4" 
build, so we can get an idea of how many other projects I need to disable 
:)  As teams make your own contributions Monday through Wednesday [1], 
feel free to re-enable, when you are ready. There might be so many I'll 
decide to leave it broken for a while ... just for example, I know DTP and 
GEF only recently updated their ICU4J, so if I see I'd have to disable 
projects at that level, I'd have to disable just about everyone! 

Thanks for your patience and contributions ... it will be an exciting 
week! 


[1] In case anyone needs a reminder, M4 is due 12/21, which means 
contributions done by Wednesday next week, Thursday EPP day, and Friday 
make available. This is the time of year we switch to a "1 week window" 
from +0 to done. _______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to