chunrong lai wrote:
Just want to check if we need more careful consideration when adding
(open) jars into the bootclasspath, as RI just includes self-make jars in
their bootclasspath.
The open jars (currently, xalan and yoko) may include "Class-Path" (main)
attribute. Which stands for "The value of this attribute specifies the
relative URLs of the extensions or libraries that this application or
extension needs. URLs are separated by one or more spaces. The application
or extension class loader uses the value of this attribute to construct its
internal search path. " according to the JAR file Specification (
http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html). I am not sure it is
satisfied currently. It is also noted that Eclipse Unit Test will
extract/examine the Class-Path attributes of bootclasspath of the used VM
and reported error info of "Missed Project Entry" or "Duplicate Project
Entry" when some exceptions are observed.
Personally I think that it is OK to just remove the "Class-Path"
attributes of the new bootclasspath jars. What is the opinion?
On Fri, Feb 27, 2009 at 4:55 PM, Tony Wu <[email protected]> wrote:
patch integrated at r748435, thanks Mark and Jimmy.
On Fri, Feb 27, 2009 at 4:48 PM, Jimmy,Jing Lv <[email protected]> wrote:
Hi,
+1
It seems a patch that update the bootclasspath property (odd that
mistake exists!) and should be fine to commit.
2009/2/27 Tony Wu <[email protected]>:
Hi, all
This is a bug making the CORBA feature unavailable in HDK. I'm here
asking for your agreement since the code repos is freezed.
https://issues.apache.org/jira/browse/HARMONY-6102
--
Tony Wu
China Software Development Lab, IBM
--
Best Regards!
Jimmy, Jing Lv
China Software Development Lab, IBM
--
Tony Wu
China Software Development Lab, IBM
If the Class-Path entries are not used by Harmony, I think it's safe to
remove them. I'll prepare patch to remove them from yoko like r749061
did.
--
Best Regards,
Regis.
