On 12/22/06, Maarten Coene <[EMAIL PROTECTED]> wrote:
Or we could try the following: devide ivy into different parts: - ivy-core: the core of ivy which uses standard JDK classes only (I'm not sure this is possible at the moment) - ivy-ant: the ant tasks - ivy-ext: the extra functionality of ivy (like the different resolvers, ...) which requires third-party libraries The ant build.xml can now compile 'ivy-core' and 'ivy-ant' without any problem, because these parts don't need extra dependencies to be downloaded. After the ivy-core and ivy-ant parts are compiled, they can be used to download the dependencies of the ivy-ext part. This has the additional advantage that for building at least the 'ivy-core' and 'ivy-ant' package, you don't have to be online
The idea is very interesting, even if it's not straightforward to do, because for the moment Ivy core has build time dependencies on third party libraries like commons httpclient. But this could give a good direction to the refactoring I plan to do when I'll have more time (that is, when doc will be migrated, patches integrated, packages renamed, and other stuff I have to do like move IvyDE and IvyCruise to a new place (more about that in another mail). The only problem I see with this approach is that if you have a bug in the core, you may not be able to use the just built core to resolve your dependencies. So we have to be careful with this approach, to be able to use a downloaded core instead of a built one when necessary. Xavier Maarten
----- Original Message ---- From: Antoine Levy-Lambert <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, December 22, 2006 2:31:42 PM Subject: Re: 1.4 builds that don't depend on jayasoft.org being up? Hi, another possiblity for the old ivy releases would be to upload them to http://repo1.maven.org/maven/ivy/distributions jars poms This document explains how to create an upload bundle. http://maven.apache.org/guides/mini/guide-ibiblio-upload.html It does not seem to explain how a distribution file should/could be named in the upload bundle. The best way would be that Xavier creates the upload bundles and enters a JIRA to get the old ivy versions uploaded. I will ask on repository@ how the distributions should be named inside upload bundle jars. Regards, Antoine On Dec 21, 2006, at 11:42 PM, Stefan Bodewig wrote: > On Fri, 22 Dec 2006, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: > >> this should be possible. > > I don't think so. > >> the source and binary zips would go to >> http://archive.apache.org/dist/ivy/ > > And are reserved for Apache releases, which old releases of Ivy are > not. > > Stefan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
