David Corbin wrote: > Actually, I want ALL the generated classes (not just interfaces) in > special packages.
You can use the <packagesubstitution> subelement for this. http://xdoclet.sourceforge.net/ant/xdoclet/tagshandler/PackageTagsHandle r.PackageSubstitution.html For example, you could use it to separate each of the artifacts by type. bean -- Abstract bean classes (source code) home interface cmp session util IIRC, each subtask takes the <ps> element. > Well, what I want is the other directory > option, but I have to convince my teammates first. Here are two useful starting points. * Do not put build artifacts into the source code repository. Tracking their versions doesn't add any value as you can always recreate any version from the source. If you cannot do that, your build system needs attention. * Do not mix build artifacts with source files. Mixing them makes cleaning the build environment more difficult. Keeping them separate allows simpler build scripts: <target name="clean-gen" description="Remove all generated source files"> <delete dir="${gen.dir}" quiet="true"/> </target> You can still easily include files from both sets for other tasks such as <javadoc> or further <ejbdoclet>ing. Ask them why they prefer the all-in-one approach? Is it difficult to setup their IDEs to have multiple source directories for name completion? Do they want to add the artifacts in the repository? Or is it simply a matter of momentum/habit? In general, I've never regretted having too much meta-information -- only lacking it. :) Peace -- David Harkness Sr. Software Engineer Sony Pictures Digital Networks (310) 482-4756 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
