Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313360 - FeaturesAndBundlesPublisher does not work with urls with %20 spaces
Summary: FeaturesAndBundlesPublisher does not work with urls with %20 spaces
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Scripting (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Scripting-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-18 10:06 EDT by Micah Hainline CLA
Modified: 2020-12-01 05:49 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Micah Hainline CLA 2010-05-18 10:06:16 EDT
Build Identifier: unknown

The application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher takes a metadataRepository and artifactRepository url.  When that url is a file url of the form file:/C:/path%20with%20spaces then the repository is incorrectly built at the file "C:\path%20with%20spaces" instead of "C:\path with spaces".  

Needless to say, this plays merry hell with the rest of my build process that relies on the repositories being in the correct location.  :)

Reproducible: Always
Comment 1 Micah Hainline CLA 2010-05-18 10:07:52 EDT
This is using the latest headless Buckminster installed using p2 from http://download.eclipse.org/tools/buckminster/headless-3.6
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:04:00 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.
Comment 3 Lars Vogel CLA 2020-12-01 05:49:27 EST
The scripting sub-category in platform is not used anymore and platform does not support scripting. Please check if you bug is still valid and report it or move it to the correct component.