On 10/17/07, Maarten Coene <[EMAIL PROTECTED]> wrote: > > I'm not sure we should download the ivy.jar ourselfs for the tutorials. > I think it should be the user who should download the jar and make it > available to the build.xml like he wants. > > Downloading the ivy.jar has also some drawbacks: > - it won't work when you don't have internet > - it isn't necessary if you already have ivy.jar in the classpath of Ant > - it could hide errors when users have put an older version of Ivy into > the classpath of Ant. This older version of Ivy will be used when defining > the tasks, even if you download a newer ivy.jar (we have the same problem > at the moment with our own bootstrap mechanism). It will be hard to find out > what goes wrong in this situation...
I agree. But we have only one "tutorial" which downloads ivy.jar: the go-ivy tutorial. The advantage is that it doesn't even require to install Ivy manually, you just copy paste a build.xml and if you already have Ant and a JDK installed (highly probable for a Java developer), that's enough to have a first experience with Ivy and pass the 2 minute test. So I'm in favor of keeping the go-ivy tutorial, and thus need a location to download the ivy.jar from. WDYT? Xavier Maarten > > ----- Original Message ---- > From: Xavier Hanin <[EMAIL PROTECTED]> > To: [email protected] > Sent: Wednesday, October 17, 2007 8:45:43 PM > Subject: 2.0 beta 1 status > > > Hi, > > I would like to check how far we are from the 2.0 beta 1, I think many > users > are waiting for it, and we were supposed to release it much earlier. > > Among the open issues assigned to the beta 1, one which requires more > work > and can't be postponed IMHO is the tutorials review. We already > discussed > that and Gilles suggested to make something where the output is > automatically captured and verified. I don't know if you've had time to > work > on that Gilles, but I think it can be very time consuming, while > reviewing > tutorials text is still necessary anyway. > > So I think we'd better go with the good old human review. I'm ok to > spend > some time on that, even though I would appreciate any kind of help (and > this > is something that can be done even by non committers, the tutorials as > well > as any other documentation can be contributed with patches). > > To start with the first tutorial (go-ivy), we need a location to > download > ivy.jar from (at least for the go-ivy tutorial). Where can we put this > jar? > On our site? IMO the best location would be in maven repository. The > problems are: > - we will only be able to put it over there once we have done the > release, > - it still requires some work from us to do that: write a pom, update > our > release script to prepare artifacts ready to be uploaded to the > repository. > > So, shall we go this way? And even if we publish on the maven > repository, > shall we use it to download ivy.jar for the go-ivy tutorial? > > Xavier > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
