Community
Participate
Working Groups
Build Identifier: 20100917-0705 Utility Jar projects when added to an EJB 2.1 Project via the Deployment Assembly --> Manifest Entries tab are being picked up when XDoclet runs as client jar projects. The XDoclet Ant task as a result adds ejb.client.module.src parameter to the generated build.properties file which in turn causes the subtask declared in the generated file tempAnt.xml for client jars to be run. This does not occur in Eclipse 3.4.2 Reproducible: Always Steps to Reproduce: 1. setup xdoclet runtime and turn off the xdoclet builder (window > preferences) 2. create an ejb 2.1 project with an xdoclet annotated session bean 3. create a utility jar project 4. create an enterprise application project and make sure to add both the enterprise bean project and the utility jar project as module dependencies 5. create a class that is used by the session bean in the utility jar project 6. in the deployment assembly page for the ejb project, manifest entries tab add the utility jar project 7. use the utility jar class in the session bean 8. clean build 9. right click on the ejb project and run xdoclet
Adam, thank you for reporting this bug. Unfortunately, there is currently no committer to maintain the XDoclet functionality in WTP. Therefore, I cannot predict when this bug could be fixed. We will appreciate if you, or someone else, can work on a patch.
I am closing all tickets related to XDoclet as WON'T FIX, because there is no committer to support this functionality. I can review patches if anyone is willing to contribute.