Changes to pretty.settings does affect the "to-beautify-or-not-beatify" logic. So if a file is not modified it shouldn't be touched by <pretty/>. And I don't have this problem, on win2k and winxp with jdk1.3.1. Maybe the way you checked out from cvs is different? And that leads to timestamp in cvs control files which are differnt from mine?
Ara. --- Andrew Stevens <[EMAIL PROTECTED]> wrote: > The jar seems okay now, but if I fetch a clean copy from CVS and > build it > without changing anything there's a bunch of source files that then > show > up as locally modified. > > It looks like the changes are due to the pretty.settings file that > got > updated a few days ago along with the prettyprinter repackaging, in > particular the stuff at the end to do with the ordering of fields, > methods, etc. Before I start checking stuff in to clean up some of > the > javadoc warnings, I thought I'd better make sure this was intentional > > (particularly since it causes a whole load more javadoc warnings by > adding > empty @return tags etc. all over the place). > > It makes spotting my changes in the diff quite challenging, but I > wouldn't > want to try checking them in without doing a build first to make sure > > they're okay... > > > Andrew. > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel __________________________________________________ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
