Mikhail, The reason is as follows. The launcher uses InvocationAPI to start VM. The spec doesn't require to provide java.class.path property. The worst thing which should happen in this case is ClassNotFound exception on attempt to load a class. So I think we have two choices either use current directory to load classes or use empty path. In the second case the search path is boot class path only. Personally I think that second is acceptable as well.
Evgueni On 10/10/06, Mikhail Fursov <[EMAIL PROTECTED]> wrote:
Evgueni, You wrote about the launcher: "As a part of its job it sets up java.class.path property." So if it is the part of it's job and the property is not set that means that this is the bug.(?) What is the reason of workarounding this bug in VM code? Are there additional usecases? -- Mikhail Fursov
--------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
