Sorry, the last msg was a little confusing... There isn't a core ant task that will do subversion pulls, although there are ways to do it (antsvntask, others?)..so we could update the script to use one of these svn tasks, and maybe get it to work..
re: CVSGrab - we are still using viewCVS to display the repositories, so it may be possible to get CVSGrab to work with the new repositories, but I haven't done it myself, so I'm not sure... Scott -----Original Message----- From: Scott Deboy [mailto:[EMAIL PROTECTED] Sent: Tue 10/18/2005 8:19 PM To: Log4J Developers List Subject: RE: 1.3 alpha 7 build The logging projects are now using subversion, and I don't think there's a 'cvsgrab' for subversion, so the best the script could do is download ORO (and VFS if we updated it, now that VFS out of the jakarta commons sandbox). install-chainsaw.xml is messed up in the alpha7 build (there's an install-chainsaw.html in the docs directory, where install-chainsaw.xml should be , but that's not it)... Anyway, it's a bit of a moot point now that we're on subversion. There's still the bundle tarball available from the Chainsaw page, which is a handy way to get the source/binaries.. Scott -----Original Message----- From: Gary Gregory [mailto:[EMAIL PROTECTED] Sent: Tue 10/18/2005 4:51 PM To: Log4J Developers List Subject: RE: 1.3 alpha 7 build The ZIP file does not include the chainsaw jar file. Is this on purpose? There is no install-chainsaw.xml either. Thanks, Gary > -----Original Message----- > From: Mark Womack [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 12, 2005 9:15 PM > To: Log4J Developers List > Subject: 1.3 alpha 7 build > > As promised, here is the 1.3 alpha 7 build. > > I think I tagged everything the right way for svn. I don't see a commit > message for my change to the HISTORY.txt file though (to set the release > date). > > Anyway, you can find the images at: > > http://cvs.apache.org/builds/logging/log4j/log4j-1.3a7/ > > Take a look and we can vote for a release if things look good. > > Some notes: > > - The main trunk requires jdk 1.4 to build right now. So, the > controversial > 1.2/1.3 compatibility is moot at this point. We will need to review the > issues and decide how to resolve. But right now it is good enough for an > alpha release, imo. > > - I did not build with the slf4j beta 4 jar. We need to decide how we are > going to move forward with slf4j support and we need to upgrade to the > latest slf4j version once we decide. > > I am going to do the 1.2.13 build tomorrow night. I'm out of time > tonight. > > -Mark > > > > --------------------------------------------------------------------- > 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]
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
