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

Bug 344153

Summary:	[director] director -roaming still includes absolute paths
Product:	[Eclipse Project] Equinox	Reporter:	Paul Webster <pwebster>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	irbull, jesper.eskilson, mknauer, pascal
Version:	3.7	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Linux
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=342156
Whiteboard:	stalebug

Description Paul Webster

2011-04-28 11:48:32 EDT

I created an install with a shared bundle pool:

TARGET=$(pwd)/target
eclipse/eclipse -application org.eclipse.equinox.p2.director \
-noSplash -bundlepool $TARGET -shared $TARGET/p2 \
-destination $TARGET/win32_win32_x86 \
-profile SDKProfile_win32_win32_x86 \
-profileProperties org.eclipse.update.install.features=true \
-p2.os win32 -p2.ws win32 -p2.arch x86 -roaming \
-repository http://download.eclipse.org/eclipse/updates/3.6 \
-installIUs org.eclipse.sdk.ide

It created $TARGET/linux_gtk_x86_64/configuration/config.ini with an absolute path:
eclipse.p2.data.area=file\:/opt/local/eclipse/I20110427-1300/target/p2/

instead of the equivalent relative path:
eclipse.p2.data.area=@config.dir/../../p2/

This prevents distributing the zipped up platform.

PW

Comment 1 Paul Webster

2011-04-28 11:54:42 EDT

The director also added an absolute path in the $TARGET/linux_gtk_x86_64/eclipse.ini:

-install
/opt/local/eclipse/multiPlatform/eclipse/linux_gtk_x86_64

See bug 344155

PW

Comment 2 Jesper Eskilson

2017-04-11 09:30:11 EDT

I'm struggling with this exact problem. The resulting eclipse installation has "-install /some/abs/path" in it. 

But the weird thing is that when I try to run the same director invocation from inside Eclipse (to debug it), it works; the "-install ..." part is omitted from config.ini.

Comment 3 Eclipse Genie

2019-09-08 12:39:18 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.

--
The automated Eclipse Genie.