On Windows, shader compilation fails if we set caps.setStencilBits(8). Setting caps.setSampleBuffers(true) fixes the problem, as does removing the stencil bit setting. Created unit test, confirmed failure on Windows and pass on Linux. Submitting pull request for unit test soon, after preliminary debugging.
Submitted pull request for failing JUnit test case at https://github.com/sgothel/jogl/pull/19. The original report of this bug was on the forum at http://jogamp.762907.n3.nabble.com/JOGL2-GLCapabilities-Windows-td2153961.html. The problem seems to be in the capabilities choosing code, so I'll wait for your next checkin before digging in too deep.
merged test, fixed by GLCapabilities change 8adc04788a6d9dd44de5a4636b46d14dbb70b799 test passed in 280
still exists on NV/Win7 .. fixing now
commit e2040ada5a94b466ba95e84a497290c069d377bb Author: Sven Gothel <sgothel@jausoft.com> Date: Sat Feb 5 04:03:51 2011 +0100 Fix bug #459 NV/Win7 PDF/caps selection Scenario - NV / Win7 driver version 266.58's - Caps: on-scr, rgba 8/8/8/0, accum-rgba 0/0/0/0, dp/st/ms: 16/8/0, dbl, mono The above 'wglChoosePixelFormatARB' impl returns an array of pixelformats, where the 1st entry is not hardware accelerated! This should be considered a bug in NV's driver, since the array should return a list ordered from 'best' to 'worst'. Workaround trying explicit hw acceleration 1st, then generic, then software.