In a EAR project, I have an app client which I cannot debug by clicking on "debug".

1) App client libraries are not found while debugging. I need to copy them to the ear project for it to work in debug mode.
2) While launching "debug" target on ear project, it asks me if glassfish is running in debug mode. If I say "yes", it
stops. So, I always say "no". It works anyway, even if running in debug mode. Found some information about that,
basically the reason for asking the question. It still looks like a bug.
3) Step 2 only allows to debug the client code. To debug the EJB module which is also part of the application, I need to
run glassfish in debug mode, and attach to the process (jpda). It then works (can set breakpoints, inspect, recompile, ...).

I think this is a real pain. It definitely needs to work better. While in a ear project, I'd expect just hitting the
"debug" button to debug the app client and ejb modules. It would restart glassfish in debug mode, attach, ... if needed.
I shouldn't have to add the client libs to the ear package, as I don't need to do that to run the client.