Re: Ivy 2.0 planning

Le jeudi 28 février 2008, Xavier Hanin a écrit : Hi, Ivy 2.0 beta 2 being around the corner, I've reviewed some of the current open issues in JIRA. I've marked all open bugs to be fixed in 2.0, as I would like to make 2.0 final as stable and clean as possible. I even think that fixing bugs

Re: Ivy 2.0 planning

+1. Now we should foccus on getting 2.0 out. So stability, and fix the bug in major 2.0 feature : maven repository compatibility. But I have noted that the list of bug is quiet long... So any patch is more than welcome :-) Gilles On 28/02/2008, Xavier Hanin [EMAIL PROTECTED] wrote: Hi,

Re: Ivy 2.0 planning

On Fri, Feb 29, 2008 at 10:23 AM, Nicolas Lalevée [EMAIL PROTECTED] wrote: Le jeudi 28 février 2008, Xavier Hanin a écrit : Hi, Ivy 2.0 beta 2 being around the corner, I've reviewed some of the current open issues in JIRA. I've marked all open bugs to be fixed in 2.0, as I would like

Re: [VOTE] Ivy 2.0.0-beta2 Release (second attempt)

Here's my own +1 On Mon, Feb 25, 2008 at 10:15 AM, Xavier Hanin [EMAIL PROTECTED] wrote: I have built a second release candidate for Ivy 2.0.0-beta2. Compared to the first attempt, the only change is that I've applied IVY-744 fix that Gilles has checked in on trunk. You can download it from

Re: Ivy 2.0 planning

On Fri, Feb 29, 2008 at 11:33 AM, Gilles Scokart [EMAIL PROTECTED] wrote: +1. Now we should foccus on getting 2.0 out. So stability, and fix the bug in major 2.0 feature : maven repository compatibility. But I have noted that the list of bug is quiet long... So any patch is more than

Fixing some naming inconsistencies in Ivy

Hi, As reported by IVY-297, Ivy suffers from some name inconsistencies and strange attribute names. Ivy 2.0 is a good opportunity to fix some of them, since I think we can afford some more deprecation warnings. So I'd like to fix IVY-297 by marking allownomd as deprecated, and providing a

Re: 1.7.1 - Beta Vote

+1 on the plan / releasing a beta Martijn Kevin Jackson schreef: Hi, As I mentioned previously (although I'm a couple of days late). I'd like to release a beta of 1.7.1 within the next two weeks. The current 1.7.1 trunk is now locked for further changes (99.9% test completion on the most

Re: https://issues.apache.org/bugzilla/show_bug.cgi?id=41724

Marcelo Tancredi schreef: Hi, I am having the same problem here. What is the fix for this? Thanks - Marcelo Tancredi IBM Software Group - Boca Raton, Florida [EMAIL PROTECTED] Hi I have added a link to the fixed source in the bugrep in ant 1.7.1 the fix will be included. Further