Re: AW: Ivy - any future or is it also going to be retired?

2016-12-07 Thread Maarten Coene
Thanks Jaikiran! :-) I'll try to review it ... kind regards,Maarten Van: Jaikiran Pai Aan: dev@ant.apache.org Verzonden: woensdag 7 december 18:17 2016 Onderwerp: Re: AW: Ivy - any future or is it also going to be retired? Thank you. Given that there does

Re: AW: Ivy - any future or is it also going to be retired?

2016-12-07 Thread Jaikiran Pai
Thank you. Given that there does seem to be willingness to do something to move things forward with the project, I have now submitted a PR for one of the open JIRAs https://github.com/apache/ant-ivy/pull/10 in an attempt to fix it. Over the weekend, I'll see if I can come up with a list of

AW: Ivy - any future or is it also going to be retired?

2016-12-07 Thread jhm
> One thing that I think is probably is a priority (based on what I have > been trying to attempt while helping out with Ivy patches) is that we > have a central system which builds this project and runs the testsuite > regularly against a *nix and Windows system. Is this already available > in

AW: Ivy - any future or is it also going to be retired?

2016-12-05 Thread jhm
> I thought Ivy was used extensively by Gradle? I see generated ivy.xml > files after running a normal Gradle build, so it still seems to be > important in that space. I don't know. But haven't thought to retire Ivy itself. Jan

AW: Ivy - any future or is it also going to be retired?

2016-12-05 Thread jhm
> If you want to push Ivy, you need integrations with IDE. Yes, I agree. But the problem getting developers to improve IvyDE. > IMHO, IvyDE works well with Eclipse; IvyDE will be available as it is. We don't delete releases as they are archived in the Apache archive. > perhaps its

Re: AW: Ivy - any future or is it also going to be retired?

2016-12-05 Thread Jaikiran Pai
On Monday 05 December 2016 01:25 PM, Jan Matèrne (jhm) wrote: We see Ivy as a widely used component. We use archiving some components to recalibrate our focus. I don't think that we want to archive Ivy in the near future. Instead we try to push Ivy. If you want to help with Ivy, you're

AW: Ivy - any future or is it also going to be retired?

2016-12-04 Thread jhm
We see Ivy as a widely used component. We use archiving some components to recalibrate our focus. I don't think that we want to archive Ivy in the near future. Instead we try to push Ivy. If you want to help with Ivy, you're welcome. "It's already a challenge to stick with Ivy build system