ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gintautas Grigelionis <g.grigelio...@gmail.com>
Subject Re: Ivy-2.5.0
Date Mon, 08 Jan 2018 15:27:37 GMT
What must be done to complete the work on SVG (IVY-922/IVY-450 or resp
PR-55/PR-60)? If you fine with merging (eventually adjusting the contents
of SVG), let's do it.

Changes to alleviate IVY-1315/IVY-1419/IVY-1420/IVY-1437 should be
evaluated by reporters, but nobody responded because the issues are so old.
I would rather close the issues and a open a new issue if needed. I added
test cases for every issue highlighting the specific parts of the problem
and I can write up separately on the design problem with permitting the
same attributes on different elements with recursive inheritance or using
the same attribute name with different semantics depending on the element
(perhaps in Confluence? or Github wiki?).

My opinion on PR-57 is that it addresses another design problem in a
similarly good-enough fashion. We can handle this like Ant and have a Java
7 branch (2.5.x) and a Java 8+ branch with further API changes (2.6.x). The
question is, whether that makes 2.5.x more interesting and is worth the
extra work?

Gintas


2018-01-08 14:48 GMT+00:00 Jan Matèrne (jhm) <apache@materne.de>:

> I took my old TODO list for Ivy-2.5.0.
>
> Most of them are still open, how to deal with that?
>
> In my opinion we should try to get a release out and postpone these to a
> 2.5.1 (means reducing stopper->later).
>
> We have lots of changes we could deliver in this way. We also show a sign
> of
> life in that way.
>
>
>
>
>
> Jan
>
>
>
>
>
>
>
> - https://issues.apache.org/jira/browse/IVY-1485
>
>   Incorrect revision of dependencies put in to delivered Ivy files
>
>   Status:
>
>     11.09.2017: Jaikiran wanted to focus on that
>
>   prio: stopper ("but it was IVY-1485 which reanimated the community")
>
>
>
> - SVG-graphics
>
>   Status:
>
>     08.01.2018: unknown
>
>   prio: should be included, as it seems to be nearly finished (for me)
>
>
>
> - https://github.com/apache/ant-ivy/pull/60
>
>   use Unicode glyphs or SVG data URLs instead of bitmaps
>
>   Status:
>
>     11.09.2017: review required
>
>     08.01.2018: not sure what to do or what impact this have
>
>   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:
>
>     11.09.2017: This includes a change which breaks BC
>
>     08.01.2018: no consense on the API change
>
>   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:
>
>     11.09.2017: nearly finished (missing header)
>
>     08.01.2018: no changes (license header missing)
>
>   prio: include that as is nearly finished
>
>
>
> - https://issues.apache.org/jira/browse/IVY-1420
>
>   defaultconfmapping on <configurations/> element is not written to
> delivered ivy file
>
>   Status:
>
>     11.09.2017: "I need about a week"
>
>     08.01.2018: done (27.09.2017)
>
>   prio: should be included
>
>
>
> - 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:
>
>     11.09.2017: open
>
>     08.01.2018: done
>
>   prio: maybe delay (and open a Jira ticket)
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message