Hi, It's been a very long time since we considered releasing Ivy 2.0 beta 1, and as I said last week I think it would really nice to release it very soon, before javapolis where I give a short talk to be accurate.
In JIRA, here are the unresolved issues assigned to 2.0 beta 1: IVY-593 UNRESOLVED Check the Export Control Classification Number (ECCN) IVY-586 UNRESOLVED ivy doesn't handle relocation in pom.xml IVY-616 UNRESOLVED Maven Dependency Management is not used to determine artifact version IVY-591 UNRESOLVED review all tutorials to make sure they are in sync with 2.0 IVY-591 is what has been blocking the 2.0 beta 1 for so long, but I think we are almost done. I've just checked in the reviewed sources of the last unreviewed tutorial (build a repository), so the last thing to do is review the tutorial itself. I will do that this week-end unless someone beats me. I don't know how critical is IVY-593, and what really need to be done. It would be nice if it would not delay 2.0 beta 1. For IVY-586 and IVY-616, I see no reason why we couldn't postpone them to a beta 2 or RC1 if they aren't get fixed in the coming days. Maarten, I've seen you just assigned IVY-616 and a couple of other maven 2 related issues to you, do you think you will have something done soon? Besides this, there's one other thing I really would like to have with 2.0beta 1 is a publication to the maven 2 repository. We are very close, we are already able to generate a pom from our ivy file, we package our sources and generate checksums, so I think it's only a matter of packaging, I should be able to prepare this too this week-end. So, do you agree if I prepare the release on sunday (with at least IVY-591 fixed, maybe some others, no guarantee though), to submit it to your vote early next week? Do you see anything blocking? Any comment on IVY-593? Xavier -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
