Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 83487

Summary: shared launch configs have hard-coded locations
Product: [Eclipse Project] PDE Reporter: Adam Kiezun <akiezun>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: douglas.pollock
Version: 3.1   
Target Milestone: 3.1 M5   
Hardware: All   
OS: All   
Whiteboard:

Description Adam Kiezun CLA 2005-01-22 15:12:05 EST 
3.1M4
My project is shared with people using Linux and Windows. We'd like to share
launch configs too (plugin junit test). However, configs have a 'location' field
which is hardcoded and platform specific
Comment 1 Darin Wright CLA 2005-01-31 09:49:10 EST 
Use the common tab to share the config with your team - i.e. "Save as > Shared 
file". Then specify a workspace location for the config.
Comment 2 Adam Kiezun CLA 2005-01-31 09:55:14 EST 
Darin,
I meant the runtime workspace location (this may be a PDE bug)
I have this in the .launch file:

<stringAttribute key="location1" value="C:\workspaces\junit-workbench-workspace"/>

which is competely nonsensical on linux
btw there's another place:
<stringAttribute key="location0" value="C:\workspaces\junit-workbench-workspace"/>
Comment 3 Wassim Melhem CLA 2005-01-31 11:39:11 EST 
you can enter a relative location in the workspace data field, should you 
choose to.
Comment 4 Douglas Pollock CLA 2005-02-02 08:33:57 EST 
Relative to what?  How do you specify a relative path?  How well will this 
work in a cross-platform situation?
Comment 5 Adam Kiezun CLA 2005-05-06 10:30:06 EDT 
how come this got closed?
this is still a big problem in M6. I end up with hard-wired locations, different
on both platforms i'm using. This makes it useless in a cross-platform setting.

Can you advice how to specify the location in the temp dir?
Comment 6 Douglas Pollock CLA 2005-05-06 10:41:37 EDT 
Yeah, Wassim, I think my questions in comment #4 fell through the cracks.
Comment 7 Adam Kiezun CLA 2005-05-06 10:47:46 EDT 
see also bug 93915 requesting access to system properties - I could then place
my workspace in the temp dir
Comment 8 Wassim Melhem CLA 2005-05-06 10:54:56 EDT 
if support for workspace locations is what you are looking for, then this is a 
dup of bug 86796 and cannot be contained in 3.1

This situation is not without a workaround though.

whatever value you enter in the workspace location field gets passed as-is to 
the runtime in the '-data' program arg.

So you can enter a platform-independent relative path like "myworkspace/bla" 
and a directory by that name will be created relative to the install location 
of your target platform.

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