ports/131872: port java/eclipse uses build directories

[Lapo Luchini]

>Number:         131872
>Category:       ports
>Synopsis:       port java/eclipse uses build directories
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 19 11:10:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Lapo Luchini
>Release:        FreeBSD 6.4-STABLE amd64
>Organization:
>Environment:
System: FreeBSD lapo.andxor.it 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan  1 08:58:24 UTC 2009     root at driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:

I hust upgraded Eclipse from the ports (to latest 3.4.1) and it stopped working, printing various paths relative to the ports directory where it was built.

>How-To-Repeat:

% eclipse
Cannot open "../../ports/java/eclipse/work/eclipse/configuration/org.eclipse.osgi/bundles/71/data/1632909880/plugins/org.eclipse.equinox.launcher.gtk.freebsd.amd64_1.0.101.R34x_v20080731"

% fgrep -Rl ../../ports/java/eclipse/work /usr/local/eclipse
/usr/local/eclipse/eclipse.ini
/usr/local/eclipse/configuration/org.eclipse.equinox.source/source.info

>Fix:

As a work-around I was thinking about sed-ing the correct path in those files, but I can't find a file named 'org.eclipse.equinox.launcher*' anywhere, so I guess the problem is worse than simply using the wrong relative path.
>Release-Note:
>Audit-Trail:
>Unformatted: