Sounds good. I'm closing in on IVY-1420; it's Willem's patch + writeInheritedItems for entire inherited configurations/dependencies blocks (and another test case for that).
PR-57 breaks BC but mitigates that except for a special case. Anyway, why must every release be a drop-in replacement for the previous one? Gintas 2017-09-25 13:42 GMT+02:00 Jan Matèrne (jhm) <apa...@materne.de>: > I recap the todo list before a 2.5.0 release: > > - https://issues.apache.org/jira/browse/IVY-1485 > Incorrect revision of dependencies put in to delivered Ivy files > Status: Jaikiran wanted to focus on that (11.09.2017) > prio: stopper ("but it was IVY-1485 which reanimated the community") > > - https://issues.apache.org/jira/browse/IVY-1420 > defaultconfmapping on <configurations/> element is not written to > delivered ivy file > Status: "I need about a week" > prio: should be included > > - SVG-graphics > Status: > prio: should be included, as it seems to be nearly finished (for me) > > - upgrading BouncyCastle > Status: done > > - IVY-1420/IVY-1437, defaultconf/defaultconfmapping/confmappingoverride > attributes > "according to ivy.xsd, all three attributes can be used on both > dependencies and configurations. > So, it's the documentation that must be adjusted accordingly" > Status: open > prio: maybe delay (and open a Jira ticket) > > - https://github.com/apache/ant-ivy/pull/60 > use Unicode glyphs or SVG data URLs instead of bitmaps > Status: review required > prio: should be included (as part of the "svg-bulk") > > - https://github.com/apache/ant-ivy/pull/57 > fix the last inconsistencies in generics > Status: This includes a change which breaks BC > prio: solve that or delay (this PR should not delay the new version in > my opinion) > > - https://github.com/apache/ant-ivy/pull/55 > use the vectorised logo > Status: nearly finished (missing header) > prio: include that as is nearly finished > > > Some comments/updates? > > > Jan > > > > -----Ursprüngliche Nachricht----- > > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com] > > Gesendet: Montag, 25. September 2017 07:16 > > An: dev@ant.apache.org > > Betreff: Re: Ivy upcoming release - where we stand > > > > Since the latest released version of that library is 1.58, I think we > > should use that version, unless there's a specific reason to not use > > it. > > A quick compilation of Ivy with this library and checking their docs > > for JDK compatibility suggested no issues with 1.58. > > > > -Jaikiran > > > > > > On 19/09/17 10:07 AM, Gintautas Grigelionis wrote: > > > I would like to propose upgrading BouncyCastle to at least 1.57 [1] > > to > > > include all security and PGP/GPG related fixes. > > > > > > Gintas > > > > > > [1] https://www.bouncycastle.org/releasenotes.html > > > > > > 2017-09-11 21:45 GMT+02:00 Gintautas Grigelionis > > <g.grigelio...@gmail.com>: > > > > > >> I'd like to have https://issues.apache.org/jira/browse/IVY-1420 > > >> included in the upcoming release. > > >> > > >> There were few opinions about using SVG graphics, so I'm not sure > > >> whether the proposals could just simply be merged. It would be nice > > >> to refresh the site for the 10th anniversary of graduation from the > > incubator, though. > > >> > > >> Finally, there is a contentious issue of API change regarding the > > use > > >> of generics. Arrays of generics is a no-no in Java [1]. Thus, the > > >> method in question should be deprecated. IMHO, the suggested > > >> mitigation by providing a default implementation of the new method > > in > > >> terms of the old one in the abstract class is sufficient for the use > > cases found in the wild. > > >> > > >> Gintas > > >> > > >> [1] https://docs.oracle.com/javase/tutorial/java/generics/ > > >> restrictions.html > > >> > > >> 2017-09-11 17:05 GMT+02:00 Jaikiran Pai <jai.forums2...@gmail.com>: > > >> > > >>> It's been a while since we have decided to revive the Ivy project > > >>> and work towards a usable release. Since then, we have fixed a good > > >>> number of bugs, added some enhancements and updated the > > >>> documentation (we also switched to asciidoc based docs internally). > > >>> When we started this, the goal was to reach a certain state where > > we > > >>> can do a release. At this point, IMO, we are _almost_ there to do > > >>> the release. I say almost because, there's one specific bug that I > > >>> want to be fixed in this release - > > >>> https://issues.apache.org/jira/browse/IVY-1485. There's been a > > >>> discussion about what it involves and why it isn't an easy fix in > > >>> this mailing list before. I have been working on it and as was > > >>> expected, it's a bit complex and since it touches a critical part > > of the code, I don't want to rush it. > > >>> > > >>> The past few weeks, I have been shifting between this issue and > > >>> fixing certain other issues that have been reported in JIRA. But at > > >>> this point, I plan to just focus on this single issue (and one > > minor > > >>> task involving reviewing the tutorial docs), before I personally > > >>> consider things done for this release. > > >>> > > >>> -Jaikiran > > >>> > > >>> > > >>> > > >>> > > >>> ------------------------------------------------------------------- > > - > > >>> - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For > > >>> additional commands, e-mail: dev-h...@ant.apache.org > > >>> > > >>> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional > > commands, e-mail: dev-h...@ant.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
