Here's another option for you.
I've just checked in an update that should log a warning in server.log during deployment if GlassFish discovers a JAR file with no manifest. The error will report the JAR file for which no manifest was found and will continue with the deployment.
The change should appear in the next nightly build, so if you want to you can download the nightly build from tonight and try your deployment with that build. Even if you don't want to use the nightly for your real deployment, this would at least help you identify which JAR is missing a manifest.
- Tim
[Message sent by forum member 'tjquinn' (timothy.quinn_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=379813