Comments on: Eclipse Classpath Insanity http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/ Longer than a blog; shorter than a book Tue, 09 Mar 2010 18:31:23 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Car http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-138189 Car Mon, 08 Oct 2007 03:43:15 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-138189 Does anyone know where I can get my hands on Eclipse 3.1? eclipse.org seem to have removed all the older versions for download! Does anyone know where I can get my hands on Eclipse 3.1? eclipse.org seem to have removed all the older versions for download!

]]> By: Bas Leijdekkers http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-90784 Bas Leijdekkers Thu, 17 May 2007 17:37:07 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-90784 My guess is Eclipse throws a StackOverflowError on the kind of pathological <code>decompose(int)</code> method. It probably uses a recursive descent parser which cannot cope with the deep stacks the gigantic if-else-if would generate. This does not mean compiler/analyzer is weak. Try to compile the class like this: "<code>javac -J-ss512k UnicodeUtil.java</code>". It will fail with a StackOverflowError. Javac probably has a stack size of about 1024k by default to cope with this kind of code. Thus increasing the default stack size of Eclipse, any other IDE, compiler or analyzer should help. Rewriting the decompose method to use a switch statement or a prepopulated lookup map would help more. My guess is Eclipse throws a StackOverflowError on the kind of pathological decompose(int) method. It probably uses a recursive descent parser which cannot cope with the deep stacks the gigantic if-else-if would generate. This does not mean compiler/analyzer is weak.
Try to compile the class like this: “javac -J-ss512k UnicodeUtil.java“. It will fail with a StackOverflowError. Javac probably has a stack size of about 1024k by default to cope with this kind of code. Thus increasing the default stack size of Eclipse, any other IDE, compiler or analyzer should help. Rewriting the decompose method to use a switch statement or a prepopulated lookup map would help more.

]]> By: hatbox http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-42992 hatbox Thu, 28 Dec 2006 12:38:21 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-42992 Marvelous. Thanks, will spread this among my friends! Marvelous. Thanks, will spread this among my friends!

]]> By: theOlster http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-37285 theOlster Thu, 14 Dec 2006 11:54:30 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-37285 Does anyone know where I can get my hands on Eclipse 3.1? eclipse.org seem to have removed all the older versions for download! Does anyone know where I can get my hands on Eclipse 3.1? eclipse.org seem to have removed all the older versions for download!

]]> By: AudioTraffic-- theOlster.net http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-37282 AudioTraffic-- theOlster.net Thu, 14 Dec 2006 11:42:21 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-37282 [...] I seem to be having the same problems as here and will now try Eclipse 3.1 - wish me luck! [...] [...] I seem to be having the same problems as here and will now try Eclipse 3.1 – wish me luck! [...]

]]> By: Elliotte Rusty Harold http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-21604 Elliotte Rusty Harold Tue, 10 Oct 2006 01:17:56 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-21604 You means something like " This entry was posted on Wednesday, August 16th, 2006 at 7:56 am and is filed under Java.", maybe conveniently placed at the bottom of each entry? I don't know. Seems a little radical. :-) You means something like ” This entry was posted on Wednesday, August 16th, 2006 at 7:56 am and is filed under Java.”, maybe conveniently placed at the bottom of each entry? I don’t know. Seems a little radical. :-)

]]> By: George Bailey http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-21519 George Bailey Mon, 09 Oct 2006 15:30:52 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-21519 Would you consider putting dates on your entries? In this case it's not hard to figure out because the comments are dated, but as they age and come up in searches it'd be nice to know when it was written. Would you consider putting dates on your entries? In this case it’s not hard to figure out because the comments are dated, but as they age and come up in searches it’d be nice to know when it was written.

]]> By: john brown http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-12237 john brown Fri, 25 Aug 2006 01:34:03 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-12237 Eclipse 3.2 is definitely NOT ready for production use (unless you are on someone else's payroll and do not have deadlines) At startup the "Initializing Java Tool" hangs the IDE, it takes forever to start and publish to Tomcat 5 (look like the IDE is hung), the Project pane incorrectly identifies packages with errors with a red X, and many many more bugs. I've wasted the last 3 weeks with eclipse 3.2 and WTP 1.5 and have opened a bug on bugzilla. Sticking with Websphere Site Studio Developer 5.1.2 (Yes its the old eclipse 2.1) which works reliably for me. I appreciate the progress on eclipse 3.2 made by the various developers. I will give eclipse 3.2 a shot later in the year as the stable 3.2 release looks like it needs a lot of cleanup. It appears that eclipse 3.0.1 is still the stable reliable version of eclipse. Eclipse 3.2 is definitely NOT ready for production use (unless you are on someone else’s payroll and do not have deadlines)

At startup the “Initializing Java Tool” hangs the IDE, it takes forever to start and publish to Tomcat 5 (look like the IDE is hung), the Project pane incorrectly identifies packages with errors with a red X, and many many more bugs.

I’ve wasted the last 3 weeks with eclipse 3.2 and WTP 1.5 and have opened a bug on bugzilla. Sticking with Websphere Site Studio Developer 5.1.2 (Yes its the old eclipse 2.1) which works reliably for me.

I appreciate the progress on eclipse 3.2 made by the various developers. I will give eclipse 3.2 a shot later in the year as the stable 3.2 release looks like it needs a lot of cleanup.

It appears that eclipse 3.0.1 is still the stable reliable version of eclipse.

]]> By: Roman Strobl http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-11500 Roman Strobl Sun, 20 Aug 2006 19:48:55 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-11500 Hi, if you'll give NetBeans another try we'd like to know from you what was your experience. Even if you decide to stick with another IDE it's for us interesting to get feedback, we're preparing future roadmap of NetBeans - so that next time you'll try NetBeans, you won't want anything else :) Hi, if you’ll give NetBeans another try we’d like to know from you what was your experience. Even if you decide to stick with another IDE it’s for us interesting to get feedback, we’re preparing future roadmap of NetBeans – so that next time you’ll try NetBeans, you won’t want anything else :)

]]> By: Marco http://cafe.elharo.com/blogroll/eclipse-classpath-insanity/comment-page-1/#comment-11037 Marco Fri, 18 Aug 2006 18:27:53 +0000 http://cafe.elharo.com/java/eclipse-classpath-insanity/#comment-11037 Jan may be right about retreating from 3.2 to 3.1. After rockin' & rollin' with many previous versions of Eclipse, my experience with 3.2 has been less than stellar. Too easy to hang up the IDE. Jan may be right about retreating from 3.2 to 3.1. After rockin’ & rollin’ with many previous versions of Eclipse, my experience with 3.2 has been less than stellar. Too easy to hang up the IDE.

]]>