Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Headless build does not produce launcher
Headless build does not produce launcher [message #720814] Wed, 31 August 2011 09:38 Go to next message
Robert Gruendler is currently offline Robert GruendlerFriend
Messages: 66
Registered: June 2011
Member
Hi,

i'm trying to follow the tutorial http://www.ralfebert.de/blog/eclipsercp/rcp_builds/ to create automated builds using buckminster and hudson. However, i'm already stuck at the manual installation of the product from a generated p2 repository using director.

When i run director it seems everything is properly created, except that the binary launcher (eclipse.exe on win32) is missing.

Director finishes without any errors and generates the following artifacts:

* configuration (folder)
* p2 (folder)
* plugins (folder)
* artifacts.xml
* eclipse.ini

In my product definition i have set a launcher name, launcher icons and selected "the product includes native launcher artifacts".

Has anyone a hint what can cause director to not create the launcher?

Report message to a moderator

Re: Headless build does not produce launcher [message #720828 is a reply to message #720814] Wed, 31 August 2011 10:04 Go to previous messageGo to next message
Achim is currently offline Achim Friend
Messages: 7
Registered: August 2011
Junior Member
Hi,

I see the same problem in my environment. I sometimes notice that the launcher is not generated when a certain dependency is added.
If you know a solution for this please let me know

Regards

Report message to a moderator

Re: Headless build does not produce launcher [message #720830 is a reply to message #720828] Wed, 31 August 2011 10:13 Go to previous messageGo to next message
Robert Gruendler is currently offline Robert GruendlerFriend
Messages: 66
Registered: June 2011
Member
it seems buckminster/director doesn't take the product definition into account. when i export the product manually from within the IDE, the .ini file is called the same name like the launcher name specified in the "Launching" tab of the product definition.

However, when i use the headless installation, the file is called "eclipse.ini" instead of "my_launcher_name.ini".

Report message to a moderator

Re: Headless build does not produce launcher [message #720839 is a reply to message #720830] Wed, 31 August 2011 10:32 Go to previous messageGo to next message
Robert Gruendler is currently offline Robert GruendlerFriend
Messages: 66
Registered: June 2011
Member
according to this thread http://www.eclipse.org/forums/index.php/mv/tree/175057/#page_top the defining feature needs to include org.eclipse.equinox.executable to get the launcher. this package does not exist in indigo as it seems (at least i can't find it).

Report message to a moderator

Re: Headless build does not produce launcher [message #720842 is a reply to message #720814] Wed, 31 August 2011 10:20 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 2011-08-31 11:38, sobert wrote:
> Hi,
>
> i'm trying to follow the tutorial http://www.ralfebert.de/blog/eclipsercp/rcp_builds/ to create automated builds using
> buckminster and hudson. However, i'm already stuck at the manual installation of the product from a generated p2
> repository using director.
>
> When i run director it seems everything is properly created, except that the binary launcher (eclipse.exe on win32) is
> missing.
>
> Director finishes without any errors and generates the following artifacts:
>
> * configuration (folder)
> * p2 (folder)
> * plugins (folder)
> * artifacts.xml * eclipse.ini
>
> In my product definition i have set a launcher name, launcher icons and selected "the product includes native launcher
> artifacts".
>
> Has anyone a hint what can cause director to not create the launcher?
>

The most likely reason is that you don't have org.eclipse.equinox.executable feature present in your target platform.
The publisher needs that feature to find the launchers for all platforms. The best way to ensure that the launcher is
present is probably to add it as a dependency in a buckminster.cspec or buckminster.cspex file. Do not include it as a
feature or product dependency since this feature is not something that should be installed.

- thomas

Report message to a moderator

Re: Headless build does not produce launcher [message #720858 is a reply to message #720842] Wed, 31 August 2011 11:34 Go to previous messageGo to next message
Robert Gruendler is currently offline Robert GruendlerFriend
Messages: 66
Registered: June 2011
Member
thanks for the tip, though i have no idea how to add the feature to the cspex file (google didn't give me an answer either).

Here's my current cspex file:

<?xml version="1.0" encoding="UTF-8"?>
<cspecExtension xmlns:com="http://www.eclipse.org/buckminster/Common-1.0"
	xmlns="http://www.eclipse.org/buckminster/CSpec-1.0">
	<actions>
		<public name="create.product" actor="ant">
			<actorProperties>
				<property key="buildFile" value="build/product.ant" />
				<property key="targets" value="create.product" />
			</actorProperties>
			<properties>
				<property key="profile" value="MailProfile" />
				<property key="iu" value="com.example.mail.product" />
			</properties>
			<prerequisites alias="repository">
				<attribute name="site.p2" />
			</prerequisites>
			<products alias="destination" base="${buckminster.output}">
				<path path="mail.${target.ws}.${target.os}.${target.arch}/" />
			</products>
		</public>
		<public name="create.product.zip" actor="ant">
			<actorProperties>
				<property key="buildFileId" value="buckminster.pdetasks" />
				<property key="targets" value="create.zip" />
			</actorProperties>
			<prerequisites alias="action.requirements">
				<attribute name="create.product" />
			</prerequisites>
			<products alias="action.output" base="${buckminster.output}">
				<path path="mail.${target.ws}.${target.os}.${target.arch}.zip" />
			</products>
		</public>
	</actions>
</cspecExtension>


Any idea how to add the feature there? When browsing the features in the target definition for example, i cant't find the org.eclipse.equinox.executable feature enywhere. there isn't even an org.eclipse.equinox.XY feature, they all start with org.eclipse.equinox.p2.* now. (eclipse 3.7)

Report message to a moderator

Re: Headless build does not produce launcher [message #720859 is a reply to message #720839] Wed, 31 August 2011 11:29 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 2011-08-31 12:32, sobert wrote:
> according to this thread http://www.eclipse.org/forums/index.php/mv/tree/175057/#page_top the defining feature needs to
> include org.eclipse.equinox.executable to get the launcher. this package does not exist in indigo as it seems (at least
> i can't find it).

You will find it in the platform repository: http://download.eclipse.org/eclipse/updates/3.7

Again, I would advice against including the executable feature in another feature.

- thomas

Report message to a moderator

Re: Headless build does not produce launcher [message #720900 is a reply to message #720859] Wed, 31 August 2011 13:05 Go to previous messageGo to next message
Robert Gruendler is currently offline Robert GruendlerFriend
Messages: 66
Registered: June 2011
Member
Thomas Hallgren wrote on Wed, 31 August 2011 07:29
On 2011-08-31 12:32, sobert wrote:

Again, I would advice against including the executable feature in another feature.


ok, but there's virtually no documentation on how to add this to the cspex file.

this is really frustrating. imho, these automated builds are way too complex to setup.

Report message to a moderator

Re: Headless build does not produce launcher [message #721333 is a reply to message #720859] Thu, 01 September 2011 13:46 Go to previous messageGo to next message
Stephan is currently offline Stephan Friend
Messages: 36
Registered: July 2009
Member
Hi Thomas

> Again, I would advice against including the executable feature in another feature.

So this means the chapter "Building RCP Products > Structure" in the BuckyBook is not up-to-date anymore (which shows an inclusion of o.e.e.excutable)?

Thanks, Stephan

Report message to a moderator

Re: Headless build does not produce launcher [message #721350 is a reply to message #721333] Thu, 01 September 2011 14:24 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 2011-09-01 15:46, Stephan wrote:
> Hi Thomas
>
>> Again, I would advice against including the executable feature in another feature.
>
> So this means the chapter "Building RCP Products > Structure" in the BuckyBook is not up-to-date anymore (which shows an
> inclusion of o.e.e.excutable)?
>
> Thanks, Stephan

Yes, please file a bugzilla for this.

Thanks,
- thomas

Report message to a moderator

Re: Headless build does not produce launcher [message #721439 is a reply to message #721350] Thu, 01 September 2011 18:57 Go to previous messageGo to next message
Stephan is currently offline Stephan Friend
Messages: 36
Registered: July 2009
Member
Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=356510

Regards, Stephan

Report message to a moderator

Re: Headless build does not produce launcher [message #721515 is a reply to message #721439] Fri, 02 September 2011 00:37 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik LindbergFriend
Messages: 2509
Registered: July 2009
Senior Member
Thanks
- henrik
On 9/1/11 8:57 PM, Stephan wrote:
> Please see https://bugs.eclipse.org/bugs/show_bug.cgi?id=356510
>
> Regards, Stephan

Report message to a moderator

Re: Headless build does not produce launcher [message #721933 is a reply to message #721515] Sat, 03 September 2011 17:03 Go to previous messageGo to next message
Stephan is currently offline Stephan Friend
Messages: 36
Registered: July 2009
Member
Hi Thomas

I just made a quick test of this dependency configuration. In a working build I
- removed o.e.e.executable from the list of included features
- added a buckminster.cspex with a dependency on o.e.e.executable

When run from the IDE, I still can build the site but creating the product with the director fails (org.eclipse.core.runtime.CoreException: C:\projects\cctvnet\wstrunk37\com.diligentit.cctvnet.server.config.build\build\product.ant:22: Java returned: 13).
- How can I get a debug log from the p2-director to find out whats wrong?
- What else must be changed to make this working?

Regards, Stephan

Report message to a moderator

Re: Headless build does not produce launcher [message #722236 is a reply to message #721933] Mon, 05 September 2011 06:27 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
On 2011-09-03 19:03, Stephan wrote:
> Hi Thomas
>
> I just made a quick test of this dependency configuration. In a working build I
> - removed o.e.e.executable from the list of included features
> - added a buckminster.cspex with a dependency on o.e.e.executable
>
> When run from the IDE, I still can build the site but creating the product with the director fails
> (org.eclipse.core.runtime.CoreException:
> C:\projects\cctvnet\wstrunk37\com.diligentit.cctvnet.server.config.build\build\product.ant:22: Java returned: 13). - How
> can I get a debug log from the p2-director to find out whats wrong?
> - What else must be changed to make this working?
>
> Regards, Stephan

The output usually ends up in the directors <director installation>/configuration directory in a file with many digits
ending with .log.

- thomas

Report message to a moderator

Re: Headless build does not produce launcher [message #722403 is a reply to message #722236] Mon, 05 September 2011 16:47 Go to previous messageGo to next message
Stephan is currently offline Stephan Friend
Messages: 36
Registered: July 2009
Member
Thank you, now I found the log and it contains:

Command-line arguments: -application org.eclipse.equinox.p2.director -artifactRepository file:/C:/01_Build/buckybuild/CfgServer/com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature/site.p2/ -metadataRepository file:/C:/01_Build/buckybuild/CfgServer/com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature/site.p2/ -destination C:\01_Build\buckybuild\CfgServer\com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature\CfgServer.win32.win32.x86 -bundlepool C:\01_Build\buckybuild\CfgServer\com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature\CfgServer.win32.win32.x86 -profile CCTVnetCfgServerProfile -profileProperties org.eclipse.update.install.features=true -installIU com.diligentit.cctvnet.server.config.product -p2.os win32 -p2.ws win32 -p2.arch x86 -consoleLog -roaming

!ENTRY org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.750
!MESSAGE Cannot complete the install because one or more required items could not be found.
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.750
!MESSAGE Software being installed: CfgServer 5.6.0 (com.diligentit.cctvnet.server.config.product 5.6.0)
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.750
!MESSAGE Missing requirement for filter properties ~= $0: com.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 5.6.0 requires 'org.eclipse.equinox.launcher.win32.win32.x86 0.0.0' but it could not be found
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.859
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.859
!MESSAGE From: CfgServer 5.6.0 (com.diligentit.cctvnet.server.config.product 5.6.0)
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.859
!MESSAGE To: toolingcom.diligentit.cctvnet.server.config.product.application [5.6.0]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.859
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.968
!MESSAGE From: toolingcom.diligentit.cctvnet.server.config.product.application 5.6.0
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.968
!MESSAGE To: toolingcom.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 [5.6.0]
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.968
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.968
!MESSAGE From: toolingcom.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 5.6.0
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:20.078
!MESSAGE To: com.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 [5.6.0]

The prefix "tooling" looks strange and I don't know where this is coming from but I don't know if this causes the problem...

BTW, if I have several nested features, where should I put the buckminster.cspex with the dependency (at the moment I have added it to every feature)?

Regards, Stephan

Report message to a moderator

Re: Headless build does not produce launcher [message #722435 is a reply to message #722403] Mon, 05 September 2011 18:47 Go to previous message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3240
Registered: July 2009
Senior Member
I'm fairly certain that the problem is this:

!MESSAGE Missing requirement for filter properties ~= $0:
com.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 5.6.0 requires
'org.eclipse.equinox.launcher.win32.win32.x86 0.0.0' but it could not be found

which would indicate that either you don't have the launcher in your target platform or you didn't use '*' for the
target.os, target.ws, and target.arch when you resolved or performed site.p2.

- thomas

On 2011-09-05 18:47, Stephan wrote:
> Thank you, now I found the log and it contains:
>
> Command-line arguments: -application org.eclipse.equinox.p2.director -artifactRepository
> file:/C:/01_Build/buckybuild/CfgServer/com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature/site.p2/
> -metadataRepository
> file:/C:/01_Build/buckybuild/CfgServer/com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature/site.p2/
> -destination
> C:\01_Build\buckybuild\CfgServer\com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature\CfgServer.win32.win32.x86
> -bundlepool
> C:\01_Build\buckybuild\CfgServer\com.diligentit.cctvnet.server.config.build_5.6.0-eclipse.feature\CfgServer.win32.win32.x86
> -profile CCTVnetCfgServerProfile -profileProperties org.eclipse.update.install.features=true -installIU
> com.diligentit.cctvnet.server.config.product -p2.os win32 -p2.ws win32 -p2.arch x86 -consoleLog -roaming
>
> !ENTRY org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.750
> !MESSAGE Cannot complete the install because one or more required items could not be found.
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.750
> !MESSAGE Software being installed: CfgServer 5.6.0 (com.diligentit.cctvnet.server.config.product 5.6.0)
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.750
> !MESSAGE Missing requirement for filter properties ~= $0:
> com.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 5.6.0 requires
> 'org.eclipse.equinox.launcher.win32.win32.x86 0.0.0' but it could not be found
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.859
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.859
> !MESSAGE From: CfgServer 5.6.0 (com.diligentit.cctvnet.server.config.product 5.6.0)
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.859
> !MESSAGE To: toolingcom.diligentit.cctvnet.server.config.product.application [5.6.0]
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.859
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.968
> !MESSAGE From: toolingcom.diligentit.cctvnet.server.config.product.application 5.6.0
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.968
> !MESSAGE To: toolingcom.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 [5.6.0]
> !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2011-09-05 18:31:19.968
> !MESSAGE Cannot satisfy dependency:
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:19.968
> !MESSAGE From: toolingcom.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 5.6.0
> !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2011-09-05 18:31:20.078
> !MESSAGE To: com.diligentit.cctvnet.server.config.product.executable.win32.win32.x86 [5.6.0]
>
> The prefix "tooling" looks strange and I don't know where this is coming from but I don't know if this causes the
> problem...
>
> BTW, if I have several nested features, where should I put the buckminster.cspex with the dependency (at the moment I
> have added it to every feature)?
>
> Regards, Stephan
>
>

Report message to a moderator

Previous Topic:Replace launcher with eclipsec.exe for Windows builds
Next Topic:Re: Buckminster build in hudson with precreated target platform
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Wed Feb 05 12:02:45 GMT 2025

Powered by FUDForum. Page generated in 0.05503 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly