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

Bug 464690

Summary:	Unable to launch applet
Product:	[Eclipse Project] JDT	Reporter:	Mat Jaggard <eclipse>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.5
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Mat Jaggard

2015-04-15 09:28:59 EDT

!ENTRY org.eclipse.core.jobs 4 2 2015-04-15 14:22:39.527
!MESSAGE An internal error occurred during: "Launching jiApplet".
!STACK 0
java.lang.NullPointerException
	at java.io.FileOutputStream.<init>(FileOutputStream.java:203)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
	at org.eclipse.jdt.internal.launching.JavaAppletLaunchConfigurationDelegate.buildHTMLFile(JavaAppletLaunchConfigurationDelegate.java:102)
	at org.eclipse.jdt.internal.launching.JavaAppletLaunchConfigurationDelegate.getProgramArguments(JavaAppletLaunchConfigurationDelegate.java:326)
	at org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:64)
	at org.eclipse.jdt.internal.launching.JavaAppletLaunchConfigurationDelegate.launch(JavaAppletLaunchConfigurationDelegate.java:63)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)



-- Configuration Details --
Product: Eclipse 4.5.0.20150326-0704 (org.eclipse.epp.package.jee.product)
Installed Features:
 org.eclipse.jdt 3.11.0.v20150320-0800

Comment 1 Eclipse Genie

2019-08-14 07:37:19 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.