Hi Jan,
My efforts to resolve IVY-1485 have taken longer than I expected, mainly
due to not finding enough time to sort it out. A few weekends I tried to
focus on this, with my local WIP changes, I ran into merge issues with
the latest upstream changes. I resolved them then and continued with the
WIP changes. But a few weeks down the line I ran into the merge
conflicts again. I haven't yet been able to find time to resolve them
locally and spend time on the real fix (I do admit that I lost a bit of
focus/interest with the merges).
I'll try again this weekend and see how far I can get this working.
Either way, I don't want to block the release anymore. If I can't get
IVY-1485 solved by this weekend, I propose to have it marked as a known
issue for this release and I will try and get it out in the next release
after that.
As you note, we do have good number of fixes in this release and it's
time that we have them available to the general public.
-Jaikiran
On 08/01/18 8:18 PM, Jan Matèrne (jhm) wrote:
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)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
