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

Bug 342914

Summary:	DBCS3.7 laucher.openFile does not work in Windows 7
Product:	[Eclipse Project] Equinox	Reporter:	Kentaroh Noji <kennoji>
Component:	Launcher	Assignee:	Project Inbox <equinox.launcher-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	camle, fmisiak, kitlo, pwebster, tjwatson
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Kentaroh Noji

2011-04-14 23:41:28 EDT

Build Identifier: I20110407-2200

Though this bug was found and reported during DBCS enablement test, note that
this may be not a DBCS problem.
OS: Windows 7 SP1 Japanese
JDK: java full version "JRE 1.6.0 IBM Windows AMD 64 build pwa6460sr9fp1-20110208_03 (SR9 FP1)" 

Fail to run eclipse in Windows 7 if --laucher.openFile is used. I confirmed that --laucher.openFile option successfully works in Windows XP SP3 Japanese edition.  

Reproducible: Always

Steps to Reproduce:
1. Start eclipse with -laucher.openFile, e.g., eclipse.exe --launcher.openFile C:\eclipse\artifacts.xml

Comment 1 Thomas Watson

2011-04-15 11:01:44 EDT

This works for me on 
java full version "JRE 1.6.0 IBM Windows 32 build pwi3260sr9ifx-20110211_02 (SR9)"

So it could be a 64-bit thing, or I am just lucky.

Do you get any failure message or it simply fails silently?

Comment 2 Kentaroh Noji

2011-04-18 03:23:47 EDT

(In reply to comment #1)
> Do you get any failure message or it simply fails silently?

I checked some messages in configuration directory, but I did not get any error messages. It fails silently. 

> I confirmed that --laucher.openFile option successfully worked in Windows XP SP3 Japanese edition.  

Just in case, I use "JRE 1.6.0 IBM Windows 32 build pwi3260sr9fp1-20110208_03 (SR9 FP1)" for my Windows XP.

Comment 3 Eclipse Genie

2019-09-29 15:18:51 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Thomas Watson

2019-09-30 08:45:49 EDT

Marking as worksforme.  Reopen if still an issue.