git master updated for eclipse 3.5 (galileo)

[Eric Van Dewoestine]

As most of you may know, the latest version of eclipse (galileo, 3.5)
was released yesterday. Eclim 1.4.x and lower are not officially
supported on this version of eclipse. However, I've just merge in the
necessary changes to the eclim master branch to now support running on
galileo. I'm hoping to have a final release ready by this weekend,
but in the meantime, if you would like to run eclim on the galileo,
you can now checkout the latest code from the git repos and build the
code yourself.

For anyone still running on eclipse 3.4 (ganymede), please note that
portions of the master branch may no longer compile against eclipse
3.4 (pdt and cdt support for example). So please don't pull the
latest code unless you are prepared to upgrade eclipse as well.

If anyone has an questions or concerns, please feel free to let me
know.

--
eric

[Lee Hinman]

Hey Eric,
I'm having an issue compiling the latest git code against Eclipse 3.5.
I'm getting this error:

% ant -Declipse.home=/Applications/Eclipse/ -Dplugins=ant,jdt
Buildfile: build.xml

init:

build.eclipse:
[javac] Compiling 30 source files to /Users/hinmanm/src/java/
eclim/build/temp/classes
[javac] /Users/hinmanm/src/java/eclim/src/java/org/eclipse/swt/
widgets/EclimComposite.java:30: cannot find symbol
[javac] symbol : method checkStyle(int)
[javac] location: class org.eclipse.swt.widgets.EclimComposite
[javac] super (parent, checkStyle (style));
[javac] ^
[javac] 1 error

Do you know what would be causing this issue?

- Lee

[Eric Van Dewoestine]

I'm not sure why that would compile for me and not you, but
regardless, I removed the call to checkStyle since it's not really
necessary anyways. Try pulling the latest from git and see if it
compiles for you now.

--
eric

[Lee Hinman]

On Jun 28, 2009, at 10:44 PM, Eric Van Dewoestine wrote:
>
> I'm not sure why that would compile for me and not you, but
> regardless, I removed the call to checkStyle since it's not really
> necessary anyways. Try pulling the latest from git and see if it
> compiles for you now.
>
> --
> eric

Eric,
Pulling from the latest git fixed the problem, the only thing I had to
do was copy the $ECLIPSE_HOME/eclipse symlink to the new Galileo
Eclipse directory so the eclimd script could find the eclipse
executable (on OSX).

Thanks for the quick fixes!

- Lee

[Glenn]

I pulled down the latest code and built the pdt and jdt plugins.
However, when starting up I see these errors:

2009-06-29 16:36:45,347 INFO [org.eclim.plugin.core.CorePlugin]
Loading eclim plugins...
2009-06-29 16:36:45,352 INFO [org.eclim.plugin.core.CorePlugin]
Loading plugin org.eclim.pdt
2009-06-29 16:36:45,369 ERROR [org.eclim.plugin.core.CorePlugin]
Failed to load plugin org.eclim.pdt:
Cannot find bundle org.eclim.pdt.

2009-06-29 16:36:45,370 INFO [org.eclim.plugin.core.CorePlugin]
Loading plugin org.eclim.jdt
2009-06-29 16:36:45,370 ERROR [org.eclim.plugin.core.CorePlugin]
Failed to load plugin org.eclim.jdt:
Cannot find bundle org.eclim.jdt.

2009-06-29 16:36:45,370 INFO [org.eclim.plugin.core.CorePlugin]
Plugins loaded.

Any suggestions on what I can do to get this up and running? The ant
build ran properly. The plugins are there and everything looks great.
I can't seem to find any information on why Eclipse might choose to
pretend a bundle doesn't exist when, to me at least, it does.

[Eric Van Dewoestine]

On Mon, Jun 29, 2009 at 3:37 PM, Glenn<glenn...@gmail.com> wrote:
>
> I pulled down the latest code and built the pdt and jdt plugins.
> However, when starting up I see these errors:
>
> 2009-06-29 16:36:45,347 INFO  [org.eclim.plugin.core.CorePlugin]
> Loading eclim plugins...
> 2009-06-29 16:36:45,352 INFO  [org.eclim.plugin.core.CorePlugin]
> Loading plugin org.eclim.pdt
> 2009-06-29 16:36:45,369 ERROR [org.eclim.plugin.core.CorePlugin]
> Failed to load plugin org.eclim.pdt:
> Cannot find bundle org.eclim.pdt.
>
> 2009-06-29 16:36:45,370 INFO  [org.eclim.plugin.core.CorePlugin]
> Loading plugin org.eclim.jdt
> 2009-06-29 16:36:45,370 ERROR [org.eclim.plugin.core.CorePlugin]
> Failed to load plugin org.eclim.jdt:
> Cannot find bundle org.eclim.jdt.
>
> 2009-06-29 16:36:45,370 INFO  [org.eclim.plugin.core.CorePlugin]
> Plugins loaded.
>
> Any suggestions on what I can do to get this up and running? The ant
> build ran properly. The plugins are there and everything looks great.
> I can't seem to find any information on why Eclipse might choose to
> pretend a bundle doesn't exist when, to me at least, it does.

I ran into a similar issue as well and since then I haven't been able
to reproduce it. The steps that resolve the problem for me were:

1. delete all the eclim plugins from eclipse/plugins
2. start eclipse
3. stop eclipse
4. build eclim again (re-deploying the plugins).

Also, make sure that when you build eclim, that you include dltk (new
requirement for pdt support) in the list of plugins, otherwise you'll
just receive an error regarding that dependency not being found.

$ and -Dplugins=dltk,pdt,jdt

I'll try reproducing the problem some more and see if I can find a way
to avoid whatever caching eclipse is performing.

--
eric

[Eric Van Dewoestine]

Could you elaborate on that? What directory did you move the symlink
from and to? Also what path is your ECLIPSE_HOME set to, or if you
supplied it via -Declipse.home, what path did you use there? If it
makes sense to, I'll update the build script to accommodate your
scenario so you, or other users with a similar setup, don't have to
worry about the extra step of moving the symlink around.

--
eric

[Lee Hinman]

Evidently, the new Galileo tarball for OSX doesn't include a symlink
to the Eclipse binary in the Eclipse folder, so I moved the symlink I
had from my old Eclipse installation directory into the new one.

Here's the resulting Symlink:
~% ll /Applications/Eclipse/eclipse
lrwxr-xr-x@ 1 hinmanm staff 34B Jun 28 23:22 /Applications/Eclipse/
eclipse@ -> Eclipse.app/Contents/MacOS/eclipse

I set my -Declipse.home to be /Applications/Eclipse

In the future, I suppose it would make sense to check for OSX-ness (or
create the symlink) since the symlink was missing for me.

- Lee

[Eric Van Dewoestine]

Ah, I misread your earlier mail. I was thinking that the eclimd
symlink was the issue. I didn't realize that the eclipse executable
was located outside the eclipse home on the mac. Just to make it
clear, is the absolute path of your eclipse executable located under
your eclipse home?

/Applications/Eclipse/Eclipse.app/Contents/MacOS/eclipse

Did you install eclipse from an eclipse.org distribution? If this is
a standard location for the eclipse executable, then I can just update
the eclimd script to check that path if the executable isn't found
elsewhere, which should alleviate the need for the eclipse symlink.

--
eric

[Lee Hinman]

Yep, keep in mind that the Mac distribution untars to a folder named
"eclipse", not "Eclipse". I just change it because I'm OCD about
capitalization, so if someone didn't rename it, it'd be:

/Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse

ECLIPSE_HOME in the first example:
/Applications/Eclipse
ECLIPSE_HOME in the second example:
/Applications/eclipse

Hope that makes sense, the actual symlink only links to
'Eclipse.app/Contents/MacOS/eclipse' (relative), not the full Eclipse
path.

> Did you install eclipse from an eclipse.org distribution?  If this is
> a standard location for the eclipse executable, then I can just update
> the eclimd script to check that path if the executable isn't found
> elsewhere, which should alleviate the need for the eclipse symlink.

Yep, this is the OSX tarball downloaded from eclipse.org. The
executable for Eclipse should *always* be
ECLIPSE_HOME/Eclipse.app/Contents/MacOS/eclipse on OSX (unless the
Eclipse foundation changes it), so you should be able to add a check
for it.

Let me know if there's anything else I can do to help.

- Lee

[Eric Van Dewoestine]

I went ahead and added the additional path to the eclimd script, so if
you can, please pull the latest git, remove your eclipse symlink and
see if the new script finds your eclipse executable correctly.

Thank you very much for your help so far. Without direct access to a
mac myself, I've had to rely heavily on the helpfulness of mac users
such as yourself, and I really do appreciate it.

--
eric

[Steven K. Wong]

I ran eclim_1.5.0.sh on my Mac OS X with Eclipse 3.5, and received the
"No eclipse executable found" error from the installer. I had to
manually create the eclipse symlink before the install could go
through.


On Jun 30, 9:23 am, Eric Van Dewoestine <ervan...@gmail.com> wrote:
> On Tue, Jun 30, 2009 at 8:55 AM, Lee Hinman<matthew.hin...@gmail.com> wrote:
>
> > On Tue, Jun 30, 2009 at 9:01 AM, Eric Van Dewoestine<ervan...@gmail.com> wrote:

>
> >> On Mon, Jun 29, 2009 at 4:21 PM, Lee Hinman<matthew.hin...@gmail.com> wrote:
>
> >>> On Jun 29, 2009, at 5:00 PM, Eric Van Dewoestine wrote:
>
> >>>> On Sun, Jun 28, 2009 at 10:25 PM, Lee
> >>>> Hinman<matthew.hin...@gmail.com> wrote:
>
> >>>>> On Jun 28, 2009, at 10:44 PM, Eric Van Dewoestine wrote:
>
> >>>>>> I'm not sure why that would compile for me and not you, but
> >>>>>> regardless, I removed the call to checkStyle since it's not really
> >>>>>> necessary anyways.  Try pulling the latest from git and see if it
> >>>>>> compiles for you now.
>
> >>>>>> --
> >>>>>> eric
>
> >>>>> Eric,
> >>>>> Pulling from the latest git fixed the problem, the only thing I had
> >>>>> to
> >>>>> do was copy the $ECLIPSE_HOME/eclipse symlink to the new Galileo
> >>>>> Eclipse directory so the eclimd script could find the eclipse

> >>>>>executable(on OSX).

>
> >>>> Could you elaborate on that?  What directory did you move the symlink
> >>>> from and to?  Also what path is your ECLIPSE_HOME set to, or if you
> >>>> supplied it via -Declipse.home, what path did you use there?  If it
> >>>> makes sense to, I'll update the build script to accommodate your
> >>>> scenario so you, or other users with a similar setup, don't have to
> >>>> worry about the extra step of moving the symlink around.
>
> >>>> --
> >>>> eric
>
> >>> Evidently, the new Galileo tarball for OSX doesn't include a symlink
> >>> to the Eclipse binary in the Eclipse folder, so I moved the symlink I
> >>> had from my old Eclipse installation directory into the new one.
>
> >>> Here's the resulting Symlink:
> >>> ~% ll /Applications/Eclipse/eclipse
> >>> lrwxr-xr-x@ 1 hinmanm  staff    34B Jun 28 23:22 /Applications/Eclipse/
> >>> eclipse@ -> Eclipse.app/Contents/MacOS/eclipse
>
> >>> I set my -Declipse.home to be /Applications/Eclipse
>
> >>> In the future, I suppose it would make sense to check for OSX-ness (or
> >>> create the symlink) since the symlink was missing for me.
>
> >> Ah, I misread your earlier mail.  I was thinking that the eclimd
> >> symlink was the issue.  I didn't realize that the eclipseexecutable
> >> was located outside the eclipse home on the mac.  Just to make it

> >> clear, is the absolute path of your eclipseexecutablelocated under

> >> your eclipse home?
>
> >> /Applications/Eclipse/Eclipse.app/Contents/MacOS/eclipse
>
> > Yep, keep in mind that the Mac distribution untars to a folder named
> > "eclipse", not "Eclipse". I just change it because I'm OCD about
> > capitalization, so if someone didn't rename it, it'd be:
>
> > /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse
>
> > ECLIPSE_HOME in the first example:
> > /Applications/Eclipse
> > ECLIPSE_HOME in the second example:
> > /Applications/eclipse
>
> > Hope that makes sense, the actual symlink only links to
> > 'Eclipse.app/Contents/MacOS/eclipse' (relative), not the full Eclipse
> > path.
>
> >> Did you install eclipse from an eclipse.org distribution?  If this is

> >> a standard location for the eclipseexecutable, then I can just update

> >> the eclimd script to check that path if theexecutableisn'tfound
> >> elsewhere, which should alleviate the need for the eclipse symlink.
>
> > Yep, this is the OSX tarball downloaded from eclipse.org. The

> >executablefor Eclipse should *always* be

[Eric Van Dewoestine]

On Sun, Jul 12, 2009 at 6:14 PM, Steven K. Wong<skws...@gmail.com> wrote:
>
> I ran eclim_1.5.0.sh on my Mac OS X with Eclipse 3.5, and received the
> "No eclipse executable found" error from the installer. I had to
> manually create the eclipse symlink before the install could go
> through.

What is the exact location of your eclipse executable?

--
eric

[Steven K. Wong]

The following shows the symlink I created pointing to the location of
my eclipse executable:

swong@lgmac-swong:~ 3722> ls -l /Applications/eclipse/eclipse
lrwxr-xr-x 1 swong staff 34 Jul 12 18:11 eclipse@ -> Eclipse.app/
Contents/MacOS/eclipse


On Jul 12, 6:33 pm, Eric Van Dewoestine <ervan...@gmail.com> wrote:

> On Sun, Jul 12, 2009 at 6:14 PM, Steven K. Wong<skwsl...@gmail.com> wrote:
>
> > I ran eclim_1.5.0.sh on my Mac OS X with Eclipse 3.5, and received the

> > "No eclipseexecutablefound" error from the installer. I had to

[Eric Van Dewoestine]

On Sun, Jul 12, 2009 at 9:20 PM, Steven K. Wong<skws...@gmail.com> wrote:
>
> The following shows the symlink I created pointing to the location of
> my eclipse executable:
>
> swong@lgmac-swong:~ 3722> ls -l /Applications/eclipse/eclipse
> lrwxr-xr-x  1 swong  staff  34 Jul 12 18:11 eclipse@ -> Eclipse.app/
> Contents/MacOS/eclipse

I think I see the issue. It looks like I had a typo in the shell
script used by the installer. To verify, if you remove that symlink,
does eclimd still start up correctly (headless version using
$ECLIPSE_HOME/eclimd)?

--
eric

[Steven K. Wong]

Yes, eclimd still starts up after removing the symlink.


On Jul 13, 7:23 am, Eric Van Dewoestine <ervan...@gmail.com> wrote:

[Eric Van Dewoestine]

On Mon, Jul 13, 2009 at 9:07 AM, Steven K. Wong<skws...@gmail.com> wrote:
>
> Yes, eclimd still starts up after removing the symlink.

Ok, good. I'll apply the change to the installer for the next
release. Thank you for the help.

--
eric