Re: Testing IvyDE

2018-07-16 Thread Microsftcompany Award compensa
On Sun, 7/15/18, Nicolas Lalevée wrote: Subject: Re: Testing IvyDE To: "Ant Developers List" Date: Sunday, July 15, 2018, 12:06 PM I have fixed the build, now relying on more recent dependencies. The updatesite built by Jenkins is now up to date. I have started to do some

Re: Testing IvyDE

2018-07-16 Thread Nicolas Lalevée
So the crash of Eclipse occurs also with Java 8. But I have managed to make it crash with other kind of Eclipse console, so this is probably not related to IvyDE. While testing I have found a little bug, some context menu doing nothing, most probably not a regression. Still, I have fixed it in

Re: Testing IvyDE

2018-07-15 Thread Nicolas Lalevée
I have fixed the build, now relying on more recent dependencies. The updatesite built by Jenkins is now up to date. I have started to do some test, but there are some crashes, the jvm of Eclipse is crashing on clearing the Ivy console for instance. I bet this is more due to the fact that I am r

Re: Testing IvyDE

2018-07-04 Thread Jaikiran Pai
On 01/07/18 6:35 PM, Nicolas Lalevée wrote: Le 28 juin 2018 à 08:41, Jaikiran Pai a écrit : On 27/06/18 10:12 PM, Nicolas Lalevée wrote: Since there is a work around (hitting refresh after resolve) and it is an RC, we could ship it like that and fix it later. But due to the automatic updat

Re: Testing IvyDE

2018-07-01 Thread Gintautas Grigelionis
On Sun, 1 Jul 2018 at 21:30, Jan Matèrne (jhm) wrote: > > It looks like Ant nightly is stuck (possibly due to plugin update in > > Jenkins) and it's blocking all other builds. > > > > Gintas > > I can't do it myself so I'll ask for killing the job. > > Jan > Ant nightly aborted, now IvyDE is stu

Re: Testing IvyDE

2018-07-01 Thread Gintautas Grigelionis
It looks like Ant nightly is stuck (possibly due to plugin update in Jenkins) and it's blocking all other builds. Gintas

Re: Testing IvyDE

2018-07-01 Thread Gintautas Grigelionis
On Sun, 1 Jul 2018 at 15:05, Nicolas Lalevée wrote: > I have found the issue and pushed a fix. > > I am then worried that the master is not well tested nor used after the > big cleanups. Two big bugs were raised during the release process. > > So I suggest we do a little testing now of the master