We are working on the GWT/CDI integration. If an application packages GWT client classes that depend on gwt-user.jar and the weld deployer kicks in it chokes in classes that import GWT client API. This happens because the usage of reflection to scan for annotation meta data, loads all classes and forces all dependencies to be present.

These classes can be excluded from the web application packaging, but it's nothing people usally do,
because they are required when running the GWT hosted mode.

So in order to simplify things, I would suggest we simply log and skip classes that cannot be scanned due to CNFE and the like, instead of preventing the deployment at all.