Re: Ivy upcoming release - where we stand

2017-09-25 Thread Gintautas Grigelionis
I'd rather deprecate as much as possible for 2.5.0, so that deprecated stuff could be removed in 3.0 :-) Gintas 2017-09-25 14:51 GMT+02:00 Jan Matèrne (jhm) : > > I'm closing in on IVY-1420; it's Willem's patch + writeInheritedItems > > for entire inherited configurations/dependencies blocks (an

Re: Ivy upcoming release - where we stand

2017-09-25 Thread Gintautas Grigelionis
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

2017-09-24 Thread Jaikiran Pai
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

Re: Ivy upcoming release - where we stand

2017-09-24 Thread Gintautas Grigelionis
2017-09-24 15:03 GMT+02:00 Nicolas Lalevée : > > > Le 11 sept. 2017 à 21:45, Gintautas Grigelionis > a écrit : > > > > I'd like to have https://issues.apache.org/jira/browse/IVY-1420 > included in > > the upcoming release. > > Every bug is important, but I think releasing often is more important.

Re: Ivy upcoming release - where we stand

2017-09-24 Thread Nicolas Lalevée
> Le 19 sept. 2017 à 06:37, Gintautas Grigelionis a > écrit : > > I would like to propose upgrading BouncyCastle to at least 1.57 [1] to > include all security and PGP/GPG related fixes. +1 Nicolas > > Gintas > > [1] https://www.bouncycastle.org/releasenotes.html > > 2017-09-11 21:45 GMT+

Re: Ivy upcoming release - where we stand

2017-09-24 Thread Nicolas Lalevée
> Le 11 sept. 2017 à 21:45, Gintautas Grigelionis a > écrit : > > I'd like to have https://issues.apache.org/jira/browse/IVY-1420 included in > the upcoming release. Every bug is important, but I think releasing often is more important. Apart from IVY-1485 which is kind of special, I think we

Re: Ivy upcoming release - where we stand

2017-09-24 Thread Nicolas Lalevée
> Le 11 sept. 2017 à 17:05, Jaikiran Pai a écrit : > > 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 > asciido

Re: Ivy upcoming release - where we stand

2017-09-23 Thread Gintautas Grigelionis
Continuing software archaeology: confmappingoverride is in both dependencies and configurations in ivy.xsd on 1.4.x branch. Gintas 2017-09-24 7:11 GMT+02:00 Gintautas Grigelionis : > I carry on talking to myself:-) according to ivy.xsd, all three attributes > can be used on both dependencies and

Re: Ivy upcoming release - where we stand

2017-09-23 Thread Gintautas Grigelionis
I carry on talking to myself:-) 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... any opinions whether that deserves a separate Jira issue? Gintas 2017-09-23 17:10 GMT+02:00 Gintautas Gri

Re: Ivy upcoming release - where we stand

2017-09-23 Thread Gintautas Grigelionis
Re IVY-1420/IVY-1437: there's yet another bug related to duplicated defaultconf/defaultconfmapping attributes. The specification says that confmappingoverride belongs to configurations. The way XmlModuleDescriptorUpdater looks -- check out startDependencies method -- it is set in dependencies elem

Re: Ivy upcoming release - where we stand

2017-09-18 Thread Gintautas Grigelionis
I believe the reason of having the same attributes in different sections of Ivy files is being able to inherit them selectively; thus they must be remain in the same section where they were set originally. Gintas 2017-09-19 7:42 GMT+02:00 Gintautas Grigelionis : > Looking at IVY-1420/IVY-1437 it

Re: Ivy upcoming release - where we stand

2017-09-18 Thread Gintautas Grigelionis
Looking at IVY-1420/IVY-1437 it appears that defaultconf and defaultconfmapping attributes were first used with dependencies and were duplicated in configurations afterwards; would it be sufficient to put them only on dependencies (that's how current code works)? I would be very grateful for any us

Re: Ivy upcoming release - where we stand

2017-09-18 Thread Gintautas Grigelionis
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 : > I'd like to have https://issues.apache.org/jira/browse/IVY-1420 i

Re: Ivy upcoming release - where we stand

2017-09-11 Thread Gintautas Grigelionis
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 th