Community
Participate
Working Groups
Using the following versions from the current Buckminster repository at download.eclipse.org/tools/buckminster/headless-4.2 in the EPP build org.eclipse.buckminster.cmdline.product 1.5.0.v20120828-0000 org.eclipse.buckminster.core.headless.feature.feature.group 1.5.0.v20120910-1329 org.eclipse.buckminster.git.headless.feature.feature.group 1.5.0.v20120823-1443 org.eclipse.buckminster.pde.headless.feature.feature.group 1.5.0.v20121007-1625 And the target.* values defined as follows: <?xml version="1.0" encoding="UTF-8"?> <cq:componentQuery xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0" resourceMap="epp.rmap"> <cq:rootRequest name="org.eclipse.epp.allpackages.feature" componentType="eclipse.feature"/> <cq:property key="target.arch" value="*"/> <cq:property key="target.os" value="*"/> <cq:property key="target.ws" value="*"/> ... I got the following error [java] WARN: Target platform directory '/shared/technology/epp/epp_repo/kepler/epp.build/TP' does not exist and will be created [java] ERROR [0034] : No suitable provider for component org.eclipse.swt.gtk.hpux.ia64:osgi.bundle/[3.101.0.v4312,3.101.0.v4312](&(target.arch=ia64)(target.os=hpux)(target.ws=gtk)) was found in resourceMap file:/opt/public/technology/epp/epp_repo/kepler/git/features/org.eclipse.epp.allpackages.feature/epp.rmap [java] ERROR [0034] : No suitable provider for component org.eclipse.swt.gtk.hpux.ia64:osgi.bundle/[3.101.0.v4312,3.101.0.v4312](&(target.arch=ia64)(target.os=hpux)(target.ws=gtk)) was found in searchPath simrelease [java] ERROR [0034] : Rejecting provider p2({0}?importType=binary[file:///home/data/httpd/download.eclipse.org/releases/staging?importType=binary]): No component match was found [java] INFO: TAG-ID 0034 = Query for org.eclipse.platform:eclipse.feature, path: org.eclipse.platform:eclipse.feature$4.3.0.v20121020-052149-9JF7EHbzFxQtcMfEWz0z-14z-GBz0ANcyda2tJh9lm -> org.eclipse.rcp:eclipse.feature$4.3.0.v20121018-183810-7IAUA7BrHQiz-UnYiPwGsUdyYkUN -> org.eclipse.e4.rcp:eclipse.feature$1.1.0.v20121025-184438-8yFTeGTCGGduU2UmXjTMpH_GZg [java] I am not entirely sure who needs to change what... maybe it is a problem with the definition of target platforms in Buckminster (that needs to be changed because the Platform contribution has changed), or it is a problem with the Eclispe Platform contribution to Kepler. An example can be found here: https://hudson.eclipse.org/hudson/user/mknauer/my-views/view/EPP/job/kepler.epp-repository-build/18/console
I think the latter, "a problem with the Eclispe Platform contribution to Kepler". Sort of. We did switch to provide the 64 bit version for hpux.ia64 instead of the 32 bit version (hpux.ia64_32) as we had been providing. But, I did not update the "configs" in the simrel.b3aggr file. So, I have just now corrected that and assume a build will be finished in morning, which I'll promote to staging, and suggest you then try again. Hopefully its as simple as that.
Meant to reference the bug documenting the change: bug 391273.
Thanks, a new EPP build will start as soon as you update the staging area. Then we'll see if everything is fixed by then.
Well, I changed the "configs" and promoted new repo to staging, but seems to result in same/similar error: build.tp: [java] WARN: Target platform directory '/shared/technology/epp/epp_repo/kepler/epp.build/TP' does not exist and will be created [java] ERROR [0034] : No suitable provider for component org.eclipse.swt.gtk.hpux.ia64:osgi.bundle/[3.101.0.v4312,3.101.0.v4312](&(target.arch=ia64)(target.os=hpux)(target.ws=gtk)) was found in resourceMap file:/opt/public/technology/epp/epp_repo/kepler/git/features/org.eclipse.epp.allpackages.feature/epp.rmap [java] ERROR [0034] : No suitable provider for component org.eclipse.swt.gtk.hpux.ia64:osgi.bundle/[3.101.0.v4312,3.101.0.v4312](&(target.arch=ia64)(target.os=hpux)(target.ws=gtk)) was found in searchPath simrelease [java] ERROR [0034] : Rejecting provider p2({0}?importType=binary[file:///home/data/httpd/download.eclipse.org/releases/staging?importType=binary]): No component match was found [java] INFO: TAG-ID 0034 = Query for org.eclipse.platform:eclipse.feature, path: org.eclipse.platform:eclipse.feature$4.3.0.v20121020-052149-9JF7EHbzFxQtcMfEWz0z-14z-GBz0ANcyda2tJh9lm -> org.eclipse.rcp:eclipse.feature$4.3.0.v20121018-183810-7IAUA7BrHQiz-UnYiPwGsUdyYkUN -> org.eclipse.e4.rcp:eclipse.feature$1.1.0.v20121025-184438-8yFTeGTCGGduU2UmXjTMpH_GZg I will have to dig deeper to see if there are (other) errors on the platform/common repo side ... but ... I wonder if someone else, Thomas?, can read these errors more directly and understand what they are trying to tell us?
Are you sure that you were looking at the correct build? For some reason, the update of /releases/staging did not trigger a new kepler.epp-repository-build. My (manually triggered) build finished successful: https://hudson.eclipse.org/hudson/user/mknauer/my-views/view/Simultaneous%20Release/job/kepler.epp-repository-build/19/ From my point of view this issue seems to be resolved.
(In reply to comment #5) > Are you sure that you were looking at the correct build? For some reason, > the update of /releases/staging did not trigger a new > kepler.epp-repository-build. > > My (manually triggered) build finished successful: > > https://hudson.eclipse.org/hudson/user/mknauer/my-views/view/ > Simultaneous%20Release/job/kepler.epp-repository-build/19/ > > From my point of view this issue seems to be resolved. Oh, good to hear! No, I'm not sure I was looking at the right build ... there just seemed to be a new "red" one there, and looked at that. Didn't check times or anything.
Perfect. Then I am closing this one as fixed and moving it to cross-project because it affects the Simultaneous Release repository and it doesn't really belong to Buckminster. Thanks!
