|
Re: mac all-in-one pdt 2.0 [message #86554 is a reply to message #86540] |
Fri, 12 December 2008 16:49 |
Eclipse User |
|
|
|
Originally posted by: nickboldt+eclipse+newsgroup.gmail.com
Try making the eclipse executable executable. Had this issue on linux.
cd /path/to/where/you/unpacked/eclipse
chmod +x eclipse
../eclipse -vm /path/to/java5.0
(when in doubt, run from the console to see what the error is.)
This is a bug in the current all-in-one packaging script which will
hopefully be fixed by the time soon.
Dan Svoboda wrote:
> I've downloaded pdt-all-in-one-macosx-carbon-2.0.0RC1.tar.gz, and after
> unarchiving it fails to launch. No splash, no errors. Using Leopard,
> java 1.5.0_16-133.
>
> Tried forcing java 1.5 in eclipse.ini (-vm /path/to/javavm). Also tried
> -Dosgi.requiredJavaVersion=1.5.
>
> I've been using ganymede-javaEE for months without issue, but wanted an
> easy, pre-configured path to pdt.
>
> Any ideas?
>
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
|
|
|
|
Re: mac all-in-one pdt 2.0 [message #86959 is a reply to message #86776] |
Tue, 16 December 2008 20:51 |
Eclipse User |
|
|
|
Originally posted by: nickboldt+eclipse+newsgroup.gmail.com
Working on a new version now, per reported issues in
http://bugs.eclipse.org/256440
You can test it early here:
http://modeling.eclipse.org/pdt/downloads/?sortBy=date
Didn't mention it in the bug, but the permissions and symlinks are now
fixed (I gave up on using Ant to tar the archive, so now I can just
update an existing archive without having to even touch the files
packaged by the Eclipse Platform team).
Gavin Gilmour wrote:
> Dan Svoboda wrote:
>
>> I've downloaded pdt-all-in-one-macosx-carbon-2.0.0RC1.tar.gz, and
>> after unarchiving it fails to launch. No splash, no errors. Using
>> Leopard, java 1.5.0_16-133.
>
>> Tried forcing java 1.5 in eclipse.ini (-vm /path/to/javavm). Also
>> tried -Dosgi.requiredJavaVersion=1.5.
>
>> I've been using ganymede-javaEE for months without issue, but wanted
>> an easy, pre-configured path to pdt.
>
>> Any ideas?
>
> I had the same issue as this throw me a bit yesterday. For some reason,
> the usual 'eclipse' symlink in the root directory to the executable
> Eclipse.app/Contents/MacOS/eclipse was just a regular, zero byte file.
> Trying to execute the actual .app bundle with open -a or something
> similar just failed in silence also which was no help.
>
> However, the solution should hopefully be: rm eclipse && chmod +x
> Eclipse.app/Contents/MacOS/eclipse && ln -s
> Eclipse.app/Contents/MacOS/eclipse && ./eclipse
>
> It just looks like the symlink and permissions have been broken in the
> build.
>
> Gavin.
>
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
|
|
|
Powered by
FUDForum. Page generated in 0.03854 seconds