Community
Participate
Working Groups
1. Install Eclipse into a directory containing spaces in the name (e.g. "/opt/eclipse301\ sdk"). 2. Start Eclipse. 3. Open Help > About > Feature Details and select a feature. 4. Click More Info -- nothing happens. If installed into a directory that does not contain spaces, then this works fine. And works fine on Windows in either case. It's understood that using paths with spaces is not that common in Linux, but it is possible and valid to do so. So this should work in that case...
Any progress on fixing this problem?
Beth, would you be willing to investigate a patch for this? See AboutFeaturesDialog.handleMoreInfoPressed(), which ends up calling ProductInfoDialog.openLink.
We will look into this problem. May need your help.
Beth to supply patch for 3.0.2.
We have came up a fix for defect #77840. Please review the fix. If it's possible, we would like this fix to be in the 3.0.2 release. The source code has comments with //77840 for the changes we made, we had added a new method urlEncodeForSpaces to take care of the space.
Created attachment 17176 [details] fix attempt
The attachment does not appear to be a patch. It is a copy of the ProductInfoDialog containing the changes. It is easier to work with submitted work if it comes in the form of a patch. To create a patch, right-click on the file in the package explorer and select "Team > Create Patch...". This *might* have bizarre effects with particular combinations of VMs (i.e., how they implement exec) and shells (i.e., non-sh compliant). I've tested this by creating a plug-in project with spaces in the name. With the patch, the info page appears without any problems. Without the patch, badness ensues. Looks good to me.
Created attachment 17234 [details] Patch to "org.eclipse.ui.workbench" Converts the given file into a patch, and removes changes to spacing. Minor formatting changes included. This patch is intended for the 3.0.2 stream.
This conversion may also be needed on the Mac. Michael, could you try the original steps?
Patch applied to the head and 3.0.x streams.
Beth, could you please verify that this is fixed in the 3.0.2 RC2 build?
I have verified the fix, it's working.
Thanks Beth.