| Windows->Linux migration [message #658615] |
Wed, 09 March 2011 04:31  |
Eclipse User |
|
|
|
Hello everybody,
I am pretty new to Buckminster. Last week I set up all required configurations to move our build form manually building using PDE to automated build with Buckminster on jenkins. So far everything was quite straight forward.
We build an update site containing several plugin/features but no product or RCP application (yet). I expected no serious problems moving the working setup from windows to linux-maschine which is dedicated to become our build-server. Some path-issues needed to be adjusted but after that buckminster was started without errors. importtargetdefinition shows no error and a new target is available in lsttargets after that.
importing CSPEC fails saying:
No suitable provider for component org.eclipse.core.runtime:osgi.bundle was found in resourceMap
Can anyone help me with that? I think for some reason buckminster does not resolve plugins from the target platform.
I currently materialize all required projects from SVN to the workspace using jenkins and reference them in the rmpa locally.
The target platform definitoin is completely chekced out from subversion and present in the workspace. I tried different .target-files referencing the directory by absolute path or even using online sites form eclipse.org, but none of them worked to resolve the required bundles.
Did I miss a step? What is the difference regarding handling of target platform in windows and linux?
My cspec looks as follows:
<?xml version="1.0" encoding="UTF-8"?>
<cq:componentQuery xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0" resourceMap="site.rmap">
<cq:rootRequest name="com.example.site" componentType="eclipse.feature"/>
</cq:componentQuery>
My rmap looks as follows:
<?xml version="1.0" encoding="UTF-8"?>
<rmap
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.eclipse.org/buckminster/RMap-1.0"
xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0"
xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0"
xmlns:pp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0">
<searchPath name="resources">
<provider readerType="local" componentTypes="osgi.bundle,eclipse.feature"
mutable="true" source="true">
<uri format="file:///{0}/{1}/">
<bc:propertyRef key="workspace.root" />
<bc:propertyRef key="buckminster.component" />
</uri>
</provider>
</searchPath>
<locator searchPathRef="resources"/>
</rmap>
Thanks,
Alexander
|
|
|
|
|
| Re: Windows->Linux migration [message #658713 is a reply to message #658653] |
Wed, 09 March 2011 10:25  |
| Eclipse User |
|
|
|
The way the RMAP is set up, the resolver currently assumes that you find everything, including all Eclipse bundles,
using a local reader that looks at your workspace root.
Normally, Buckminster will consult the target platform before it consults the RMAP so either your target platform hasn't
been setup correctly, or your CQUERY contains an advisor node to explicitly avoid resolving against the target platform.
- thomas
On 2011-03-09 12:52, Alexander May wrote:
> Hi Thomas,
>
> thanks for your advice. Unfortunately it did not help.
>
> I tried several differentnotations in the URI of the resolver but nothing changed in the result.
>
> The problem occurs only with the bundles I expect to be resolved from the target platform (like o.e.*). My own bundles
> (with sources located in my workspace) are resolved properly.
>
> I did some further investigation and found some other lines in the output that seem stragen to mee:
>
>
> org.eclipse.core.runtime:osgi.bundle: Using resolver Local resolver
> org.eclipse.core.runtime:osgi.bundle: Trying provider local(materialized)
> No materialization found for org.eclipse.core.runtime:osgi.bundle
> org.eclipse.core.runtime:osgi.bundle: Trying provider local(workspace)
> No open workspace project found that corresponds to org.eclipse.core.runtime:osgi.bundle
> org.eclipse.core.runtime:osgi.bundle: Trying provider local(target)
> org.eclipse.core.runtime:osgi.bundle: Rejecting provider eclipse.platform(plugin/${buckminster.component}): No component
> match was found
>
>
> The bundle o.e.c.r is not located in my workspace therfore i think it is correct that the first two providers do not
> find a match. I expected the third provider to find a match. After that my rmap is used, but this does only resolve to
> projects located in directories below the workspace.
>
> Any further suggestions?
> What I still don't understand completely is the handling of the target platform. Why does the provider local(target) not
> resolve the eclipse bundles? Can I check the content of the target platform or see wether errors occured during
> importing of the target platform?
>
> Thanks,
> Alexander
|
|
|
|
|
|
|
|
| Re: Windows->Linux migration [message #659717 is a reply to message #658615] |
Tue, 15 March 2011 06:31 |
| Eclipse User |
|
|
|
Thank you,
I finally got a working build. The key was to set up the target platform materialization as a sepperate build which materializes from p2-sites to a local directory.
For the directory I configured an according target definition which I use when testing within the UI and when building headless only targetPlatformPath is used.
Thanks a lot, Buckminster is an awfully usefull tool, once it is set up and integrated in the procedures.
Alexander
|
|
|
Powered by
FUDForum. Page generated in 0.15403 seconds
Home