On 5/8/07, Maarten Coene <[EMAIL PROTECTED]> wrote:
I'll commit within some minutes, just testing if the emma report still works... The generated ivy-core.jar now contains everything but ant releated classes. However, this is inconsistent with the ivy-core artifact defined in the ivy.xml file. This artifact is in the "core" configuration which is documented as "only ivy core, without ant tasks and any dependencies".
Indeed, this is not very clean... I'm not sure how we should package Ivy: maybe we could package in the core only things which are compiled in the first step of the build, and then package each optional stuff in its own little jar. This would make a change for users of ivy-core (like IvyDE), but it's pretty easy to adapt to the change when using a good dependency manager :) As we have already discussed, even if we provide Ivy in a modular packaging, I'm still in favor of providing ivy.jar as we did before, containing all Ivy in one jar (much easier to use for bootstraping for example). - Xavier I'll create a JIRA issue for this (so we can either fix the jar or fix the
ivy.xml file or both) Maarten ----- Original Message ---- From: Xavier Hanin <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, May 4, 2007 12:28:23 AM Subject: Re: dependency on ivy.jar This seems like a very good thing to me. The only point is about the packaging, ivy-core used to caintain everything but ant related classes, and I think we should keep an artifact like this one, which is used at least in IvyDE. ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html
-- Xavier Hanin - Independent Java Consultant Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
