>> I know the issue of Eclipse working with GNU Classpath has mentioned >> several times on the mailing list in the past. Can anyone give me a >> status update, especially as regards the 3.x series?
Mark> Not much has changed since 0.10 when we could startup 3.0 but not do Mark> much else (basically the java editor view is broken which makes most of Mark> the IDE a bit useless). I've been running Eclipse as a test case for the binary compatibility work in gcj (and also the upcoming GCC 4.0 release). I ran into this bug too and I fixed it this weekend. Try again with the BreakIterator patch I committed today, the JDT editor should work now. Mark> PATH=.:$PATH ./eclipse -vm jamvm -debug -consoleLog -vmargs -ms256M -mx256M \ Mark> -bootclasspath/p ~/xalan/bin/xml-apis.jar:~/xalan/bin/xercesImpl.jar:~/xalan/bin/xalan.jar \ Mark> -Dosgi.locking=none For newer versions of Eclipse you need -Dorg.eclipse.core.runtime.ignoreLockFile=true instead. I read that on this list a while back, apologies since I forgot who discovered this. There's a couple other minor tweaks you need to make it work with gij, I'll post to the gcj list. Mark> For 0.12 I want to at least move GNU JAXP in again in the external Mark> directory. Maybe it can become a regular part of GNU Classpath, we would Mark> need to discuss that with Chris and Arnaud. IMO Classpath should have as much of J2SE as possible, including tools and everything else. It is simply more convenient if it is all in one repository. For JAXP in particular it would be nice to find out why Eclipse doesn't work with it before checking it in... Tom _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
