Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340980

Summary:	Cannot start basic package with start.bat
Product:	z_Archived	Reporter:	Udo Walker <Udo.Walker>
Component:	RTP	Assignee:	Project Inbox <rtp.all-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	hmalphettes, holger.staudacher
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Udo Walker

2011-03-25 12:14:11 EDT

Build Identifier: rt-basic-incubation-0.1.0.v20110315-1547-M6

I called the batch script start.bat in the folder where I unpacked the zip archive. I got following error:


F:\rt-0.1.0>start.bat
the console arG  -console

Launching Equinox with: "C:\Programme\Java\jdk1.6.0_23\bin\java" -jar F:\RT-01~1.0\/=\  -Declipse.ignoreApp=true -Dosgi.noShutdown=true -Djetty.home=. -Dlogback.configurationFile=etc/logback.xml  -Dlogback.configurationFile=F:\RT-01~1.0\etc\logback.x
ml -install F:\RT-01~1.0\ -console

Unable to access jarfile F:\RT-01~1.0\/=\

I think the problem is that the file eclipse.ini contains not all required data. The eclipse.ini which was in the zip archive contains this:


-console
-vmargs
-Declipse.ignoreApp=true
-Dosgi.noShutdown=true
-Djetty.home=.
-Dlogback.configurationFile=etc/logback.xml


I think the launcher is missing.



Reproducible: Always

Comment 1 Hugues Malphettes

2011-03-28 03:15:27 EDT

Thanks for the report Udo.
Yes indeed I had used and tested this bat file against a slightly different build where the launcher is specified.

Let me grab a windows machine and add support for this situation.

Comment 2 Udo Walker

2011-03-29 05:37:09 EDT

2 things I found out:

1. Add these 2 lines to the beginning of the file eclipse.ini:

-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110124-0830.jar


2. In the file configuration/org.eclipse.equinox.simpleconfigurator/bundles.info remove the entry


org.eclipse.equinox.launcher.gtk.linux.x86,1.1.100.v20101018,plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.100.v20101018/,4,false


and add the one for Windows. 

In the plugins directory there are only Linux specific bundles. Probably you have to add the Delta Pack to your target platform and rebuild the product also for the platform Windows.

Comment 3 Holger Staudacher

2011-03-29 05:54:46 EDT

Hugues, is it possible to make the launch scripts find the launcher dynamically?

Comment 4 Hugues Malphettes

2011-03-29 06:23:22 EDT

(In reply to comment #3)
> Hugues, is it possible to make the launch scripts find the launcher
> dynamically?
Yes. Absolutely.


(In reply to comment #2)
> 2 things I found out:
> 
Udo, we delete the native launchers on purpose: we don't need the SWT bindings and or any of those things for our server-side products.
We prefer the batch and bash scripts that server-side developers and IT admins are familiar with.

At the moment, we have not found a way to package the batch and bash script as a true "launcher" and we have not found how to prevent p2-director from installing a native launcher. We are discussing with the p2-devs about this.

Thanks for observing that our build script that removes the native launchers should also remove the OS native fragment mentioned in the bundles.info file.

I am looking at what we did in the shell version to cope with the case where p2-director did not generate the -startup line.

Comment 5 Hugues Malphettes

2011-03-29 06:53:43 EDT

Fixed with this commit for the batch file:
http://git.eclipse.org/c/rtp/org.eclipse.rtp.git/commit/?id=ca59612302799d7a108a362809a2dc90200d3c10

Working on removing the fragment launcher from the bundles.info although it really does not seem to have an impact.