Re: Q: Classpath and Eclipse
Hi, On Fri, Nov 07, 2003 at 12:21:14AM +0100, Patrik Reali wrote: Has anybody already tried to import classpath under Eclipse? I tried to create a project and import the files, but then Eclipse is far too intelligent: * gnu/java/lang classes are imported into package java.lang * vm/reference/java/lang classes are imported into package vm.java.lang Probably I'm just doing something wrong (I'm using Eclipse 3.0M4) Eclipse is trying to be much to smart and it doesn't seem as flexible as we want it to be. Some of this might be my inexprience with using the Eclipse JDT though. It seems to want to insist on using a multiple project layout if your filesystem has multiple source directories that contain classes that belong in the same package (combining java and vm/reference/java). It has its own exclusion mechanism (you want to use the lib/standard.omit file). You have to remove the standard JRE libraries (since the kaffe or gcj standard libraries are slightly different, which you will notice when trying to compile the VMinterface classes). We have things like gnu.classpat.Configure which is generated in the obejct tree and doesn't live in the source tree. It does support some Ant trickery, but I haven't gotten that to work yet (mostly Ant being to smart and trying to call all kinds of com.sun classes. Sigh...). Since the CDT seems to have some Makefile support we might be able to hack on that to get the Classpath build structure working. That has the advantage of integrating the build with our JNI C stuff. I don't know how easy it for Eclipse to parse the error output of external tools (like emacs can). If that is possible then we could still use our own Makefile structure and use the standalone eclipse java compiler that Anthony Green created for the RHUG project (he calls it ecj and it is faster then jikes! - compiled with gcj to a native binary of course). What I ended up doing was making an empty java project and then creating a directory structure in it with symlinks to the java files in my classpath source and object directory. It works and the eclipse java compiler points out some errors/warnings that weren't showing with jikes or gcj. It is also nice for cleaning up import statements. But far to slow under gij for such a big project (but the positive news is that it does work). We really have to get a native gcj compiled 3.0 working (just haven't tried since I still have some troubles with the interpreted one, see the gcj mailinglist). More positive news: gij + Eclipse 3.0 M4 + java-gnome bindings + gnome plugin wizard seem to work quite nicely. More info (and screenshots!) when I have better internet access. Cheers, Mark ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Q: Classpath and Eclipse
Has anybody already tried to import classpath under Eclipse? I tried to create a project and import the files, but then Eclipse is far too intelligent: * gnu/java/lang classes are imported into package java.lang * vm/reference/java/lang classes are imported into package vm.java.lang Probably I'm just doing something wrong (I'm using Eclipse 3.0M4) Never tried it. Most IDEs do not expect people to try to work on core java, especially not a different core java. Even so, there's nothing stopping you from configuring Eclipse to do so. The main areas you will need to configure are: - project properties - Java Build Class Path - Source Remove the autodetected source paths and add the project root as one. - Run - Run As - New Application (make sure you have your test app's main class open in the editor) gives you options to override the bootclasspath and other sundry items. I develop fbAWT under Eclipse 3.0M4 without problem. I use classpath's java.awt.Font* classes as they don't initialise native libs ;) Cheers, Stephane ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Q: Classpath and Eclipse
Julian Dolby knows more about this (maybe he will jump in), but when you run eclipse on Jikes RVM we've written a plugin such that the classpath libraries are not only used by eclipse, but are also used by the applications you develop in eclipse (and Jikes RVM is used to execute them). So, you can edit, build, compile, and run your Java code in Eclipse without needing any other JVM at all. One downside is that we haven't implemented JDWP in Jikes RVM yet, so you can't use the Eclipse debugger in this mode, but we all write bug free programs the first time, right ;-) We also have mainly been testing this on the 2.x versions of eclipse. I'm pretty sure we have a little work to do to get the current Eclipse milestone builds to work on Jikes RVM. --dave___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Q: Classpath and Eclipse
Patrik == Patrik Reali [EMAIL PROTECTED] writes: Patrik Has anybody already tried to import classpath under Eclipse? FWIW, I wouldn't object to someone checking in an eclipse .project file (and other stuff) into classpath, provided it didn't rely on anything site-specific. Tom ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Q: Classpath and Eclipse
Patrik Reali [EMAIL PROTECTED] writes: Hi! Has anybody already tried to import classpath under Eclipse? I tried to create a project and import the files, but then Eclipse is far too intelligent: * gnu/java/lang classes are imported into package java.lang * vm/reference/java/lang classes are imported into package vm.java.lang Probably I'm just doing something wrong (I'm using Eclipse 3.0M4) Never tried it. Most IDEs do not expect people to try to work on core java, especially not a different core java. Brian -- Brian Jones [EMAIL PROTECTED] ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
