JOGL integration with netbeans 7 after update [solved]

dear community

i have face a little problem when updating to netbeans 7
and would like to share my solution as it was hard to track

here it is, i update my NBP suite using jogl 1.1.1 to  nebeans 7
it works with minor changes
but at some point, i clean and rebuild everything and jogl stops to work :

the GLCanvas (or GLJPanel) only shows a black screen with written in the middle "glcanvas" or "gljpanel"

the init(GLDrawable...) never gets called, and nothing else happens

after trying many solution, including trying JOGL 2, updating all my libraries...
creating a small minimal module inside my main project to test jogl independanlty
no success

passing to jogl 2 with GLCanvas get me an error with some AWT thing not supported when the glcanvas is added to the Topcompenent
i couldnt find any thing on the net for that

but then creating a new suite, with one single jogl 2 module inside, and it works

so i start to figure there is some library that i was including in my mproject, that interferes

go to the main project libraries
remove everything except Platform libraries
then click to resolve some libraries  missing

clean build run, and tada
it works

the interferring library is somewhere in
apisupport
harness
ide
jave

but i wont spent time now trying to figure what it was

hopes this helps anyone facing some weird problems with jogl and netbeans upgrade

many thanks to all the developpers by the way
it is a very nice api, and helps me a lot in my work

thanks

Philippe

Hi Philippe,

Thanks for sharing the solution to your problem! I can't seem to duplicate it, though

When I take the simple JOGL 2 example at https://jogamp.org/wiki/index.php/Using_JOGL_in_AWT_SWT_and_Swing, and set it up in NetBeans as shown at https://jogamp.org/wiki/index.php/Setting_up_a_JogAmp_project_in_your_favorite_IDE, it seems to work fine in NetBeans 7. I updated my NetBeans version this morning to make sure.

I ran my test on Windows 7 64-bit -- what platform are you running on? Maybe there's a platform-specific or project-specific problem.