I just (re)start working it today, when I was in the train. For the moment, I only plan to run the tutorials, and store the result in a file in svn.
So indeed, a review of the text (and possibly the scripts) of the tutorial will be required. Gilles 2007/10/17, Xavier Hanin <[EMAIL PROTECTED]>: > > 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/ > -- Gilles SCOKART
