Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319103 - [target] Allow relative paths for p2 repositories in target definition files
Summary: [target] Allow relative paths for p2 repositories in target definition files
Status: CLOSED DUPLICATE of bug 282254
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-07 06:51 EDT by Jan Poganski CLA
Modified: 2010-07-07 14:49 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Poganski CLA 2010-07-07 06:51:20 EDT 
Build Identifier: I20100608-0911

I created a target defintion that only contains p2 repo. These repositories are zip files form Eclipse downloads. I want to store these repos together with my target definition in a version control system. Sharing my target with other developers this way however is a pain because the target definition file contains the absolute paths to the repositories. The repo locations are noted as JAR URLs which do not allow relative paths as far as I know. Target definitions should allow relative paths to p2 repositories.

Reproducible: Always

Steps to Reproduce:
1. Create a target definition file.
2. In the target editor click "Add..." and choose "Software Site".
3. Clear the field "Work with:".
4. Note the validation result "Location must be absolute".
Comment 1 Curtis Windatt CLA 2010-07-07 14:49:30 EDT 
The best workaround for this would be to use variables.  You can set a variable for the workspace and then use a path relative to that.

There is already a request to have a variable for "target definition location".

*** This bug has been marked as a duplicate of bug 282254 ***