Comments on: How to Tell Where Eclipse Finds a Class? http://www.elharo.com/blog/software-development/java/2009/01/03/how-to-tell-where-eclipse-finds-a-class/ Ranting and Raving Mon, 30 Aug 2010 19:51:26 -0500 http://wordpress.org/?v=2.9.1 hourly 1 By: Lorenzo Gatti http://www.elharo.com/blog/software-development/java/2009/01/03/how-to-tell-where-eclipse-finds-a-class/comment-page-1/#comment-622174 Lorenzo Gatti Sun, 04 Jan 2009 14:48:43 +0000 http://www.elharo.com/blog/?p=1001934#comment-622174 If there are multiple copies of one class in the workspace, Open Type (Ctrl-T) shows all of them with their location, which is only a partial clarification. It happens to me all the time because I access many projects both as sources for modification and as read-only JARs (not as project dependencies) from other projects. I'd rather recommend Open Declaration (F3) and related commands, since they respect the imports of the source file you start from and the classpath of the enclosing project. However, there is no direct relationship between Eclipse's model and the runtime classpath of your tests; XML-related libraries, with their balkanized JARs, obsolete packages, multiple versions and complicated loading mechanisms, are a common source of race conditions (the class that is loaded first determines subsequent classloading). If there are multiple copies of one class in the workspace, Open Type (Ctrl-T) shows all of them with their location, which is only a partial clarification. It happens to me all the time because I access many projects both as sources for modification and as read-only JARs (not as project dependencies) from other projects.

I’d rather recommend Open Declaration (F3) and related commands, since they respect the imports of the source file you start from and the classpath of the enclosing project.

However, there is no direct relationship between Eclipse’s model and the runtime classpath of your tests; XML-related libraries, with their balkanized JARs, obsolete packages, multiple versions and complicated loading mechanisms, are a common source of race conditions (the class that is loaded first determines subsequent classloading).

]]> By: Elliotte Rusty Harold http://www.elharo.com/blog/software-development/java/2009/01/03/how-to-tell-where-eclipse-finds-a-class/comment-page-1/#comment-622167 Elliotte Rusty Harold Sun, 04 Jan 2009 14:33:02 +0000 http://www.elharo.com/blog/?p=1001934#comment-622167 Thanks. That did the trick. Looks like it's coming from the Java 1.4.2 class libraries. Now the next question is how those are ending up in my classpath, and how this only happens for some of the unit tests but not others. Still digging... Thanks. That did the trick. Looks like it’s coming from the Java 1.4.2 class libraries. Now the next question is how those are ending up in my classpath, and how this only happens for some of the unit tests but not others. Still digging…

]]> By: Luís Miranda http://www.elharo.com/blog/software-development/java/2009/01/03/how-to-tell-where-eclipse-finds-a-class/comment-page-1/#comment-622148 Luís Miranda Sun, 04 Jan 2009 12:56:07 +0000 http://www.elharo.com/blog/?p=1001934#comment-622148 Try this: highlight the class name, then select <i>Open Type</i> from the <i>Navigate</i> menu. When you select a class name from the list, the JAR / source directory is displayed near the bottom of the <i>Open Type</i> dialogue. Try this: highlight the class name, then select Open Type from the Navigate menu. When you select a class name from the list, the JAR / source directory is displayed near the bottom of the Open Type dialogue.

]]>