[GitHub] ant-ivy issue #55: use the vectorised logo

2018-01-08 Thread twogee
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/55 Thanks for recapitulating the issues; headers and javadoc corrected. I tested the xsl using the buildfile provided above (without pointing out the xsl explicitly), so I tend to suspect you're

AW: Ivy-2.5.0

2018-01-08 Thread jhm
> 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. I added a comment on the PR. For short: - license header is missed on two files - improve two JavaDocs - test: does the fresh

[GitHub] ant-ivy pull request #63: IVY-1486 respect exclude regardless of order

2018-01-08 Thread twogee
GitHub user twogee opened a pull request: https://github.com/apache/ant-ivy/pull/63 IVY-1486 respect exclude regardless of order You can merge this pull request into a Git repository by running: $ git pull https://github.com/twogee/ant-ivy ivy-1486 Alternatively you can revie

Re: Ivy-2.5.0

2018-01-08 Thread Jaikiran Pai
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

[GitHub] ant-ivy issue #55: use the vectorised logo

2018-01-08 Thread janmaterne
Github user janmaterne commented on the issue: https://github.com/apache/ant-ivy/pull/55 Still open are: IvyLogo.java JavaDoc of the parameters of IvyLogo(int width, int height) are bad ("ditto") test the report But a simple ivy:report didnt work

Re: Ivy-2.5.0

2018-01-08 Thread Gintautas Grigelionis
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

Ivy-2.5.0

2018-01-08 Thread jhm
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