I've been trying for about two months to get Elcipse (the Java compilier) to install on my system, and no matter what I do it tells me to check a log file that doesn't exist (an error occurs as it trys and fails to open). So I'm in a bind. If anyone can help with this problem of course that's be great, but I doubt it, so my question is, are there any good Java copmiliers out there (besides Eclipse)? And if they're command line type programs, how do you do that?
I have what is basically a UNIX emulator (Cygwin), so I can probably handle UNIX or Windows appilications.
Hobbes Posted by kaioshin00 (Member # 3740) on :
Umm. You can't use the compiler that comes with the java development kit from sun microsystems?
[ November 08, 2004, 10:54 PM: Message edited by: kaioshin00 ]
Posted by King of Men (Member # 6684) on :
[nitpick] Eclipse is not a compiler, but an IDE. And you spelled it wrong anyway.[/nitpick]
Why don't you just use the java compiler that comes with the development kit, and emacs for editing source code? Works perfectly for me.
Posted by kaioshin00 (Member # 3740) on :
Hurray! another emacs fan! Down with Vi.
Posted by Zevlag (Member # 1405) on :
Down with VI!?!
*whacks kaioshin*
Posted by fugu13 (Member # 2859) on :
<-- must admit that, forced to choose, its emacs all the way. I like an operating system available in my text editor . However, I tend to do most of my coding in BBEdit, a wonderful mac app.
People above are right, what you're talking about is an IDE, which is essentially unrelated to a compiler (though the IDE often hooks into the compiler). There are many, many Java IDEs out there. This search lets you find tons of them: http://www.google.com/search?q=java+ides&ie=UTF-8&oe=UTF-8
Furthermore, as eclipse is a very popular open source project I would suggest some simple steps: google for the error you get when you try to start it (if the error seems environment specific, try to pick out general elements of it). Ask on some programming forums about the particular error, or perhaps on the Eclipse mailing lists or newsgroups (all referenced on the eclipse website). In fact, make sure when you google you take a look at the google groups tab.
If you haven't solved your problem at this point, its likely quite a problem .
Posted by Bekenn (Member # 6602) on :
It's also worth noting that Borland has a free version of JBuilder available from their web site.
Posted by Bokonon (Member # 480) on :
Huh. I've never had an issue installing Eclipse. Did you make sure you installed Sun's JDK beforet installing Eclipse?
-Bok
Posted by IanO (Member # 186) on :
Yeah, from what I remember, Borland puts out JBuilder X, foundation version, for free. Doesn't do everything (of course, neither does professional) but I found it very useful. It became very intuitive.
I've got JBuilder installed and running, haven't tested it out yet but it looks good. Thanks!
Hobbes Posted by twinky (Member # 693) on :
BBEdit: It Doesn't Suck™.
Best slogan ever. Posted by Hobbes (Member # 433) on :
So I've got JBuilder up and running and I really like the interface, this is good. The one thing is that it doesn't seem to want to handle multiple Java files. As in, if I extend one class with another it tells me it doesn't recognize the second class even though I certainly have the class file in the project and what not. Was Eclipse letting me get away with (not doing) something that I need to do to make the compilier recognize that there's other files out there, or is there some setting I haven't found yet in JBuilder or what?
Hobbes Posted by kaioshin00 (Member # 3740) on :
*cough*
Why don't you use the compiler that comes with java development kit? Posted by Hobbes (Member # 433) on :
I like a more ... user-friendly IDE. Which yes, I actually do know what it is, I just don't care enough to distinguish between it and a compiler.
Hobbes Posted by Hobbes (Member # 433) on :
And I'd just like to say that though I'm normally a Microsoft fan, at least in terms of their products, and I really love developing on MS VS .NET, I seriously resent the way they made J#.
That is all.
Hobbes Posted by Hobbes (Member # 433) on :
*bump*
Hobbes Posted by Hobbes (Member # 433) on :
*bump* ?
Hobbes Posted by MrSquicky (Member # 1802) on :
Hobbes, What are the bumps for? Isn't the business here done?
Incidentally, if you're using JBuilder (I think the free thing is a good mrketing thing on their part. I bought the more advanced stuff because they got me hooked on the free versions and now it's what I'm comfotable with), I'd recommend checking out the opentools site. They've got some pretty spiffy add-ons there.
Posted by kaioshin00 (Member # 3740) on :
post.count++;
Posted by Hobbes (Member # 433) on :
quote:So I've got JBuilder up and running and I really like the interface, this is good. The one thing is that it doesn't seem to want to handle multiple Java files. As in, if I extend one class with another it tells me it doesn't recognize the second class even though I certainly have the class file in the project and what not. Was Eclipse letting me get away with (not doing) something that I need to do to make the compilier recognize that there's other files out there, or is there some setting I haven't found yet in JBuilder or what?
Hobbes Posted by MrSquicky (Member # 1802) on :
Hobbes, My bad. It sounds like you may be running into packaging problems. When you create a new class, JBuilder generally defaults to putting it into the package of the currently active file. Check to make sure that you're package statements are congruent and, if not, just import the class in the other package into the thread or refactor the package assignment in the class you want to change.
Or it could be that the class it says it can't find isn't on your project's classpath. You can change that by using the menu itme Project -> Project Properties and then under the Paths section (it should be open by default) select the Required Libraries and add the other project or library that contains it.
There's also an OpenTool that I use that's really useful for class importing that makes it so you can press Ctrl+F11 over a not found class and it will give you a dropdown list of all the classes in your current classpath that could match that class and let you automatically import it by clicking on the right one.
I hope that helps. If it doesn't, give me a more complete description of the problem and I should probably be able to help.
Posted by Hobbes (Member # 433) on :
It seems to be working, thanks a million Squicky-mister!
Hobbes Posted by Hobbes (Member # 433) on :
OK, so now I'm having a new problem (unrelated to work for once) and I'm hoping that someone knows what this is right off the bat... I createde a new project from existing .java files (I've tried multiple ways of doing this, from creating the project with the working directory where the code was, to creating a blank project and then adding in the files manually). And I continually get the problem that it thinks various files (the it here being JBuilder) are defined twice, listing the same path for each file (like the file .../.../.../...java is also defined at .../.../exactly_the_same_path). And then of course, can't compile since it thinks there's an error. I've tried searching through project properties and what not to see if there's two pointers to this folder, or another one, as a source folder but I can't find anything. Any ideas?
Hobbes Posted by Hobbes (Member # 433) on :
*bump*
Hobbes Posted by Jay (Member # 5786) on :
This was build with your other tool? Anything in there it could be referencing? I know sometimes JBuilder can be picky about libraries. Can’t think of anything else right off the bat. Can you post the error? That might have some goodies in it
Posted by MrSquicky (Member # 1802) on :
JBuilder doesn't like it when files aren't stored in directories that reflect their package structure. Sucks, but there you go. It sounds like that's probably what you're running into.
If you have a bunch of classes in say a squicky.bluebuttbaboon package, the java files need to be stored in a directory like /src/squicky/bluebuttbaboon. If the directories don't match up with the packages, you get problems like what you're talking about.
Also, when you move files around in directories and packages, you generally need to rebuild the project instead of just compiling it. Otherwise, JBuilder tries to include all the previous generated class files in its build and you'll generally run into something like a class defined in more than one place error.
![[Smile]](smile.gif)
![[Wink]](wink.gif)
. However, I tend to do most of my coding in BBEdit, a wonderful mac app.![[Big Grin]](biggrin.gif)
![[Cool]](cool.gif)
The one thing is that it doesn't seem to want to handle multiple Java files. As in, if I extend one class with another it tells me it doesn't recognize the second class even though I certainly have the class file in the project and what not. Was Eclipse letting me get away with (not doing) something that I need to do to make the compilier recognize that there's other files out there, or is there some setting I haven't found yet in JBuilder or what?![[Confused]](confused.gif)
![[Group Hug]](graemlins/grouphug.gif)