Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[buckminster-dev] Re: mspec problems with released buckminster 
Hi Johannes,
I had the exact same problem, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=282810. Thomas fixed this in revision 10451, so a self-built version of Buckminster should work.
An unrelated question: Currently the Hudson Buckminster builder does not show up in multi-configuration projects. Is this just a configuration issue or are there additional requirements for a builder to support that? 

Best regards,
Carsten

On 15.07.2009 13:54, Johannes Utzig wrote:

Hi,
as discussed in http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg00845.html I am working on creating a tutorial on how to build eclipse RCPs with buckminster and how to integrate that into a CI system (hudson in this case). The necessary modifications to the hudson plugin are in place and deployed, but I'm having issues with materializing the target platform. 
As suggested by Thomas I start by resolving a target platform with an mspec.
To do so I essentially use this mspec:
http://build.eclipse.org/tools/buckminster/hudson/tp.mspec
The only thing I had to modify was the tp.rmap because the URL wasn't working anymore. 
My modified rmap points to the galileo release:
<?xml version="1.0" encoding="UTF-8"?>
<rmap xmlns="http://www.eclipse.org/buckminster/RMap-1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
	xmlns:mp="http://www.eclipse.org/buckminster/MavenProvider-1.0";
	xmlns:pmp="http://www.eclipse.org/buckminster/PDEMapProvider-1.0";
	xmlns:bc="http://www.eclipse.org/buckminster/Common-1.0";>

	<searchPath name="org.eclipse.platform">
<provider readerType="eclipse.import" componentTypes="osgi.bundle,eclipse.feature" mutable="false" source="false"> <uri format="http://download.eclipse.org/releases/galileo/?importType=binary"/> 
		</provider>
	</searchPath>
	<locator searchPathRef="org.eclipse.platform"/>
</rmap>
Apart from that, mspec, cspec and rmap are identical to the resources in http://build.eclipse.org/tools/buckminster/hudson/ 

To start with the target platform I invoke buckminster like that:
java -DtargetPlatformPath=/where/target/platform/should/be/materialized
-jar plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
-application org.eclipse.buckminster.cmdline.headless
-data /data/directory/
--loglevel info
-S /commands.txt

The command to be executed in this case is simply
import http://url/to/tp.mspec
The path /where/target/platform/should/be/materialized does not exist yet and should be populated with the freshly downloaded platform. This works great with the RC4, but I get a bunch of error messages when trying the released version. I verified this on two machines and it's the same thing in both cases: RC4 works, released version does not. 
The error messages are:
ERROR   [0001] : An error occurred while collecting items to be installed
ERROR [0001] : session context was:(profile=1247658332601-0.23645752893850414, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=). ERROR [0001] : No repository found containing: osgi.bundle,org.eclipse.equinox.common,3.5.0.v20090520-1800 ERROR [0001] : No repository found containing: osgi.bundle,org.eclipse.equinox.registry,3.4.100.v20090520-1800 ERROR [0001] : No repository found containing: osgi.bundle,org.eclipse.core.runtime.compatibility.registry,3.2.200.v20090429-1800
and many many more (A few hundred of those messages each with different bundles. I'll attach the full trace as a file if requested). The funny thing is though, resolving the cquery instead of importing the mspec works just fine so those components obviously are in place and resolvable.
Any help here would be appreciated, because I can't really write a tutorial that only works with a specific RC... 

Best regards and thanks for the support,
Johannes

Back to the top