- This topic has 3 replies, 2 voices, and was last updated 18 years ago by
.
-
Posts
-
Hello,
I have a web project which references a class library via the “build path->libraries->add class library” settting. For compilation the class library is visible, but during deployment the required classes are not included in the WEB-INF/classes folder. As I workaround, I am forced to export a jar file and include this as part of the build path and subsequently it is placed in the WEB-INF/lib folder, but I am hoping to use a more dynamic approach. I would imagine this is a common and simple fix, but my searches have not revealed the solution; any advice is appreciated.
Thanks
ChrisChris,
If you go to the MyEclipse preference panel under your project properties, then go to the Deployment tab. You can set the deployment rules for libraries on your build path, that should help.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.
