I've been using Eclipse for about 3 months now and all I can say is WOW.
I used Forte before Eclipse and when I changed I felt a huge relief from
Forte's resource demands. It was a lot faster not only first loading, but
also responding to general user interaction.
But what really made me into Eclipse was its "on the fly" error
discovery. With Forte, I had to wait until compile time to get most of the
errors Eclipse shows me when I am writing, and this is a lot faster since I
don't have to wait for compilation just to know about simple syntax or
include errors.
Another thing I liked was its "save & compile" feature (Automatic build,
as it is called inside Eclipse). I think is a natural way of compiling.
One thing I had problems with was that Eclipse erases all compiled
classes when refreshing a project. And when it finds and error (a missing
library, for example) it just quits recompiling, which left us without a
single compiled class and no one knew why (now we do, but we had to
investigate a little).
Another thing is that when I was starting to use it, I wanted to import
a project we were already building with other IDE's. So I had some trial and
error before finding out where I should place the Eclipse project folder. In
one of this trial and error projects, I answered yes to the "Should Eclipse
erase all project files?" question. Thought it would only erase Eclipse
project files. Wrong guess. We had a backup, so we solved it rather quickly,
but my coworkers got a bad first impression from Eclipse. So be careful with
that...
Anyway, I think is great and it's free. I would like to find some way to
debug Turbine apps from inside it, but even if I couldn't (and I think I
will find out sooner or later), it is the best I have tried.
This are my 2 cents...
Rodrigo
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 27, 2003 7:09 PM
Subject: RE: Anyone using Eclipse with Turbine?
> Well,
>
> I have to say, after using the maven plugin to generate my eclipse
projects,
> I am pretty impressed with Eclipse. What I remember from before was that
> eclipse wanted to import everything into it's own directory, rather then
let
> me use my maven builds. Now, it seems that eclipse will let me use it
just
> as an IDE. I may just have to switch from JEdit!
>
> However, I can't seem to get either the Build With External Tools stuff to
> work from Maven (I know, a little OT) or the Tomcat debugger. If I could
> debug tomcat, then I would be golden!
>
> Eric
>
> -----Original Message-----
> From: David Worms [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 27, 2003 6:57 PM
> To: Turbine Users List
> Subject: Re: Anyone using Eclipse with Turbine?
>
>
> >
> > Eclipse Con:
> > - IDEA has pretty good caching and seems to work faster as long as you
> > have
> > a whole bunch of memory allocated to it (but the speed of the UI and
> > incremental compiles in Eclipse makes up for it).
> > - IDEA seemed to have better search/replace facilities across files.
> >
>
> Being an OS 10 user also, I use BBEdit for search/replace. At least one
> of the two Cons:)
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
