Yes for the first part. For optional dependencies, actually I'm not sure how we handle them. If we can't handle them, we should raise a Jira issue.
The problem that we have with go-ivy is not related to optional or not. It is related to our interpretation of the test scope of modules published on a repository. I will spare you the details. Maybe you can explain what you want to do. The go-ivy example is the most basic use case : use ivy to download one module and its potential dependencies. Maybe what you want to do is to download all dependencies of your own module. For that, look at the other tutorials. Gilles 2007/7/31, Jing Xue <[EMAIL PROTECTED]>: > > > If I understand correctly, the only manual step is to copy the ivy.jar > into either $ANT_HOME/lib, or ~/.ant/lib. And you should be able to > build the examples or your own scripts as long as they don't involve > the optional dependencies. > > Cheers > -- > Jing Xue > > Quoting Chris Hane <[EMAIL PROTECTED]>: > > > No problem. Could you write up at least in email the couple of steps I > > need to get the alpha2 working? I would like to start using the new > > version of Ivy but need a little direction. > > > > Also, I'm using eclipse 3.3 rather than the command line. > > > > Thanks, > > Chris... > > > > -- Gilles SCOKART
