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

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?

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?

> 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

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

+1. Nicolas' mail has some precise things that need to be done. I am willing to help out wherever possible on those steps. I think the first thing to release probably should be a 2.4.1-Beta-1 just to iron out any process and other issues in itself and explicitly tag it as a beta so as to

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

Nicolas raises some great ideas, I would suggest that we get those into Jira and try to cut a release from the current code (just to test the release process). If that works let's try to address one or two simple to fix issues (just to give the release some value) and push out 2.4.1. If

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

On 2016-12-06, Nicolas Lalevée wrote: > These are just ideas poping up my mind to show that if people are > enough motivated, they can make things happen. And obviously, if > things work well, credentials will be granted. Yes, of course. > I think this is the same for IvyDE, but it requires

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

> Le 6 déc. 2016 à 17:21, Stefan Bodewig a écrit : > > On 2016-12-05, Jaikiran Pai wrote: > >> I have been following the latest emails on retiring sub projects in >> Ant. I just see a proposal to retire IvyDE (the Eclipse plugin) for >> valid reasons (given the lack of any

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

On 2016-12-05, Jaikiran Pai wrote: > I have been following the latest emails on retiring sub projects in > Ant. I just see a proposal to retire IvyDE (the Eclipse plugin) for > valid reasons (given the lack of any real activity in there). Given > this, I would like to understand what the future

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

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

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

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

I have been following the latest emails on retiring sub projects in Ant. I just see a proposal to retire IvyDE (the Eclipse plugin) for valid reasons (given the lack of any real activity in there). Given this, I would like to understand what the future of Ivy project itself is. I have asked