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

> 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

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

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. On 5 December 2016 at 08:58, Oulds, Jonathan wrote: > We use Ant + Ivy extensively in our build system. I

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

We use Ant + Ivy extensively in our build system. I too have noticed the lack of development within the Ivy project which is why I recently re-joined the community. I would be happy to contribute patches and or ideas for future development if the project is to continue. Please bear in mind

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

> 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: Ivy - any future or is it also going to be retired?

On Monday 05 December 2016 04:17 PM, Johan Corveleyn wrote: An innocent bystander's opinion (I'm not an ivy / ant developer, but I'm active in the Apache Subversion community): First of all, this is a volunteer-driven open source project. I completely understand. You're entirely free to

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

On Mon, Dec 5, 2016 at 11:33 AM, Jaikiran Pai wrote: > > > On Monday 05 December 2016 03:26 PM, Gintautas Grigelionis wrote: >> >> If you want to push Ivy, you need integrations with IDE. > > > +1 > > I haven't voted in that mail about retiring IvyDE because I don't know

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

On Monday 05 December 2016 03:26 PM, Gintautas Grigelionis wrote: If you want to push Ivy, you need integrations with IDE. +1 I haven't voted in that mail about retiring IvyDE because I don't know what a -1 (which is what I would have voted) would do in reality. As noted in that other

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

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

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

If you want to push Ivy, you need integrations with IDE. IMHO, IvyDE works well with Eclipse; perhaps its release cycle needs to be synced with Ivy release cycle (which is roughly biannual a this point). Is there a release plan for Ivy, by the way? When will this