I think we should try to further split ivy into modules: * ivy-core: contains the ivy core; requires only standard Java APIs and contains 2 resolvers: filesystem and http * ivy-ant: contains the ant tasks; has a dependency on ivy-core and Ant * ivy-plugins: contains additional plugins, like http-resolver-with-httpclient, vfs, sftp, ...
The build process could than be changed to: step 1: build ivy-core.jar step 2: build ivy-ant.jar using ivy-core.jar from step 1 step 3: use ivy-core.jar and ivy-ant.jar from previous steps to retrieve the dependencies of the ivy-plugins module. step 4: build the ivy-plugins.jar I think this requires some more work, so this will be hard to accomplish before this release. But I think the first step for this has already been made by the source reorganisation by Xavier. regards, Maarten ----- Original Message ---- From: Xavier Hanin <[EMAIL PROTECTED]> To: [email protected] Sent: Saturday, March 31, 2007 4:29:56 PM Subject: Re: release preparation: release guide Yes, but we have a circular problem here: go-ivy need a version available on the net to run, so we can't update it to the released version before the release is published... OTOH, releasing without updating to the new version is not a very good thing. We have the same problem for Ivy build itself. So, if anyone has an idea, I take it! - Xavier ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html
