When I download some library, I like having all the runtime dependencies included in the zip. It's sometimes a lot of work to: - get an overview of all the dependencies - find the dependencies on the web - find the correct version of the dependency When the dependencies are part of the distribution, you are sure that you have them all and you also have the correct version.
However, not all dependencies should be in the distribution file! For instance: I don't think having junit.jar and emma.jar in the ivy.zip would be good. However, I don't think this should block the first alpha release. Maybe you could use this new version of Ivy to download Ivy's dependencies :-) regards, Maarten ----- Original Message ---- From: Xavier Hanin <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, April 23, 2007 5:49:12 PM Subject: Include dependencies in distribution (Was Re: [VOTE] Submit release apache-ivy-2.0.0-alpha-1-incubating to the IPMC for ratification) On 4/23/07, Scheper, Erik-Berndt <[EMAIL PROTECTED]> wrote: > > I agree that these jars are only required for certain configurations, > and as such may be considered optional. > However, I do believe that these dependencies should have been included, > as otherwise you will run into noclassdeffound errors if you try some of > the documented features. I think we need to put a better documentation about dependencies and when they are required. About including them in the distribution instead of providing an easy way to download them separately, I personally prefer to keep them separated, so that you download them only if you need them. Also, most of these jars are apache jars (jakarta / commons). I cannot > believe that including these should be a problem form IPMC ratification. > The only problematic jars I can think of are jdom and jsch. However, the > Maven 2.0 binary already packages jsch, and Geronimo packages jdom, so > this should not be a problem either. > Or am I mistaken here? You're probably right, the ratification is not a good reason. But I still think that using Ivy itself to download its dependencies on demand is a clean and good way to get only needed dependencies, and make people better understand what they actually need to run Ivy. What do others think? Adding an ant script to download the required jars might be a simple way > to solve the issue for this alpha release - at least there is a > documented way to retrieve these dependencies. In forthcoming releases I > would still prefer to have them included in the binary distribution. I don't think we'll fix the problem for the alpha release, unless we get a -1 (I know we are only 0.01 away from your -1 :-) ). This alpha release is not focused on production quality, it's there to get somthing out in the incubator, test our release process, clear legal bits, and get something released before ApacheCon EU. So I really hope the attempt currently submitted to the IPMC will be accepted, otherwise it will be difficult to get the release in time for ApacheCon. But I'm open to the discussion for later releases, and if other share your opinion about shipping dependencies, we will review our distribution for the next release. Xavier (Almost) all other apache products do it too (look in the geronimo > binary for the sheer number of jars included there). > > Regards, > > Erik-Berndt Scheper > > > -----Oorspronkelijk bericht----- > Van: Xavier Hanin [mailto:[EMAIL PROTECTED] > Verzonden: maandag 23 april 2007 15:37 > Aan: [email protected] > Onderwerp: Re: [VOTE] Submit release apache-ivy-2.0.0-alpha-1-incubating > to the IPMC for ratification > > > On 4/23/07, Scheper, Erik-Berndt <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I have just downloaded and tried the ivy-2.0.0 alpha 1 snapshot which > > seems to work OK, but misses all dependent jars necessary to run ivy. > > > None of those jars are necessary, they are only optional dependencies. > Therefore to simplify the IPMC ratification (which is mostly based on > legal issues), we have removed those jars from the distribution. > > Now I had to download and include these manually. > > > Sorry for the inconvenience, maybe the easiest way to solve this problem > would be to add an ant script with the release distrib, which would use > ivy to download its dependencies (as is done in the src distrib). Then > downloading would be really easy as soon as you have ant installed. > > If you think this would be a good solution, you can open an issue in > JIRA. > > Xavier > > -- > Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ > Manage your dependencies with Ivy! http://incubator.apache.org/ivy/ > > Disclaimer: > This message contains information that may be privileged or confidential > and is the property of Sogeti Nederland B.V. or its Group members. It is > intended only for the person to whom it is addressed. If you are not the > intended recipient, you are not authorized to read, print, retain, copy, > disseminate, distribute, or use this message or any part thereof. If you > receive this message in error, please notify the sender immediately and > delete all copies of this message. > -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
