On Sun, 2007-01-07 at 17:08 +0000, Joerg Heinicke wrote: > Martin Cooper <martinc <at> apache.org> writes: > > > > In general I don't like the need for internet access on build time. > > > > This is a red herring. One way or another, you're going to have to get the > > jars from the network, whether it's getting them from SVN, or having Maven > > or Ant retrieve them. And in all of those three cases, once you have them on > > your local machine, you don't need the network to build the next time. > > There is one big difference: With everything in the src jar or at least in the > svn checkout your requirements are less sophisticated than with the build > system. For src jar I only need a browser, for svn checkout I need a svn > client, > but for Ant and Maven I need additionally Java and the build environment > itself. > And this is a big difference if the machine with internet access is not your > local machine.
I've got no objection to commons-transaction providing a custom download, eg "commons-transactions-6.7-src-all.tgz" which contains jars if you feel this would make users happy. However no other commons project has done this AFAIK, and I don't see any complaints on the user lists. When using maven, only the first run needs to download the jars; thereafter they are cached locally. So, no need for "internet access at build time". For ant, have a look at the build.xml file in logging that I provided a link to; it defines a separate "getlibs" task to download the jars. This can be run *once* to download the jars, but is not part of the main build task, so there is no need for "internet access at build time". Re your maven issues: it's not mandatory to use maven to create builds; ant is fine. Providing both is even better. It's only the jars issue that is being discussed. > (I speak from experience. In my company I get access to the internet only via > a > terminal server. There is no build environment. For proposed changes in the > build I need to download all dependencies by hand.) A poor corporate internet access policy at one company is *NOT* a good justification for misusing the Apache SVN repository. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
