Community
Participate
Working Groups
Build ID: I20081211-1908 Steps To Reproduce: hi, colleagues: I met quite a few of error info like "Project is missing required library ..." and "Build Path contains duplicate entry ..." when I run Eclipse (EUT) on top of Harmony (http://harmony.apache.org), particularly when org.eclipse.jdt.core.builder.TestingEnvironment.addExternaljars(projectPath, Util.getJavaClassLibs()) which adding the bootclasspaths of a JVM to the class path of a project. Investigating the codebase I think that the classpath checking rules inside org.eclipse.jdt.internal.core.JavaProject.setRawClasspath() are arguable. More information: For example: (1) "Project is missing required library .\deploy\jdk\jre\lib\boot\xalan-j_2.7.0\serializer.jar". Note: the name serializer.jar is extracted from the Class-Path info in the Manifest of xalan.jar, which is an entry of Harmony's bootclasspath. But actually serializer.jar is not used, so it is not in the JVM¡¯s default release. Question: is it possible for Eclipse to ignore the non-existing JAR file, from the Class-Path attributes? (2) "Build Path contains duplicate entry: ...\xml-apis.jar". Note: the duplication is resulted because the first occurrence (of xml-apis.jar) extracted by Eclipse from the Class-Path info in the Manifest of the xalan.jar, which is set in bootclasspath of Harmony, while the second occurrence (of xml-apis.jar) is directly read from the (later entry of)bootclasspath. In my understanding this rule limits the order of the bootclasspath or other adding classpath-list if the entries are refered each other by the Class-path info. Question: is it possible for Eclipse to extract the Class-Path info (in the Manifest) after adding all of the Classpath list items?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
