[windup-dev] Windows Issues

[Brad Davis]

I think we could maybe create the decompiler as a runnable, and interrupt the thread with a timeout if the decompiler takes more than a minute for a class, which should be plenty of time.  We should log this, though, to make sure they are aware that one of the classes did not successfully decompile.

Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com 


----- Original Message -----
From: "Ondrej Zizka" <ozizka at redhat.com>
To: "Windup-dev List" <windup-dev at lists.jboss.org>
Sent: Tuesday, October 14, 2014 11:55:17 AM
Subject: [windup-dev] Windows Issues

Hi, 

I've tried on Windows 7 64bit, Oracle JDK 1.7.0_67. 

The tests fail with WINDUP-335 and WINDUP-332 . 
The run against Tim's EAR get stuck on Decompilation for about 8 hours, seems it's in an endless loop. WINDUP-337 


Is Windows a priority? Do we have estimation on what portion of users will run on Windows? 

Ondra 



_______________________________________________
windup-dev mailing list
windup-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev