All, > I personally don't think that generated html in /www/, which is there to > allow controlled website updates not to version the docs themselves which > are versioned in /src/, nedds to have this as strictly enforced as > elsewhere, IMO it takes effort for no appreciable benefit. > > Thoughts?
I have to disagree. First off, I'm going to comment that I very much hope the www directory goes the way of the dodo early in the 3.0 cycle. The presence of this directory violates one of the basic tenets of good build design. Specifically, that running the build (with no source code changes) should not introduce any diffs with the source control tree. In other words, the build operation itself should be idempotent. To see that this isn't true, do the following: 1) Check out a new Jakarta-james tree 2) Run 'build website' 3) Diff the tree - you'll see every javadoc file is changed. <shudder> Add to this that specific changes in the src/java directory (additions, deletions) have to be manually carried over to the www directory and it is obvious that the current process is fragile and should be changed. (Note, for example, that the "fetchpop" classes weren't added until yesterday). We've discussed all this on the list before, so I'll let it go at that. That all said, if the www stuff (and most importantly the javadocs and mailet API docs) are going to be in source control for the moment, it's important to minimize the diffs so that one can discern actual issues among all the noise. After I did my largest recent check-in on the javadocs directory I was able to find several issues in the Javadocs precisely because not every line contributed to the diff. So standardization on LF served a very useful purpose, as well as being a really easy change to make. --Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
