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

Reply via email to