Well, I also thought that as best strategy, not putting these intermediate files into CVS. But we dont have a homogen development environment here, some guys want to use JBuilders fancy GUI to generate interfaces and deployment descriptors, and we want to use only XDcolet and Ant (and preferably Eclipse with them). So, JBuilder wants the interfaces and deployment descriptors in the repository, Xdoclet doesnt need them and doesnt like them to be in repository. I wish I could enforce everybody to use Xdoclet.
Is it very difficult to add Xdoclet ant task asome functionality to check whether the generated code's content and existing codes content are same? Or should I open a bug report?
regards.
Mehmet D. AKIN penned
We are using CVS . Whenever someone generates and commits an Xdoclet
generated file, [...]
I highly recommend leaving all build artifacts (tool generated files) out of CVS. If you want to publish JAR/WAR snapshots, stick 'em on file servers. Since you can always generate them for any point in the source tree, there's no reason to keep them around or make your repository do useless work. And I expect Eclipse can generate them as part of the build process.
Doing this will spare you many headaches like your current situation to boot. :)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
