I'm pretty sure that I did not update to the latest site contents before doing the a8 build. Oversight on my part. If that makes a concrete difference, then we should -1 and do it again.
(Have I mentioned that I really dislike having a dependency on a separate repo?) -Mark On 2/1/06, Mark Womack <[EMAIL PROTECTED]> wrote: > Not sure what you are looking at to determine ant version. If I look > at the jar files in the dist image, the manifest clearly says it was > built with ant 1.6.5. > > I re-copied the alpha8 tag after applying all of the latest build/test > related changes in the log4j repo. I have not applied any changes or > tags to the site repo, so I am guessing that is what you are talking > about here. I can make a tag (somehow as you describe). There will > be another tag in site for the actual changes for the 1.3a8 dist > release (updating download.xml, other 1.3a8 info, etc). > > -Mark > > On 1/31/06, Curt Arnold <[EMAIL PROTECTED]> wrote: > > > > On Jan 31, 2006, at 3:16 PM, Mark Womack wrote: > > > > > http://cvs.apache.org/builds/logging/log4j/log4j-1.3a8 > > > > > > I'd like to move on this. I won't be available Thursday or Friday to > > > push the release to dist. > > > > > > +1 > > > > Was able to reproduce build (other than expected Javadoc > > timestamps). Looks like your still using Ant 1.6.4, but not a big deal. > > > > However, the alpha8 tag needs to be updated since the distribution > > was built off the current trunk and not off the tag. Do the tag > > update before committing any changes to downloads.xml, etc (or > > specify a revision when copying to the tag) to make sure the tag and > > the distribution are in sync. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
