I agree. I don't know why they are included. The jar files aren't in SVN. If it's a source distribution, shouldn't it just be exactly what's in SVN (a fresh checkout)? It looks like it's using an older version of the build.xml file, or the artifacts are still hanging around (the directory isn't deleted each time). The old build.xml used to download the jar files into lib/runtime and lib/build, but the new one is generated from Maven, so all of that stuff should go into target/lib.
-----Original Message----- From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Saturday, January 28, 2006 1:12 PM To: Jakarta Commons Developers List Subject: Re: [proxy] Nightly Builds... On 1/28/06, James Carman <[EMAIL PROTECTED]> wrote: > All, > > The nightly source code build distributions for Proxy include its > dependencies. I am not sure, but I don't think we're supposed to do that, > are we? <snip/> While I'm unaware of the specifics of [proxy] (is there any particular reason for doing this?), it usually shouldn't be necessary for Commons components. -Rahul > Isn't there some sort of license restriction? > > James > --------------------------------------------------------------------- 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]
