Yes, at least give the users a choice by providing 2 different distributions (which was suggested in a previous post).
I'm behind a very restrictive proxy server, therefor Ivy (or any other Java program) doesn't has Internet access where I work. (So far I don't have a problem since I only use the standard Ivy resolvers for which I don't need any extra library) Besides, I think it complicates installing Ivy on your system. Compare the 2 installation procedures: 1. distribution with all dependencies Installation is very simple: unpackage all includes jars to some folder and use that folder as classpath when loading Ivy tasks. 2. distribution with only ivy.jar Installation requires the following steps: - unpackage ivy.jar and ivy.xml to some directory - create a temporary Ant target which resolves Ivy's ivy.xml and download the jars to the same directory. Things gets extra complicated because the VFS version used by Ivy at the moment doesn't exist on ibiblio. (this should somehow be fixed in a future release I guess). - run that target - delete the temporary ant target and the ivy.xml file (or keep it in the build.xml to download the dependencies for the next Ivy release) - use the jars in the download directory as classpath for the Ivy tasks regards, Maarten ----- Original Message ---- From: Xavier Hanin <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, April 23, 2007 6:22:42 PM Subject: Re: Include dependencies in distribution (Was Re: [VOTE] Submit release apache-ivy-2.0.0-alpha-1-incubating to the IPMC for ratification) Why not, but I agree with Matthias that we should promote the distrib without dependencies. And if the dependencies downloading is made very easy (which is quite simple with Ivy), should we still deliver a bundle with all dependencies? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
