Hi Liviu,
Liviu Vasut wrote:
>> Hmmm. What's the output of:
>>
>> java -version
>>
>> I've tested with Java 1.6.0_29 and now also with Java 1.7.0_01. Works for
>> me. I case you've used plain Java 1.7.0, can you update to the latest
>> Java
>> 1.7.0_01?
>
> I was already using it and even made a reinstall, but the exception is
> still there:
> java -version
> java version "1.7.0_01"
> Java(TM) SE Runtime Environment (build 1.7.0_01-b08)
> Java HotSpot(TM) Client VM (build 21.1-b02, mixed mode, sharing)
>
>
> I also ran the test on my home computer, running linux, and it came out
> just fine.
Phew, some light ;-)
> java version "1.6.0_22"
> OpenJDK Runtime Environment (IcedTea6 1.10.4)
> (ArchLinux-6.b22_1.10.4-1-i686)
> OpenJDK Client VM (build 19.0-b09, mixed mode)
>
>
> The question is (let's say I work on another system and finish my
> application)
> If I release it to users is there any chance this problem would appear
> somewhere?
Actually, I don't think it's the Java application itself. However, I am too
long gone from the Windows shell to remember every detail. The point is that
for some reason the provided classpath seems not to work. You're running the
command from a Windows shell? Or did you try it from a Cygwin bash? Did you
try to quote the classpath option?
- Jörg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
