Re: VOTE Retire IvyDE

I decided to take a quick look at the build process and it's not broken per se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32. I would like to make the process to adapt to the build platform. Any suggestions for a reasonable Eclipse baseline? Should we target Java 8, that would be 4.5 (or

[GitHub] ant-ivy pull request #10: Fix for IVY-1531

GitHub user jaikiran opened a pull request: https://github.com/apache/ant-ivy/pull/10 Fix for IVY-1531 The commit here contains a potential fix for the issue reported in https://issues.apache.org/jira/browse/IVY-1531. Maven pom.xml allows dependency exclusion to include

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

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: VOTE Retire IvyDE

On 2016-12-07, Gintautas Grigelionis wrote: > Somebody mentioned that IvyDE build process is broken and I would like to > look into that if it could help to prevent retirement. That would be wonderful, regardless of whether it prevents retirement. Stefan

Re: VOTE Retire IvyDE

Somebody mentioned that IvyDE build process is broken and I would like to look into that if it could help to prevent retirement. Gintas 2016-12-07 10:00 GMT+01:00 Dominique Devienne : > +1 > > On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart < >

Re: VOTE Retire EasyAnt subproject

+1 On Wed, Dec 7, 2016 at 8:14 AM, Jean-Louis Boudart < jeanlouis.boud...@gmail.com> wrote: > +1 > > 2016-12-07 1:05 GMT+01:00 Conor MacNeill : > > > +1 > > > > Conor > > > > > > On 5 December 2016 at 18:04, Jan Matèrne (jhm) > wrote: > > > I start a vote

Re: VOTE Retire IvyDE

+1 On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart < jeanlouis.boud...@gmail.com> wrote: > +1 > > Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée" a > écrit : > > > +1 > > > > Nicolas > > > > > Le 6 déc. 2016 à 17:22, Stefan Bodewig a écrit : > > > >

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: VOTE Retire IvyDE

I would prefer an agreement on status. IvyDE is dependent on Ivy and ideally their release cycles should be synced. Since there seem to be some changes brewing in Ivy, IvyDE could be used as a test case. Gintas 2016-12-07 11:37 GMT+01:00 Stefan Bodewig : > On 2016-12-07,

Re: VOTE Retire IvyDE

> Le 7 déc. 2016 à 12:34, Gintautas Grigelionis a > écrit : > > I would prefer an agreement on status. IvyDE is dependent on Ivy and > ideally their release cycles should be synced. > Since there seem to be some changes brewing in Ivy, IvyDE could be used as > a test

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

Ivy JIRA issues - how do I subscribe?

Is there a specific mailing list to where the Ivy JIRA issue notifications go to? I would like to subscribe to these issues and I can't find a way in JIRA project to send me notifications only for Ivy project JIRAs. -Jaikiran

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