Eclipse

Thread view:

Shawn McDermott - 20 Jul 2003 15:27 GMT

I am trying to move my project from Sun One Studio....to Eclipse. I
have had absolutly no luck with Forte(sun one). I have to kill the ide
many times just to clear duplicate class errors when there are none.

Anyway, can someone talk me through moving my project to Eclipse?

Shawn

Reply to this Message

Tim Tyler - 20 Jul 2003 22:16 GMT

: I am trying to move my project from Sun One Studio....to Eclipse. I
: have had absolutly no luck with Forte(sun one). I have to kill the ide
: many times just to clear duplicate class errors when there are none.

: Anyway, can someone talk me through moving my project to Eclipse?

Start my making sure all your source files are in one directory,
and all your class files are in another one.

Eclipse likes things like that.

Signature

__________
|im |yler http://timtyler.org/ tim@tt1.org

Reply to this Message

tk - 21 Jul 2003 04:08 GMT

Also,
check out the myriad of plugin's available with eclipse:

http://eclipse-plugins.2y.net/eclipse/plugins.jsp?category=Whatsnew&pager.of
fset=10

What a great IDE!!!

I'm using the quantum JDBC-Connectivity and JBoss IDE plugin's for eclipse
among other things!!!

They even have a few Swing GUI builder ones that generate code/event
handlers. Wish I would have
knew that earlier so I did not have to do all those GridBagLayout constaints
by hand ;-P

Eclipse rocks!!!

Reply to this Message

Jon A. Cruz - 21 Jul 2003 04:56 GMT

> Start my making sure all your source files are in one directory,
> and all your class files are in another one.
>
> Eclipse likes things like that.

Actually, it likes the opposite.

Make sure you source files are all in a proper directory hierarchy that
mirrors your packaging (you are using packages, aren't you).

If you have pre-built classes that you have to use (eww), put them in a
project by themselves, in a propery directory hierarchy also.

Often if you have things split into a few different source directories
it has been done for a reason, and those reasons usually map well into
separate Eclipse projects.

Oh, and once you have a project that relies on another, just go to the
project in the browser that has the dependency, right click it, then
look for "properties" on that popup menu. Add your other project and
you're off!

Reply to this Message

Tim Tyler - 21 Jul 2003 11:03 GMT

:> Start my making sure all your source files are in one directory,
:> and all your class files are in another one.
:>
:> Eclipse likes things like that.

: Actually, it likes the opposite.

: Make sure you source files are all in a proper directory hierarchy that
: mirrors your packaging (you are using packages, aren't you). [...]

I'll put it another way - don't try using the javac default - of having
your class files and source files stored in the same directories.

Eclipse has a tendency to totally delete all the files in the
user's "bin" directory without asking permission, you see.

Signature

__________
|im |yler http://timtyler.org/ tim@tt1.org

Reply to this Message

Shawn McDermott - 22 Jul 2003 01:32 GMT

>> Start my making sure all your source files are in one directory,
>> and all your class files are in another one.
[quoted text clipped - 5 lines]
> Make sure you source files are all in a proper directory hierarchy that
> mirrors your packaging (you are using packages, aren't you).

thanks to all. I am getting it up and running! I have never used forte
from the beginning (of time), but now the project I am on, they are
trying to push it down my throat. I am going to get eclipse working and
show them what a hunk of junk sunOne-forte really is.

thanks again
Shawn

Reply to this Message

Eclipse

Free Magazines