Riyad,
I am aware of the property settings you mention, but I think you may be missing the problem I am having. Allow me to try and explain more clearly- I have a project which requires that I generate classes using an ant task (xmlBeans). The output folder for the generated classes is a “class folder”. I have my build path defined such that the class folder is visible within the project. I have also modified the deployments tab to require all dependent projects to be “jar’d” and placed in the WEB-INF/lib directory. During the deployment step, the xmlbean generated classes are not included as part of the exported jar. However, all of the normal classes generated using eclipse build are exported.
It would seem that the deployment does not honor the “class folder” as being part of the project. Oddly, all dependent external jar files from the build path are being included as part of the deployment, so one would think that if it does not include as part of the base project jar it would at least create a jar as if it were external.