Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 262465 - Product files should store locations using relative paths
Summary: Product files should store locations using relative paths
Status: RESOLVED DUPLICATE of bug 260328
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5 M7   Edit
Assignee: Chris Aniszczyk CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 262464
  Show dependency tree
 
Reported: 2009-01-26 19:47 EST by Ian Bull CLA
Modified: 2009-04-13 12:58 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Bull CLA 2009-01-26 19:47:25 EST
Product files store the location of a number of things (config.ini, exes, etc...). These should be stored relative to the .product files parent folder.
Comment 1 Chris Aniszczyk CLA 2009-01-26 19:47:59 EST
I agree Ian.

Andrew, do you forsee any changes in PDE Build?
Comment 2 Curtis Windatt CLA 2009-01-28 12:14:01 EST
I imagine this should be pushed to M6.
Comment 3 Chris Aniszczyk CLA 2009-01-28 12:17:14 EST
Agreed, there's a little too much churn for this one still.

It should be an easy fix for early M6

I would actually prefer to just limit people to the current project for selecting the product definition.
Comment 4 Andrew Niefer CLA 2009-01-28 13:59:19 EST
There is work for this in build, build replaces versions in the .product file and writes the new one to a different location.  We then point publisher at the new copy, anything publisher is expecting to find relative to the .product file will also need to be copied to the new location.
Comment 5 Chris Aniszczyk CLA 2009-03-10 13:57:40 EDT
I don't think we'll need this at all once we move to properties support in M7
Comment 6 Chris Aniszczyk CLA 2009-04-13 12:58:26 EDT
going to mark this a dupe of bug 260328 as this won't be an issue when 260328 is solved

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