Community
Participate
Working Groups
I20100720-0800 Sometimes a FileNotFoundException is generated when starting the infocenter with a clean workspace. java.io.FileNotFoundException: C:\cs\workspaces\runtime-New_configuration81\.metadata\.connection (The system cannot find the path specified.) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:205) at java.io.FileOutputStream.<init>(FileOutputStream.java:157) at org.eclipse.help.internal.base.HelpApplication.writeHostAndPort(HelpApplication.java:135) at org.eclipse.help.internal.base.HelpApplication.start(HelpApplication.java:61) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
Created attachment 175514 [details] Patch The old code was was using this expression to find the metadata location: new File(Platform.getLocation().toFile(), ".metadata/") which does not look right, it should be using Plugin.getStateLocation() instead.
Patch applied to HEAD, Fixed.
Reopened - see Bug 332694 - [Help] Standalone help with "-command displayHelp" not working
Created attachment 198297 [details] Patch version 2
Chris, please also update the bundle version in the manifest.
Good catch, I have updated the bundle version. I'll set the state to fixed once 3.8M1 is added to the target milestones.
(In reply to comment #6) > Good catch, I have updated the bundle version. I'll set the state to fixed once > 3.8M1 is added to the target milestones. I get API tooling errors now.
You must be using 3.6.2 ( and not 3.7) as the API baseline. The API problem filters need to change every time the bundle version changes. If 3.7 is the API baseline no errors will show because there has been no API change since 3.7, I will fix the filters to get rid of the errors when 3.6.2 is the baseline.
(In reply to comment #8) > You must be using 3.6.2 ( and not 3.7) as the API baseline. Ah yes. We (JDT) are currently coding for 3.7.1 and hence I didn't pump up the API baseline yet. Sorry for the noise.
This was fixed in 3.8M1, see Comment 6.
I see this was targeted to 3.8, and not 3.7.1 or 3.7.2 -- is this because there's some sort of workaround for 3.7.x? I ask because I'm seeing this consistently trying to launch org.eclipse.help.base.infocenterApplication within the IDE (using an Eclipse Application Run Config)... I'm trying to test some changes I've made to my help plugin, and I'd rather not have to rebuild and redeploy each time I make a minor HTML modification :) Thanks!
(In reply to comment #11) > I see this was targeted to 3.8, and not 3.7.1 or 3.7.2 -- is this because > there's some sort of workaround for 3.7.x? I don't think so. It was just not considered critical enough to be backported.
